An Extensible Message Format for Delivery Status Notifications
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 40
- Abstract
- This memo defines a Multipurpose Internet Mail Extensions (MIME) content-type that may be used by a message transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a message to one or more recipients. This content-type is intended as a machine-processable replacement for the various types of delivery status notifications currently used in Internet electronic mail. Because many messages are sent between the Internet and other messaging systems (such as X.400 or the so-called "Local Area Network (LAN)-based" systems), the Delivery Status Notification (DSN) protocol is designed to be useful in a multi-protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign" addresses and error codes, in addition to those normally used in Internet mail. Additional attributes may also be defined to support "tunneling" of foreign notifications through Internet mail. [STANDARDS-TRACK]
- Publication Date
- 2003-01-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC3464- Link
- https://doi.org/10.17487/RFC3464
- Author(s)
- Keith MooreGregory Vaudreuil
- Keyword(s)
- DSN, MIME, Content Type
Latest version of IETF RFC 3464
Document Versions — IETF RFC 3464
-
▶ IETF RFC 3464 (2003-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 821 [Superseded*]
- IETF RFC 822 [Superseded*]
- IETF RFC 1047 [Active*]
- IETF RFC 1123 [Active*]
- IETF RFC 1894 [Superseded*]
- IETF RFC 2045 [Active*]
- IETF RFC 2047 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 3461 [Active*]
- IETF RFC 3462 [Superseded*]
- IETF RFC 3463 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3464.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3464, An Extensible Message Format for Delivery Status Notifications. Available at https://doi.org/10.17487/RFC3464
Snippet:
IETF RFC 3464, An Extensible Message Format for Delivery Status Notifications. Available at https://doi.org/10.17487/RFC3464
HTML (ISO 690 compliant)
Preview:
IETF RFC 3464, An Extensible Message Format for Delivery Status Notifications. Available at https://doi.org/10.17487/RFC3464
Snippet:
<span class="citation"><cite>IETF RFC 3464</cite>, An Extensible Message Format for Delivery Status Notifications. Available at <a href="https://doi.org/10.17487/RFC3464" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3464</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3464, An Extensible Message Format for Delivery Status Notifications
doi: 10.17487/RFC3464
url: https://doi.org/10.17487/RFC3464
doi: 10.17487/RFC3464
url: https://doi.org/10.17487/RFC3464
Snippet:
<li> <cite id="bib-rfc3464">IETF RFC 3464</cite>, An Extensible Message Format for Delivery Status Notifications <span class="doi">10.17487/RFC3464</span> </li>
Referenced By
- IETF RFC 3461 [Active*]
- IETF RFC 3462 [Superseded*]
- IETF RFC 3463 [Active*]
- IETF RFC 3798 [Superseded*]
- IETF RFC 3801 [Active*]
- IETF RFC 3886 [Active*]
- IETF RFC 4408 [Superseded*]
- IETF RFC 4952 [Superseded*]
- IETF RFC 5321 [Active*]
- IETF RFC 5336 [Superseded*]
- IETF RFC 5429 [Active*]
- IETF RFC 5598 [Active*]
- IETF RFC 6522 [Active*]
- IETF RFC 6530 [Active*]
- IETF RFC 6531 [Active*]
- IETF RFC 6533 [Active*]
- IETF RFC 8098 [Active*]