ietf-822
[Top] [All Lists]

Re: [ietf-dkim] Mailing lists as 2822-Sender (was: Responsibility vs. Validity)

2007-12-04 16:54:30
[Apologies for duplicates, if any. List issues and decided to Cc ietf-822 and ietf-smtp.]

On 12/1/07 at 3:30 PM +0000, John Levine wrote:

RFC 2822 section 3.6.2 describes originator fields. By my reading it is pretty clear that a list should add a Sender: field with the list's name since it's the list that's sending the mail.

Uh.....not by my reading. Lists add List-* fields (RFC 2369, RFC 2919) if they want to indicate something. Fields in the original message should be preserved as-is.

Section 3.6.6 describes resent headers. One could make a plausible argument that a list should add a Resent-Sender: rather than a Sender: but it's reasonable to do it either way.

Mailing lists using Resent-* fields gives me the willies. Resent-* fields were intended for MUAs resending mail. They weren't intended for mailing lists.

pr
--
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated
--
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated
_______________________________________________
NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html