Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site grkermi.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!genrad!grkermi!eric
From: eric@grkermi.UUCP (Eric N. Starkman)
Newsgroups: net.mail.headers
Subject: Re: Re: Avoiding expansion of mail's metacharacters
Message-ID: <573@grkermi.UUCP>
Date: Thu, 22-Aug-85 15:45:26 EDT
Article-I.D.: grkermi.573
Posted: Thu Aug 22 15:45:26 1985
Date-Received: Sat, 24-Aug-85 19:25:50 EDT
References: <1391@cbosgd.UUCP> <2637@sun.uucp> <1043@sdcsvax.UUCP> <138@maynard.UUCP> <560@neuro1.UUCP> <5063@mit-eddie.UUCP>
Reply-To: eric@grkermi.UUCP (Eric N. Starkman)
Organization: GenRad, Inc., Concord, Mass.
Lines: 26
Summary: 

In article <5063@mit-eddie.UUCP> barmar@mit-eddie.UUCP (Barry Margolin) writes:
>         The recipient of a message is specified in SMTP with the "RCPT
>TO:" command.  The following is well within the SMTP (RFC 821, I
>believe) protocol:
>
>MAIL FROM:
>RCPT TO:
>DATA
>From: 
>To: 
>This is a message being delivered to someone
>who is not in the header.
>.
>
>This might occur because UserB is a blind-copy recipient.
                          ^^^^^
should read               UserA.  The rcpt to:<> has UserA in it, and
that's where the message will go.

>    Barry Margolin
>    ARPA: barmar@MIT-Multics
>    UUCP: ..!genrad!mit-eddie!barmar

					-Eric Starkman
ARPA: starkman@mit-athena
UUCP: ...decvax!genrad!panda!ens