[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "proper" handling of BCC
- To: ietf-smtp@xxxxxxx
- Subject: Re: "proper" handling of BCC
- From: "John Levine" <johnl@xxxxxxxxx>
- Date: 16 Apr 2012 15:38:13 -0000
- Cc: john@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f8c3cfb.xn--30v786c.k1204; i=johnl@xxxxxxxxxxxxx; bh=k/NdxkJQceX0Benk1u9DL6bW5DoYqwbXscNwVPuJ2p8=; b=VolSqXr4DYDFr0ZH6WrCUQmi5zucWQ//42Ce/7yu5asitpAEjxCaJ8nSDXJHCD4cHrhMdgNCIjA3jHtD6/fqIf4AKw61rtx78vLlZfpENvzr2xqu2A/zjVuggE0YUlcAGZIhdgEWHNqbA6dsllQj0QPRmFyj1GrDzCVxBC89+uU=
- Dkim-signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f8c3cfb.xn--30v786c.k1204; olt=johnl@xxxxxxxxxxxxx; bh=k/NdxkJQceX0Benk1u9DL6bW5DoYqwbXscNwVPuJ2p8=; b=SD22DccrnLmOrunUp0RUksdAjY/dh4rQKb6prJklt93zUeNjxlM5ucoQ+bG4E441oJINqxOLUZ26ZTgxRQUX7VWPzd8dEWqVO5xaxfykeutXIhviVFYgCtZQCIg1arbD1KcvKy1Jmw+UN6mvxjalS4VplYc5FOWSZkeu0OD8g9k=
- In-reply-to: <>
- List-archive: <http://www.imc.org/ietf-smtp/mail-archive/>
- List-id: <ietf-smtp.imc.org>
- List-unsubscribe: <mailto:email@example.com?body=unsubscribe>
- Sender: owner-ietf-smtp@xxxxxxxxxxxx
- Vbr-info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
> Of course, if one had a submission server that was smart about these
> things, the MUA could hand the message, including the Bcc field, to
> it and let it sort out envelopes (which it needs to do anyway) and
> the warning message.
That strikes me as a really unfortunate idea. Submission servers know
all about envelopes and message headers. In most cases, they don't
know anything about the body of the message beyond what they can
intuit from the MIME headers.
If your submission server adds text to a body saying something like
"you are a blind copy recipient", in what language is that message
expressed? If you'd rather it use another language, how can you tell
it to do so? This all belongs in the MUA.
While there is plenty of historical precedent for submission servers
fixing up headers, adding missing ones that can be constructed
mechanically, and creating an envelope based on recipient addresses in
the headers, I can't think of fixups they do to message bodies other
than perhaps wrapping the whole unmodified body in a crypto signature.
I'd rather move toward MUAs creating correct messages, and having
submission server fixups as a backup.