[Oberon] another fault involving SMTP?
joerg.straube at iaeth.ch
Sun Oct 17 23:19:46 MEST 2010
"Bcc" is a can of worms as its handling is very implementation
dependent. The newest SMTP specs RFC 5321, Appendix B
recommend the following:
The original UA (sender's mail program) should hand over
the mail to the first MTA (SMTP server) as follows
- add all Bcc recipients to the RCPT command
- the "Bcc:" header field (provided in DATA) should be present
On 17.10.2010, at 22:32, Duke Normandin wrote:
> On Sun, 17 Oct 2010, peasthope at shaw.ca wrote:
>> Imagine I send a message to these addresses.
>> to: cougar at mountains.org
>> bcc: goat at mountains.org
>> In MacOS both recipients see both addresses in the header.
>> In MS-Win each recipient sees only his or her address.
>> According to my very limited understanding of SMTP, this
>> is a fault of the SMTP server. A bcc: recipient should
>> receive only his/her own address. A to: or cc: recipient
>> should not receive bcc: addresses. Whether or not a
>> receiving system shows bcc: addresses is a secondary
>> argument. Can anyone confirm this or correct my misunderstanding?
>> As an additional test this message is addressed
>> To: oberon at lists.inf.ethz.ch
>> bcc: eagle at mountains.org
>> If the Shaw SMTP server transmits it, I'm curious to
>> know whether the eagle at mountains.org is in the header.
> I'm replying using Al(pine). No bcc showed up in the headers - as
> should be. Only the sender and recipient of the bcc should be aware of
> its existence. Didn't see it using emacs/RMAIL either. HTH
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon