RFC 7960: Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows
In plain English — editorial summary, not part of the RFC
Domain-based Message Authentication, Reporting, and Conformance (DMARC) introduces a mechanism for expressing domain-level policies and preferences for email message validation, disposition, and reporting. However, the DMARC mechanism enables potentially disruptive interoperability issues when messages do not flow directly from the author's administrative domain to the final Recipients. Collectively, these email flows are referred to as "indirect email flows". This document describes these interoperability issues and presents possible methods for addressing them.
Document record
- Document ID
- RFC7960
- Published
- September 2016
- Authors
- F. Martin; E. Lear; T. Draegen; E. Zwicky; K. Andersen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9991Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure ReportingCurrent
May 2026
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
- RFC 8601Message Header Field for Indicating Message Authentication StatusCurrent
May 2019
- RFC 8617The Authenticated Received Chain (ARC) ProtocolCurrent
July 2019
- RFC 7001Message Header Field for Indicating Message Authentication StatusObsoleted
September 2013
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?