Re: [mlmmj] Problem with mail sent by @orange.fr to @protonmail.com

Baptiste Daroussin <[email protected]> Tue, 28 Nov 2023 17:06:12 +0100
Newsgroups org.mlmmj.mlmmj
Message-ID <ctexrm2bjkzeaslilgkvdwc2pwkhy6x6h7aqmgag6gdr5b5o6b@ih4iyoij5uxp>
On Tue, Nov 28, 2023 at 10:58:13AM -0500, Konstantin Ryabitsev wrote:
> On Mon, Nov 27, 2023 at 10:55:22PM +0100, Baptiste Daroussin wrote:
> > Well if you don t alter the email (no subject modifications for example)
> 
> So, can we stop the mlmmj list from doing this? :)

I would love to and this will simplify a lot some part of the code ;)
> 
> > I first went down the "munging from" path using rspamd in front of mlmmj
> > (hence the new feature of suporting X_ORIGINAL_FROM in mlmmj 1.4.0). But
> > then realised that if I stop altering the emails (just play with custom
> > headers) then the dkim signatures remains valid and all mail providers do
> > accept the emails as only being relayed.
> 
> This should continue to work for a while, but soon we'll need to work on being
> conformant with DARA [1], which will require adding Forwarded-To: headers and
> ARC-signing every outgoing message. Yes, this means that if your mailing list
> has 5,000 subscribers, you'll need to cryptographically sign 5,000 individual
> messages.
> 
> We probably have a couple of years before that starts being relevant, though.

Forwarded to is something that can be easily implemented in mlmmj, I will add it
to the todo list for 1.5

As for the signature, it will be up to the smtp setup to to it, meaning mlmmj
should be easily compliant to this rule.
> 
> -K
> 
> [1] https://datatracker.ietf.org/doc/draft-chuang-replay-resistant-arc/