Hello, On Mon, 13 Apr 2020, Christopher Faylor wrote:
> On Wed, Apr 08, 2020 at 04:15:27PM -0500, Segher Boessenkool wrote: > >On Wed, Apr 08, 2020 at 01:50:51PM +0000, Michael Matz wrote: > >>On Wed, 8 Apr 2020, Mark Wielaard wrote: > >>>Earlier versions of Mainman2 had some issues which might accidentally > >>>change some headers. But the latest fixes make this possible. It is > >>>how the FSF handles DMARC for various GNU mailinglists (by NOT > >>>modifying the headers and body and passing through the DKIM > >>>signatures): > >>>https://lists.gnu.org/archive/html/savannah-hackers-public/2019-06/msg00018.html > >> > >>Oh, that would be nice to have at sourceware.org. Please? :-) > > > >Yes, please please please, can we have this? > > In case it isn't obvious, we are already running the latest available > version of mailman 2. I think that means that dmarc_moderation_action: "Munge From" can simply be switched off then (at least I don't see which other headers e.g. gcc@ is rewriting that would cause DMARC to scream; and if there are any, then it would be better to disable those as well. Same with any potential body rewriting that might still happen). I would offer help testing that this doesn't cause delivery issues, e.g. on some test email list, but it seems none of my domains is DMARC-infected :-/ Ciao, Michael. P.S: I wonder btw. why the From munging is enabled also for p=none domains like redhat.com. The RFC says this is to be used for gathering DMARC feedback, not requiring any specific action for the mail text itself on the sender or receiver. But an answer to this would be moot with the above non-munging of From.
