Skip to main content

Message Disposition Notification
RFC 8098 also known as STD 85

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc8098 in std85 via sync to the rfc-index
2023-12-12
(System) No history of STD85 is currently available in the datatracker before this point
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This memo defines a MIME content type that may be used by a Mail User Agent …
Received changes through RFC Editor sync (changed abstract to '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).')
2017-04-21
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2017-03-03
(System) IANA registries were updated to include RFC8098
2017-02-28
(System)
Received changes through RFC Editor sync (created alias RFC 8098, changed abstract to 'This memo defines a MIME content type that may be used …
Received changes through RFC Editor sync (created alias RFC 8098, changed abstract to '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.', changed standardization level to Internet Standard, changed state to RFC, added RFC published event at 2017-02-28, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-appsawg-mdn-3798bis and RFC 3798, created updates relation between draft-ietf-appsawg-mdn-3798bis and RFC 2046, created updates relation between draft-ietf-appsawg-mdn-3798bis and RFC 3461, created alias STD 85)
2017-02-28
(System) RFC published