Re: [Exim-dev] Exim's handling of Bcc lines (was Re: [BUG] …

Top Page
Delete this message
Reply to this message
Author: Matthew Byng-Maddick
Date:  
To: Derek Martin
CC: exim-dev
Subject: Re: [Exim-dev] Exim's handling of Bcc lines (was Re: [BUG] mutt 1.2.5 sends mail with Bcc: header)
On Fri, Jul 23, 2004 at 01:09:45PM +0900, Derek Martin wrote:
> RFC 822 is superceeded by 2822; it is therefore irrelevant.


Dear Derek

| 0822 Standard for the format of ARPA Internet text messages. D.
|      Crocker. Aug-13-1982. (Format: TXT=109200 bytes) (Obsoletes RFC0733)
|      (Obsoleted by RFC2822) (Updated by RFC1123, RFC1138, RFC1148,
|      RFC1327, RFC2156) (Also STD0011) (Status: STANDARD)

                                                 ^^^^^^^^

| 2822 Internet Message Format. P. Resnick, Ed.. April 2001. (Format:
|      TXT=110695 bytes) (Obsoletes RFC0822) (Status: PROPOSED STANDARD)

                                                      ^^^^^^^^^^^^^^^^^


This is from the rfc index as updated today, HTH, HAND.

Personally, I happen to agree with Exim's current handling. The way that
SMTP is defined, the envelope and the headers are completely separate,
they only bear relation to each other by convention. If your MUA can't
construct the headers and envelope for transmission appropriately, and
I encourage you to look at the way that it passes mail to the MTA for
onward transmission, that would seem to be your MUA's problem. My copy
of mutt seems to cope perfectly well with using Bcc in its own construction
of the envelope, and then deleting it, and I would suggest that this is
the correct behaviour.

This is also probably the wrong list to be discussing this on.

Cheers

MBM

-- 
Matthew Byng-Maddick          <mbm@???>           http://colondot.net/
                      (Please use this address to reply)