On 29/06/2026 19:49, John R Levine wrote:
On Mon, 29 Jun 2026, Alessandro Vesely wrote:
And this brings us nicely back to the main topic, since that 1% is precisely the traffic for which ARC was devised.  Is it bound to be rounded away or to be properly dealt with?

I would prefer to stop beating this dead horse.  We all know where to find the DKIM2 discussions in the DKIM WG.

I thought we are here to discuss why ARC failed to fix the mailing list problem.  Discussions in the DKIM WG don't seem to cover this point.

Aw, come on.   Trent's draft explains why ARC failed.  I realize you don't agree with it but I'm pretty sure you're in the rough here.


Yet, abstaining from discussion is not the same as replying. The argument has not been unfolded.


As I would have thought everyone here was aware, DKIM2 sort of combines DKIM and ARC to provide a chain of custody that receivers can verify without having to trust any of the signers at intermediate hops not to lie.


That's certainly a great improvement, but mailing lists won't have any knowledge of what software is installed at their subscribers' MXes, therefore, they'll have to keep on munging or risk having their emails rejected.

Those who will benefit from DKIM2 verification may want to enable unmunging the From:'s. This perspective is not optimal, as it bypasses the author's domain DMARC policy during transfer. Furthermore, DKIM2 differences do not appear to guarantee semantic integrity, so the restored From: header may be misleading.


Best
Ale
--




_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to