15 Oct
2021
15 Oct
'21
10:05 a.m.
Philip Colmer writes:
The situation we're seeing is that if person A sends an email from a Google account to Mailman 3 and receives the (modified) post back from Mailman 3, the message ID is not being changed. Google's behaviour then is not to show that message to the user because it thinks it is the same message that the user sent out.
Google is broken, but they're not going to change.
Since Mailman 3 is modifying the message, it ought to have a different message ID.
I don't think your posters would agree that Mailman is the author of their posts.
The IETF has addressed the issue of non-identical but equivalent messages with the Resent-Message-ID field (and in general the whole suite of Resent-* fields.
Steve