Summary: | mailman: Comply better with DKIM | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Michael Tremer <michael.tremer> |
Component: | Mail & Mailing Lists | Assignee: | Peter Müller <peter.mueller> |
Status: | CLOSED WORKSFORME | QA Contact: | Michael Tremer <michael.tremer> |
Severity: | - Unknown - | ||
Priority: | - Unknown - | CC: | peter.mueller |
Version: | unspecified | ||
Hardware: | unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugzilla.ipfire.org/show_bug.cgi?id=11765 | ||
Bug Depends on: | |||
Bug Blocks: | 11634 |
Description
Michael Tremer
2018-02-21 14:13:31 UTC
Mailman needs to be updated so I am afraid we will have to build it ourselves. As far as I am concerned, if a mailing list does not alter messages by adding footers or rewriting subjects, Mailman is now DKIM-compliant. @Michael: Please confirm. :-) (In reply to Peter Müller from comment #2) > @Michael: Please confirm. :-) Confirm what again? Except for some mails which Mailman processes in a way it renders DKIM signatures invalid, it is now DMARC compliant. Unfortunately, this kind of thing does not seem to be reproducible or deterministic, so I am leaving this opened for further investigations. I am not sure what we can do about this here. I do not want to wrap the messages into a new one. That brings all other sorts of problems. Sender: and the envelope sender should allow us to sign any messages. I am not sure if there is any improvement in Mailman 3, although I much more prefer Mailman 2. Closing this as WORKSFORME, since we run a "quarantine" DMARC policy for quite some time now, and I am unaware of any DKIM-caused issues with it. |