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 RFC 5322 and predecessors (see > <https://lists.mailman3.org/archives/list/mailman-us...@mailman3.org/thread/UCH46WS4RII5HKZWGQTBUDUHZMJZDFNC/>, > and those RFCs at least say it's optional and SHOULD be present.
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. And then there *should* be a way to reply "off list". Of course then you have to preserve the original originator all the way to the beginning, so... And even if "Message-ID MUST be present and MUST be unique", that doesn't make the converse true: that two copies of the same message *must* carry the same Message-ID. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
