Interoperability Issues Between DMARC and Indirect Email Flows

Document Type Replaced Internet-Draft (dmarc WG)
Authors Franck Martin  , Eliot Lear  , Tim Draegen 
Last updated 2015-10-14 (latest revision 2015-01-19)
Replaced by RFC 7960
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Adopted for WG Info Only
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-dmarc-interoperability
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


DMARC introduces a mechanism for expressing domain-level policies and preferences for message validation, disposition, and reporting. The DMARC mechanism can encounter interoperability issues when messages originate from third party sources, are modified in transit, or are forwarded enroute to their final destination. Collectively these email flows are referred to as indirect email flows. This document describes interoperability issues between DMARC and indirect email flows. Possible methods for addressing interoperability issues are presented.


Franck Martin (
Eliot Lear (
Tim Draegen (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)