Make alignment solid
When you originate a message, DKIM2 requires three things to line up:
- the envelope sender (
5321.MAIL FROM), - the
From:header (5322.From), - the signing domain (
d=).
DMARC through DKIM already needs From and
d= aligned; DKIM2 adds the envelope sender.
Watch out: if you pass DMARC only through an
aligned SPF, that won’t carry over — DKIM2 needs DKIM
alignment.
ESPs, bounces and feedback
- Using an ESP? They sign on your behalf (you
publish a key, or a CNAME delegated to them), or they rewrite your
Frominto a domain they control. Most ESP customers need do nothing. - Expect more asynchronous bounces. DKIM2 makes bounces safe to send after the connection closes, and the chain routes them home — make sure your bounce processing can handle them.
- Want handling feedback? Ask for it with the
f=feedbackflag. The report format is still being defined.
What should your organization do now?
- Get DKIM keys first. Only SPF, or nothing at all? Start DKIM-signing with aligned keys now — DKIM2 builds on them.
- Pick an owner. Decide who in your organization owns DKIM2.
- Map your modifications. Find where your pipeline changes content, rewrites addresses, or expands one message to many recipients — and cut changes you don’t need. Every change you make is one you’ll be accountable for.
- Plan your signing workflow. Where you verify incoming signatures, drop invalid ones, add your own, and extend existing chains.
- Ask your vendors. MTA, ESP and gateway vendors: what’s their DKIM2 implementation and interop plan? See the software that already supports DKIM2.
To see how it all fits together, read how DKIM2 works, or try it against the addresses on this host.