Kris Deugau said: >> If you use a competent email client you will be offered the option >> of keeping a local copy, which saves the redundant recipient. > > Some people deliberately turn this off. I'm not sure why. (I can > *sort* of understand it for mailing list mail, but not for "direct" > mail.) > >> Further, you should never assume that other recipients do not >> see BCCs. That it entirely up to the settings of the recipient's email >> client. > > If your MUA is actually adding a "real" header with BCC: information, > it's broken. BCC isn't supposed to be a header in the usual sense; it's a > way to tell your mail client to add extra SMTP RCPT TO: commands when > sending the message. The recipients should NEVER see those extra > recipients. > > The only way someone might find out about BCC'ed recipients is if they > are the server admin (or have access to the mail logs) and are willing to > spend the effort to wade through the logs tracking the message ID to see > who got a copy. And that only applies in the case where the sender's SMTP > server is also the destination; and partially applies if there are > multiple recipients at a remote domain. If a remote domain only has one > recipient in the list, they will NOT see any information regarding other > recipients.
I've also seen broken mail servers that add headers based on the "rcpt to:" so you should assume that recipients bcc or not on the same remote server may be able to discover each other. But if you're confident your mail server/client isn't doing something stupid then there should be no way for [EMAIL PROTECTED] to discover the message was BCCed to [EMAIL PROTECTED] Jay -- Jay Lee Network / Systems Administrator Information Technology Dept. Philadelphia Biblical University --
