Re: Mailing lists as 2822-Sender
Hector Santos <[email protected]>
| Newsgroups | gmane.ietf.dkim,gmane.ietf.rfc822 |
|---|---|
| Organization | Santronics Software, Inc. |
| Message-ID | <[email protected]> |
Frank Ellermann wrote:
> 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) 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).
Sender predates PRA so how can PRA regulate it?
> Example: Charles + Scott as authors (2822-From) post an answer
> to a mailing list (with 2822-Sender Scott), what's the mailing
> list software supposed to do if it doesn't support a 4406 PRA ?
>
> Frank (cc rfc822, maybe it's not exactly a DKIM question)
Unless I am mis-understanding here, if so, I apologize for jumping in ....
No, for a mailing list, Sender: is generally the mailing list's "Pseudo
Admin Agent", like for this list IETF-DKIM message:
Sender: [email protected]
or like in our setup in our support lists:
Sender: [email protected]
So Scott should not be in the Sender: field.
The key thing is that it should never be part of a HUMAN reply process,
and as far I recall in our various MUA testing, none include it in a
"Reply To All" concept. IMO, this is one reason why the PRA algorithm
is flawed.
--
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com