Message Disposition Notification

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 37
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 header fields 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 are 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 multiprotocol 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. This document is an Internet Standard. It obsoletes RFC 3798 and updates RFC 2046 (message/partial media type handling) and RFC 3461 (Original-Recipient header field generation requirement).
Publication Date: 2017-02-01
Status Note: Internet Standard
DOI: 10.17487/RFC8098
Link: https://doi.org/10.17487/RFC8098
Author(s): Tony Hansen
Alexey Melnikov
Keyword(s): Delivery Notification, MDN

Latest version of IETF RFC 8098

Document Versions — IETF RFC 8098

▶ IETF RFC 8098 (2017-02-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2045 [Active*]
IETF RFC 2046 [Active, Amended*]
IETF RFC 2047 [Active*]
IETF RFC 2119 [Active*]
IETF RFC 3461 [Active*]
IETF RFC 3464 [Active*]
IETF RFC 3503 [Active*]
IETF RFC 5321 [Active*]
IETF RFC 5322 [Active, Amended*]
IETF RFC 6522 [Active*]

Bibliographic Reference(s)

IETF RFC 2634 [Active*]
IETF RFC 3249 [Active*]
IETF RFC 3501 [Superseded*]
IETF RFC 3801 [Active*]
IETF RFC 5226 [Superseded*]
IETF RFC 5233 [Active*]
IETF RFC 5429 [Active*]
IETF RFC 5598 [Active*]
IETF RFC 6533 [Active*]
T-REC-F.400.1999 — X.400 EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC8098.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 8098, Message Disposition Notification. Available at https://doi.org/10.17487/RFC8098

Snippet:

IETF RFC 8098, Message Disposition Notification. Available at https://doi.org/10.17487/RFC8098

HTML (ISO 690 compliant)

Preview:

IETF RFC 8098, Message Disposition Notification. Available at https://doi.org/10.17487/RFC8098

Snippet:

<span class="citation"><cite>IETF RFC 8098</cite>, Message Disposition Notification. Available at <a href="https://doi.org/10.17487/RFC8098" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8098</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 8098, Message Disposition Notification
doi: 10.17487/RFC8098
url: https://doi.org/10.17487/RFC8098

Snippet:

<li>
<cite id="bib-rfc8098">IETF RFC 8098</cite>, Message Disposition Notification
<span class="doi">10.17487/RFC8098</span>
</li>