On Saturday 14 January 2012 12:59:10 Werner Flamme wrote:
But what does the next mailserver do? Example: userd@d.com sends a mail to his local mail server (outgoing mail relay) that is addressed TO: usera@a.com, CC: userb@b.com, and BCC: userc@c.com. This first mail server removes the BCC line, and sends the mail with the remaining TO and CC entries to the MX of c.com - this server may not compare the envelope recipient with TO: and CC: - or what? Do the servers compare with Bcc: only?
To make it clearer, let me give you an example: a mail is addressed to a@foo.com and b@foo.com, cc c@bar.com and bcc: d@baz.com The client connects to the MX for foo.com and sends in the envelope RCPT TO: a@foo.com, b@foo.com the contents of the email are To: and CC: only, not bcc. it then connects to the MX for bar.com and sends RCPT TO: c@bar.com and finally to the MX for baz.com and sends RCPT TO: d@baz.com The actual email contents are the same in all three cases, To: and CC: only, no bcc info. The only server that sees that d@baz.com gets the email is the MX for baz.com. foo@com and bar@com know nothing about this. Your client will then note that you are nowhere in To or cc, and deduce that you must have been in bcc, so e.g. kmail will then display your address as bcc. but this is a client side nicety. it is not in the actual email itself. If on the other hand it had been bcc d@foo.com instead, that final stage would have been eliminated, and the initial connection would have been RCPT TO: a@foo.com, b@foo.com, d@foo.com instead, and the mail administrator of foo.com would have been able to see d as a bcc recipient (since all is logged), but a and b when looking at their emails in their inboxes would still only have seen the actual mail contents, which as I said were always limited to To: and CC: Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org