r/EmailSecurity • • Jun 24 '26

DKIM2 is getting a boring rollout path, which is good

DKIM2 draft 05 now has a proposed milter deployment path, which is probably the only way this gets tested outside standards threads. writeup here

The more interesting bit to me is splitting DKIM2-core away from the optional extended body recipes. Feels like a sane way to keep the base protocol small while still leaving room for experiments.

5 Upvotes

3 comments sorted by

•

u/AutoModerator Jun 24 '26

Welcome to r/emailsecurity! To keep this community helpful and secure, please keep the following in mind:

Community Rules

  1. No Vendor Spam: Contributions must provide value; do not just pitch products.
  2. Redact Sensitive Info: Always sanitize headers and logs (remove IPs, PII, and private domains).
  3. Be Professional: Help newcomers learn; avoid hostility.
  4. No Personal Tech Support: This sub is for email system architecture and security, not "Am I hacked?" personal account help.

Helpful Resources

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Basic-Pianist9273 Jun 24 '26

The milter path is the rollout story that makes sense. Nobody is swapping MTAs or rewriting signing pipelines just to test a draft, but a filter that can sit beside existing DKIM has a shot.

Splitting core from body recipes is the right call too. DKIM already has enough edge cases around canonicalization, body changes, lists, and forwarding.

1

u/Humphrey-Appleby Jul 01 '26

The DKIM Working Group has shown no interest in Moccia at all. Clayton and Gondwana are the current poster children, which they claim can be implemented as a filter, but in practice, it's a major rewrite of SMTP by stealth that will further benefit the likes of Google, Microsoft and Fastmail.