RFC 7372: Email Authentication Status Codes
In plain English — editorial summary, not part of the RFC
This document registers code points to allow status codes to be returned to an email client to indicate that a message is being rejected or deferred specifically because of email authentication failures. This document updates RFC 7208, since some of the code points registered replace the ones recommended for use in that document.
Document record
- Document ID
- RFC7372
- Published
- September 2014
- Authors
- M. Kucherawy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 7208
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7374Service Discovery Usage for REsource LOcation And Discovery (RELOAD)Current
October 2014
- RFC 7375Secure Telephone Identity Threat ModelCurrent
October 2014
- RFC 7377IMAP4 Multimailbox SEARCH ExtensionCurrent
October 2014
- RFC 7378Trustworthy LocationCurrent
December 2014
- RFC 7380RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG2 Transport Stream (TS) Program Specific Information (PSI) Decodability Statistics Metrics ReportingCurrent
November 2014
- RFC 7363Self-Tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)Current
September 2014
- RFC 7362Latching: Hosted NAT Traversal (HNT) for Media in Real-Time CommunicationCurrent
September 2014
- RFC 7386JSON Merge PatchObsoleted
October 2014
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?