On 4/9/20 9:33 AM, Lindsay Haisley wrote:
This is actually a common, legitimate technique for dealing with DMARC mitigation issues on mailing lists and mail redirections.
Yes, re-writing the From: address is a common technique. How it's re-written is important. (See below.)
I don't know if SA has the ability to fully parse an email address based on RFC-2822 criteria, but this would be what's necessary.
It's my understanding that SpamAssassin already knows the difference in the email address and the human friendly name parts. Please elaborate on what else SpamAssassin needs to know about and do.
The Mailman code substitutes the word "at" in the comment field for the ampersand to avoid this sort of problem, but other implementation may not.I have seen many others suggest NOT using a format recognizable as an actual email address, <user>@<domain>.<tld>, inside of the human friendly name, specifically to avoid collisions like this. I've been suggesting the same. I personally like "name - <user> at <domain>.<tld>" <email address>. It gives the information for someone to be able to reconstruct the email address if they want to.
I also quite frequently see "name via <list>". But sadly that doesn't give the email address information.
But avoid the recognizable RegExable email address in the human friendly name.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
