RFC 3463: Enhanced Mail System Status Codes
In plain English — editorial summary, not part of the RFC
This document defines a set of extended status codes for use within the mail system for delivery status reports, tracking, and improved diagnostics. In combination with other information provided in the Delivery Status Notification (DSN) delivery report, these codes facilitate media and language independent rendering of message delivery status. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3463
- Published
- January 2003
- Authors
- G. Vaudreuil
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 16
- Also known as
- —
- Obsoletes:
- RFC 1893
Topics
Referenced by
5 later RFCs formally update or obsolete part of this document.
- RFC 3886An Extensible Message Format for Message Tracking ResponsesCurrent
September 2004
- RFC 4468Message Submission BURL ExtensionUpdated
May 2006
- RFC 4865SMTP Submission Service Extension for Future Message ReleaseCurrent
May 2007
- RFC 4954SMTP Service Extension for AuthenticationUpdated
July 2007
- RFC 5248A Registry for SMTP Enhanced Mail System Status CodesCurrent
June 2008
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent
July 2004
- RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent
September 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 2821Simple Mail Transfer ProtocolObsoleted
April 2001
- RFC 3207SMTP Service Extension for Secure SMTP over Transport Layer SecurityUpdated
February 2002
- RFC 3030SMTP Service Extensions for Transmission of Large and Binary MIME MessagesCurrent
December 2000
- RFC 2852Deliver By SMTP Service ExtensionCurrent
June 2000
- RFC 2476Message SubmissionObsoleted
December 1998
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?