At 12:14 PM 9/11/2001 +0100, Norman wrote:
> > 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.
Yes, that's what I said. Correct.
In over a decade of administering SMTP mail servers and mentoring dozens of
mail admins on various platforms, I can state definitively that the
distinction between the SMTP envelope and the headers is the least
understood aspect of SMTP for mail admins. Which is unfortunate, because
it's so important.
>Multiple RCPT TO's are used so that a single message can
>go to many receipients, the same as for any other message.
This was the specific item I was testing, as Ed had suggested that each BCC
recipient would be sent a separate message.
Certainly, the RCPT TO: envelope recipients could be multiple, or could be
singular causing more mail messages. Neither choice impacts the successful
"hiddenness" of BCC: recipients, but does impact the amount of redundant
traffic Exchange generates.
Fortunately, as you say and as I found, Exchange does the Right Thing
(IMHO), putting multiple BCC recipients in one envelope.
>Receiving mail servers should not be massaging headers!
Of course not. I think this is an idea that neither Ed nor I expressed,
but was injected by Greg.
Joel Noble
[EMAIL PROTECTED]
_________________________________________________________________
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]
