DMARC Escape
draft-otis-dmarc-escape-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Douglas Otis | ||
Last updated | 2015-12-09 (Latest revision 2015-06-07) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
DMARC assumes the From header field has the combined role of Author and Sender or that it shares the same domain as that of the Sender. Message delivery becomes unreliable and the Author role may be supplanted as services adapt to DMARC's incompatible policies affecting otherwise valid and well formed messages. This document recommends two methods to allow DMARC to be compatible with RFC5322.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)