The purpose of this document is to recommend ways to make email messages DMARC compliant and to explain how and why messages are rewritten for DMARC compliance
Note: The WiscList team plans to modify all lists to support DMARC.
Your list needs to rewrite the From header of messages so that they use the same domain as the list server (@lists.wisc.edu). If you do not do this, receiving systems will quarantine or reject messages sent through the list for any senders who have DMARC-protected domains.
In the WiscList admin site, go to Utilities → List Settings → Email Submitted Content → Header Rewrites
Use the following settings to ensure the From header uses the following format:
"'Bucky Badger' via listname"
"'%%merge inmail_.hdrfrom_%%' via %%list.name%%" <%%email.list%%>
"'%%author.nameemail%%' via %%list.name%%" <%%email.list%%>
Change the Reply-to option to “author” so that Reply-all can be used by recipients to reply back to the list as well as the original message’s author.
Messages sent via WiscList will pass SPF for @lists.wisc.edu. DMARC will pass as a result. Ensure that the From header of messages sent via your list use the @lists.wisc.edu domain so that DMARC alignment occurs.
Once WiscList starts DKIM signing messages it means that messages sent via WiscList, with the From header domain matching @lists.wisc.edu, will help ensure DMARC passes in the event that SPF fails (typically this occurs when messages are forwarded).
Google Groups will automatically rewrite the From header to the following format if the sender’s domain publishes a DMARC record with a quarantine or reject policy:
"’Bucky Badger’ via listname"
Messages sent via UW-Madison Google Groups will pass SPF for @g-groups.wisc.edu, and the messages will be signed with a DKIM selector in the g-groups.wisc.edu domain. DMARC will pass as a result.