Pete Resnick wrote:
On 12/1/07 at 3:30 PM +, 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
On Tue, 4 Dec 2007, [EMAIL PROTECTED] wrote:
I don't recall anyone considering using Resent- fields for this until
just now, but I could easily have missed it
I think it's a cute idea, but Resent- fields are an interop nightmare
because the 822 specification is too weak to work in general
[Apologies for duplicates, if any. List issues and decided to Cc
ietf-822 and ietf-smtp.]
On 12/1/07 at 3:30 PM +, 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
Pete Resnick wrote:
[Apologies for duplicates, if any. List issues and decided to Cc
ietf-822 and ietf-smtp.]
On 12/1/07 at 3:30 PM +, 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
Scott Kitterman wrote on the DKIM list:
On Thursday 29 November 2007 06:32, Charles Lindsey wrote:
Note that a mailng list expander is supposed to insert a Sender.
IIRC it's a SHOULD and not a MUST, so one really can't rely on it.
Can you (Charles + Scott, or anybody else who knows it)
Can you (Charles + Scott, or anybody else who knows it) please
check this ? I thought that mailing lists are NOT supposed to
insert Sender (or Resent-*) header fields unless they wish to
participate in PRA checks (RFC 4406).
Since Sender-ID is at most an experimental RFC, no sensible mailing
