Message Disposition Notification
RFC 8098, “Message Disposition Notification”, is an Internet Standard document published in February 2017 by T. Hansen, A. Melnikov. It updates RFC 2046, RFC 3461. It obsoletes RFC 3798. The canonical text is published by the RFC Editor.
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).
What “Internet Standard” means
A mature, widely-implemented specification that has completed the full IETF standards process — the highest maturity level on the standards track.
The canonical text of RFC 8098 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8097 BGP Prefix Origin Validation State Extended Community
- RFC 8099 OSPF Topology-Transparent Zone
- RFC 8096 The IPv6-Specific MIB Modules Are Obsolete
- RFC 8100 Diffserv-Interconnection Classes and Practice
- RFC 8095 Services Provided by IETF Transport Protocols and Congestion Control Mechanisms
- RFC 8101 IANA Registration of New Session Initiation Protocol Resource- Priority Namespace for Mission Critical Push To Talk Service
- RFC 8094 DNS over Datagram Transport Layer Security
- RFC 8102 Remote-LFA Node Protection and Manageability