Message Disposition Notification
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 30
- Abstract
- This memo defines a MIME content-type that may be used by a mail user agent (MUA) or electronic mail gateway to report the disposition of a message after it has been successfully delivered to a recipient. This content-type is intended to be machine-processable. Additional message headers are also defined to permit Message Disposition Notifications (MDNs) to be requested by the sender of a message. The purpose is to extend Internet Mail to support functionality often found in other messaging systems, such as X.400 and the proprietary "LAN-based" systems, and often referred to as "read receipts," "acknowledgements", or "receipt notifications." The intention is to do this while respecting privacy concerns, which have often been expressed when such functions have been discussed in the past. Because many messages are sent between the Internet and other messaging systems (such as X.400 or the proprietary "LAN-based" systems), the MDN 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, 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
- 2004-05-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC3798- Link
- https://doi.org/10.17487/RFC3798
- Author(s)
- Tony HansenGregory Vaudreuil
- Keyword(s)
- Message Disposition Notifications, MDN, Media Type, MIME, Multipurpose Internet Mail Extensions
Latest version of IETF RFC 3798
Document Versions — IETF RFC 3798
-
▶ IETF RFC 3798 (2004-05-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2047 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2821 [Superseded*]
- IETF RFC 2822 [Superseded*]
- IETF RFC 3461 [Active*]
- IETF RFC 3462 [Superseded*]
- IETF RFC 3464 [Active*]
Bibliographic Reference(s)
- IETF RFC 2298 [Superseded*]
- IETF RFC 2634 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3798.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 3798, Message Disposition Notification. Available at https://doi.org/10.17487/RFC3798
Snippet:
IETF RFC 3798, Message Disposition Notification. Available at https://doi.org/10.17487/RFC3798
HTML (ISO 690 compliant)
Preview:
IETF RFC 3798, Message Disposition Notification. Available at https://doi.org/10.17487/RFC3798
Snippet:
<span class="citation"><cite>IETF RFC 3798</cite>, Message Disposition Notification. Available at <a href="https://doi.org/10.17487/RFC3798" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3798</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3798, Message Disposition Notification
doi: 10.17487/RFC3798
url: https://doi.org/10.17487/RFC3798
doi: 10.17487/RFC3798
url: https://doi.org/10.17487/RFC3798
Snippet:
<li> <cite id="bib-rfc3798">IETF RFC 3798</cite>, Message Disposition Notification <span class="doi">10.17487/RFC3798</span> </li>
Referenced By
- IETF RFC 3801 [Active*]
- IETF RFC 3864 [Active*]
- IETF RFC 3885 [Active*]
- IETF RFC 3886 [Active*]
- IETF RFC 4021 [Active*]
- IETF RFC 4823 [Active*]
- IETF RFC 5321 [Active*]
- IETF RFC 5429 [Active*]
- IETF RFC 5598 [Active*]
- IETF RFC 6533 [Active*]