>
>
> >>BCC results in a separate message sent to each non-Exchange
> recipient.
>
> >Actually, this appears to not be true.
>
> That was my understanding too. I was under the impression
> that it is up to the receiving server to massage the headers
> so that it looked like the BCC recipient was the only one
> receiving the message. But, when Ed Crowley said "BCC
> results in a separate message sent to each non-Exchange
> recipient", my confidence was broken and I bowed to the master.
>
> So, masters and apprentices, which is it?
Neither.
Use of the BCC field simply tells the *sending* client to not put those
recipient addresses in the RFC822 headers.
The addresses only go in the transient SMTP envelope(s) which won't be seen by
the final recipients. Multiple RCPT TO's are used so that a single message can
go to many receipients, the same as for any other message.
Receiving mail servers should not be massaging headers!
Norm
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
