On Wed, 2004-08-18 at 03:36:24, Philip Hazel
<ph10(_at_)cus(_dot_)cam(_dot_)ac(_dot_)uk> wrote:
<snip>
With one possible exception, everybody's opinion was that an MTA has no
business messing with Bcc: header lines. Here is a quote from Tony
Hansen:
"The MUA, however it is constituted, should handle all BCC processing,
and the cloning of messages with and without the Bcc: header."
<snip>
I haven't seen it mentioned here yet, but shouldn't the rule be that the
agent that extracts the contents of the Bcc: header field, along with To:
and Cc:, in order to construct the 2821 RCPT TO: commands, is the agent that
determines the contents and/or (lack of) presence of the Bcc: field in the
message. Any agent that receives the recipient addresses via RCPT TO: can
be assured that the decision has already been made.
The part here about receiving addresses via RCPT TO is certainly fine. I
believe the part about agents which construct envelopes from headers is also OK
- it is certainly how I've implemented it. However, since in our model this
sort of processing happens within the MUA, it isn't clear to be we can, or for
that matter should, specify it.
Ned