Visual RFC.
ALL RFCs / RFC 7489
Read the RFC ↗
RFC 7489 / MECHANISM GUIDE

Mailing lists and limitations

05

Forwarding and message transformations can disrupt the authentication paths DMARC depends on.

This guide explains the 2015 publication. Superseded by RFC 9989, RFC 9990, RFC 9991.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 7489 · § 10.5EXAMPLE
3 / 3
Mailing lists and limitationsForwarding and message transformations can disrupt the authentication paths DMARC depends on.Mailing lists and limitationsOriginal aligned messageforwarded from new IPSPF path can breakList footer can also break DKIMHistorical rules: see the 2026 successor set
03
Assess failure carefully

Use authentication evidence and receiver policy without treating every failure as proof of malice.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Forwarding can break SPF; body/header modifications can break DKIM.

  • Forwarding can break SPF; body/header modifications can break DKIM.
  • Alignment prevents an unrelated domain’s pass from authenticating the visible From.
  • DMARC does not detect every impersonation or lookalike-domain attack.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Visible author and alignment
  2. Discover domain policy
  3. Pass and policy disposition
  4. Aggregate and failure reports
  5. Mailing lists and limitations
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗