A mailing list is an original mail object that is comprised of vetted
submitted material much like a newspaper. It should take submitted
material, empty the accompanied envelope and remail using a fresh clean
envelope with new headers.
Thanks,
Bill Oxley
Messaging Engineer
Cox Communications
404-847-6397
-----Original Message-----
From: ietf-dkim-bounces(_at_)mipassoc(_dot_)org
[mailto:ietf-dkim-bounces(_at_)mipassoc(_dot_)org] On Behalf Of Dave Crocker
Sent: Saturday, December 01, 2007 10:54 AM
To: ietf-dkim(_at_)mipassoc(_dot_)org
Subject: Re: [ietf-dkim] Mailing lists as 2822-Sender
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.
+1.
A mailing list agent often and reasonably changes a message in
substantial
ways. Even if a particular agent does not make changes (other than
re-posting) it is, in fact, re-posting. That makes the mailing list
agent the
address that is appropriate for the rfc2822.Sender field.
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.
My own feeling is that resent headers were a good idea that have proved
far
more problematic that beneficial. One could make a very plausible
argument for
deprecating them...
ps. Having this list discuss Sender-ID seems a bit odd. Worse is the
idea
that Sender ID or DKIM or any adjunct protocol enhancement could be
viewed as
modifying anything as basic as the content of rfc2822 Originator
fields...
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html