IETF mail transition changes address rewriting for DMARC
The IETF’s September mail transition rewrites addresses according to SPF and DMARC policies. Teams using its lists should check headers and replies.
What changed
The IETF completed its email infrastructure transition on 11 September 2026, covering ietf.org, iab.org, irtf.org and rfc-editor.org, including mailing lists. Its announcement was first published on 28 August and updated on 11 September to confirm completion.
Why From addresses may look different
The new service checks sending domains’ SPF and DMARC policies. For domains with p=reject or p=quarantine, it rewrites the visible From address to the corresponding IETF-operated dmarc. subdomain, then signs with DKIM. The envelope sender is also rewritten when its domain’s SPF policy excludes the IETF’s outbound servers.
For example, the announcement shows dane@email.example becoming dane=40email.example@dmarc.ietf.org for delivery through an IETF list. This is an operational change to those services, not a new authentication standard or a requirement for every domain.
What administrators should check
Teams using these lists should inspect delivered messages’ From, Return-Path, DKIM signing domain and authentication results, and test replies. Keep your domain’s enforcement policy in place; investigate unexpected filtering or reply failures using the actual message headers.
Sources
Sources reviewed .