Sender Authentication Best Practices
draft-fosterd-dmarc-spf-best-practices-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Douglas Foster | ||
| Last updated | 2023-11-14 (Latest revision 2023-05-13) | ||
| 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
Sender Authentication contributes to the goal of detecting and blocking maliciously impersonated email identifiers. Sender Policy Framework (SPF) (RFC 7208) validates the RFC5321.MailFrom address, and Domain-based Message Authentication, Reporting, and Conformance (DMARC) (RFC 7489) validates the RFC5322.From header address. Both techniques may produce a result other than PASS on a message that the recipient considers acceptable and wanted. This document describes best practices for integrating SPF and DMARC into an email filtering strategy.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)