Re: [mlmmj] Mailing Lists and DKIM signing breaking when sender DKIM policy is REJECT

Baptiste Daroussin <[email protected]> Tue, 9 Apr 2024 10:46:27 +0200
Newsgroups org.mlmmj.mlmmj
Message-ID <akzm25ybse7v7m24fd3qt3glhi3j2khyvnpd43n7f2mvbqp4pz@h2hhcdwasj3a>
On Tue 09 Apr 09:40, Christof Thalhofer wrote:
> Am 09.04.24 um 00:23 schrieb Kent:
> 
> > I note this mailing list:
> > 
> > 1) Modifies the 'Subject' by inserting [mlmmj] at the start - this
> > will invalidate the original senders dkim.
> > 
> > 2) Sets the 'Sender:' header, however this didn't make any difference
> > when I used 'Reply'  It wasn't until I clicked 'Reply All' that the
> > list was added as a recipient (and the Cc recipient) and hence why I
> > was originally setting the 'Reply-To:' header.
> 
> I'm not the maintainer of this ML. Seems that it's a long time ago since it
> was configured and so it 'naturally' filters out every Gmail account that
> bounces.

If only I had access to the website and the mailing list I would reconfigure it
to be dkim compliant but also update the website to actually tell about the
1.4.x series.
> 
> > What's the process to request a flag to make this option available ?
> > 
> > As much as I avoid Google myself, the enforcing by Google and Yahoo
> > of SPF, DKIM and DMARC means you are needing to do what they do like
> > it or not, and their own mailing lists are From-munging !
> 
> If you want to do From-munging then Mlmmj is the wrong software for you.
> Sympa can do that but that's another beast.
> 
> I configured my mailinglists so that the original DKIM signatures are kept
> (no prefix, no footer, no extra Reply-To) and wrote in
> 'control/customheaders':
> 

You can configure From-munging with mlmmj, but yes this is not in mlmmj. you
will need mlmmj 1.4.x which supports X-Original-From and configure something
before mlmmj reception like rspamd which will do the munging and move the From
into the X-Original-From.

rspamd will only munge when the email is sent from a sender which has a very
restrictive DMARC policy.

In rspamd the configuration is easy:

in dmarc.conf:
```
munging {
	list_map =  "/usr/local/mlmmj/rspamd-munging";
	mitigate_strict_only = true;
}
```


in rspamd-munging files you have the list address you expect to munge from.

Note that this feature was specifically designed for mlmmj :D
https://github.com/rspamd/rspamd/issues/3647

This was done to help migration from mailman to mlmmj for the FreeBSD project

We don't use it anymore in the FreeBSD project as we don't alter anymore fields
use in the dkim signatures.

> > Precedence: list List-Id: User Mailing List <user.example.com>
> > List-Unsubscribe: <https://example.com/>,
> > <mailto:[email protected]?subject=unsubscribe> List-Post:
> > <mailto:[email protected]> List-Help:
> > <mailto:[email protected]?subject=help> List-Subscribe:
> > <http://example.com/>,
> > <mailto:[email protected]?subject=subscribe> Sender:
> > <[email protected]> Mail-Followup-To: <[email protected]>
> 
> The 'Mail-Followup-To:'-header makes it possible that Gmail-Users can hit
> Reply-to-all to answer to the list.
> 
> And then I said to the users they should answer to the list or to all and
> filter their mail for 'To: [email protected]' and that works now.
> 
I did not know the Mail-Followup-To trick, I will look into it ;)

Best regards,
Bapt