File formats:

Status:

INFORMATIONAL

Authors:

F. Martin, Ed.
E. Lear, Ed.
T. Draegen, Ed.
E. Zwicky, Ed.
K. Andersen, Ed.

Stream:

IETF

Source:

dmarc (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7960

Discuss this RFC: Send questions or comments to the mailing list dmarc@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7960

Abstract

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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.