RFC 5248: A Registry for SMTP Enhanced Mail System Status Codes
In plain English — editorial summary, not part of the RFC
The specification for enhanced mail system status codes, RFC 3463, establishes a new code model and lists a collection of status codes. While it anticipated that more codes would be added over time, it did not provide an explicit mechanism for registering and tracking those codes. This document specifies an IANA registry for mail system enhanced status codes, and initializes that registry with the codes so far established in published standards-track documents, as well as other codes that have become established in the industry. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5248
- Published
- June 2008
- Authors
- T. Hansen; J. Klensin
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- BCP138
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4865SMTP Submission Service Extension for Future Message ReleaseCurrent
May 2007
- RFC 4406Sender ID: Authenticating E-MailCurrent
April 2006
- RFC 4141SMTP and MIME Extensions for Content ConversionCurrent
November 2005
- RFC 4130MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)Current
July 2005
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent
September 2004
- RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent
July 2004
- RFC 3461Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)Updated
January 2003
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?