Liviu Daia <daia@???> probably said:
> RFC 822 requires removal of "Bcc:" headers only for copies sent to
> the recipients in the "To:" and "Cc:" fields; it's optional on copies
> sent to "Bcc:" addressees. If your MTA does something else, then your
> MTA is broken, and not Mutt. From RFC 822:
>
> : 4.5.3. BCC / RESENT-BCC
> :
> : This field contains the identity of additional recipients of the
> : message. The contents of this field are not included in copies
> : of the message sent to the primary and secondary recipients.
> : Some systems may choose to include the text of the "Bcc" field
> : only in the author(s)'s copy, while others may also include it
> : in the text sent to all those indicated in the "Bcc" list.
I'm arguing that mutt should remove the Bcc: if the user doesn't want
it to go anywhere.
It does seem to be that the MTA should remove the Bcc: when the
message is sent to the primary recipients because otherwise the MUA
would have to send two copies of the message to the MTA (one with the
bcc: included and list recipients of the bcc and another copy without
the bcc: and the recipients listed as the to: and cc: people).
Urg. In general.
P.
--
pir pir@??? pir@??? pir@???
--
*** Exim information can be found at
http://www.exim.org/ ***
