Agreed there's risk in HTML hiding content and showing malicious things but that risk has existed before. An updated DKIM authenticator could help us understand who did those malicious updates along some forwarding path.
I'm pretty sure that changing DKIM is very out of scope for this working group.
We have a decade of experience with DKIM. If l= were useful, someone would have figured it out by now.
R's, John _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
