On 1/12/2012 10:32 PM, Werner Flamme wrote:
[12.01.2012 23:12] [John Andersen]:
On 1/12/2012 12:00 PM, Werner Flamme wrote:
[12.01.2012 07:01] [Basil Chupin]:
I tested this out before responding (by sending some test messages to my wife, sitting 3 feet away from me :-) ) and you are correct about the BCC: but not the CC: option: you don't get the "Undisclosed-recipients" with the CC: when the To: field is empty.
A normal mail server will remove the "Bcc:" lines from a mail, but the "Cc:" remain. So, when the "To:" field is empty, and the sender entered addresses in "Bcc:" only, it is a real case of "undisclosed recipients", isn't it? :-)
Since normally the "Cc:" recipients are transported to every receiver, the recipients (at least not all) are not undisclosed ;-)
Actually it used to be the job of the CLIENT to remove the BCC. If this is now handled by the Server it is certainly not universally handled correctly.
Which client? The sending client? So where would the server know the Bcc from? The receiving client? Why should privacy depend on client software behaviour only? You might turn off the Bcc behaviour and see all the recipients then, though the sender may not want this.
Receiving client. I'm not defending this method Werner, just reporting how it use to be in days gone by. Not all servers stripped BCC, and receiving clients were set up to do so, but anyone with a tiny bit of work could fetch the entire BCC list. I speculate there are a few such servers still running somewhere, but most have improved. Even Wikipedia mentions this problem, its been a long standing issue. http://en.wikipedia.org/wiki/Blind_carbon_copy#Visibility says this:
It also states: There are three ways in which the "BCC:" field is used. In the first case, when a message containing a "BCC:" field is prepared to be sent, the "BCC:" line is removed even though all of the recipients (including those specified in the "BCC:" field) are sent a copy of the message. In the second case, recipients specified in the "To:" and "CC:" lines each are sent a copy of the message with the "BCC:" line removed as above, but the recipients on the "BCC:" line get a separate copy of the message containing a "BCC:" line. (When there are multiple recipient addresses in the "BCC:" field, some implementations actually send a separate copy of the message to each recipient with a "BCC:" containing only the address of that particular recipient.) Finally, since a "BCC:" field may contain no addresses, a "BCC:" field can be sent without any addresses indicating to the recipients that blind copies were sent to someone. Which method to use with Bcc: fields is implementation dependent and may depend on both one's mail user agent (e.g. Outlook, Thunderbird) and mail submission agent (usually provided by one's ISP). Since the hiding of the Bcc: addresses from other Bcc: addresses is not required by RFC 2822, one cannot assume the Bcc: addresses will be hidden from other Bcc: addresses.
-- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org