Re: [Mailman-Users] Message-ID required - was: Reply-to options not working

2018-02-06 Thread Dimitri Maziuk
On 2018-02-06 04:09, Stephen J. Turnbull wrote: Do you have something to add to that, or disagree with that? I said it was what *I* believe, not what IETF believes. Dima -- Mailman-Users mailing list Mailman-Users@python.org

Re: [Mailman-Users] Message-ID required - was: Reply-to options not working

2018-02-06 Thread Stephen J. Turnbull
Dimitri Maziuk writes: > Heh. I personally believe that a message sent by a mailing list > *must* have the mailing list as the originator: dkim, id, and > whatever else. First, please be careful with terminology. *Originator* is well-defined (RFC 5598) as the agent of the Author that first

Re: [Mailman-Users] Message-ID required

2018-02-06 Thread Stephen J. Turnbull
Mark Sapiro writes: > On 02/05/2018 12:22 AM, Stephen J. Turnbull wrote: > > > > According to RFC, Message-ID is an originator field, and MUST be > > present and MUST be unique. > > Do you have a reference for this? I thought this was correct, but I > recently looked it up in RFC 5322 and

Re: [Mailman-Users] Message-ID required - was: Reply-to options not working

2018-02-05 Thread Dimitri Maziuk
On 02/05/2018 11:55 AM, Mark Sapiro wrote: > On 02/05/2018 12:22 AM, Stephen J. Turnbull wrote: >> >> According to RFC, Message-ID is an originator field, and MUST be >> present and MUST be unique. > > Do you have a reference for this? I thought this was correct, but I > recently looked it up in

Re: [Mailman-Users] Message-ID required - was: Reply-to options not working

2018-02-05 Thread Mark Sapiro
On 02/05/2018 12:22 AM, Stephen J. Turnbull wrote: > > According to RFC, Message-ID is an originator field, and MUST be > present and MUST be unique. Do you have a reference for this? I thought this was correct, but I recently looked it up in RFC 5322 and predecessors (see