💭 we know when a mailing list successfully delivered our messages, because we get a DMARC report for disallowed forwarding lol
@ireneista there are multiple well-understood ways to solve this problem and many mailing lists implement them; DKIM/DMARC incompatibility is specifically an artifact of older list software or configuration: https://wiki.list.org/DEV/DMARC?highlight=%28DMARC%29 https://www.lsoft.com/manuals/17.0/advancedtopics/133HowdoesLISTSERVcomplywithDMAR.html
the "munge sender" option also can improve privacy by avoiding exposing the sender's actual email address publicly
@rcombs@treehouse.systems @ireneista@irenes.space The most straightfoward if the mail is DKIM1 signed is
- Munge envelope From with SRS (just redirection) or VERP (mailing list, for backscatter detection)
- Do not modify any signed message fields
- Do not modify the mbody
If you insist on body munging then yes, you need to start modifying the Form header
@rcombs@treehouse.systems @ireneista@irenes.space Now if someone has DMARC p=reject/quarantine and no DKIM you're in for a world of pain because they've made their email unforwardable. This is somewhat of a skill issue on their part, but you may need to cope with it
@erincandescent @ireneista isn't that still a non-issue if you either munge message-from or mime-wrap?
no, but for real, the fact that this is expected behavior for any sort of mailing list, while also being expressly forbidden by spam-prevention mechanisms, really demonstrates that these mechanisms are not about user well-being.