RFC 3464: An Extensible Message Format for Delivery Status Notifications
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC3464
- Published
- January 2003
- Authors
- K. Moore; G. Vaudreuil
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 40
- Also known as
- —
- Obsoletes:
- RFC 1894
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3420Internet Media Type message/sipfragCurrent
November 2002
- RFC 3555MIME Type Registration of RTP Payload FormatsObsoleted
July 2003
- RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent
September 2002
- RFC 3302Tag Image File Format (TIFF) - image/tiff MIME Sub-type RegistrationCurrent
September 2002
- RFC 3745MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)Current
April 2004
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current
July 2004
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?