Mitigating DMARC damage to third party mail
DMARC is an anti-phishing technology. It has recently been repurposed by large mail providers for public webmail domains.
DMARC alignment requires that the From: line address in a mail message match either a DKIM signature d= domain, or an SPF-validated bounce address domain. Depending on a domain's published policy, unaligned mail may be quarantined, i.e. relegated to the spam folder or rejected by recipient systems. Mailing lists and other software that send legitimate but unaligned mail often find that mail rejected. Problems include recipients not getting the mail they want, and in some cases the normal list bounce processing removes the recipients from lists.
- 1 ML-side workarounds
- 2 Cooperative solutions
Techniques which can be applied by any mailing list operator unilaterally.
Exclude domains that require alignment
Check the DMARC policy on incoming mail, and refuse mail from domains with quarantine or reject polcies.
- Users in affected domains have to get new addresses or leave.
- Operation otherwise unaffected.
Turn off all message modifications
Disable subject tags, message footers, and anything else that might break a DKIM signature.
- Still doesn't work for domains that validate mail with SPF
- Users can't recognize list mail by subject tags or anything else.
- Sorting by subject tags doesn't work.
- Often impractical when footers have mandated content.
Replace address with a generic one
Lists rewrite the From: line to use the list's address rather than the author's, either for all mail, or for mail from domains with policies.
Address may be moved into address comment, e.g.
From: foo list for mmeyer-at-yahoo.com <email@example.com>
Author's address may be placed in a Reply-To: header, give or take the usual issues about lists and Reply-To.
- Reply to author unavailable without Reply-To:
- Address book techniques based on recognizing From: address don't work or work differently.
- Author not visible in MUA message list.
- Mail sorting rules don't work the same.
- Encourages phishing by training users that address in the comment is equivalent to address.
Add fixed string such as .invalid to addresses
Add a suffix to From: line addresses with policies.
From: Marissa <firstname.lastname@example.org>
- Sorting rules might break depending on match details
- Reply to author requires usenet-style demunging
- Encourages phishing by training users that munged address is equivalent to address.
Rewrite addresses to forwarding addresses
Rewrite addresses to a valid address that will forward to the original address, either using a wildcard domain suffix or a pseudorandom address.
From: Marissa <email@example.com>
From: Marissa <firstname.lastname@example.org>
- List function largely unchanged
- Requires list operator to run a forwarder, which must be managed to avoid relaying spam
- Encourages phishing by training users that modified address is equivalent to address.
Wrap each message in an outer message, similar to single-message digests.
- Looks like digests to users unless they have (so far nonexistent) MUA unwrapping extensions
- May encourage phishing depending on how MUA displays message.
Require all users, or users on recipient systems that enforce DMARC, to get list mail as digests
- All the usual reasons people don't like digests, mail is delayed until the digest is sent, replying to individual messages is harder, replying to the whole digest loses threads, etc.
Ignore DMARC bounces
Check for DMARC codes in bounce messages and disregard them for list management.
- Recipients lose mail
- Bounces may affect list reputation and delivery
Techniques which need mutual cooperation in order to work.
Third party maintains DMARC-bypass whitelist of IPs and/or DKIM signatures of senders who send legitimate unaligned mail. Could probably seed with forwarders known to large mail systems. Probably wouldn't be absolute whitelist, just skip DMARC alignment check.
- Someone has to do it.
- Eligible senders need to find out about it and apply, if not seeded.
- Could allow more spam or phish depending on how careful forwarders are.
Per sender whitelist
Senders publish list of DKIM signatures allowed to send for them, like in RFC 6541.
- A lot of work for each sender
- Large senders unlikely to know all of the third parties that their users use.
Remailers include a header reporting on the authentication of the incoming message
- Since the header is trivially forgable, recipients have to know who to trust. (See whitelist above.)
- List operation unaffected if it works.
Original sender includes a header with a signed token that identifies the relay.
- A variety of bad things if the relay tries to play games.
- Senders will probably only want to include them in mail to trustworthy relays. (See whitelist above.)