Search RFCs
- File formats:
- Status:
- INTERNET STANDARD
- Obsoletes:
- RFC 3798
- Updates:
- RFC 2046,RFC 3461
- Authors:
- T. Hansen, Ed.
A. Melnikov, Ed. - Stream:
- IETF
- Source:
- appsawg (art)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8098
Discuss this RFC: Send questions or comments to the mailing listart@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8098
Abstract
This memo defines a MIME content type that may be used by a Mail UserAgent (MUA) or electronic mail gateway to report the disposition of amessage after it has been successfully delivered to a recipient.This content type is intended to be machine processable. Additionalmessage header fields are also defined to permit Message DispositionNotifications (MDNs) to be requested by the sender of a message. Thepurpose is to extend Internet Mail to support functionality oftenfound 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 todo this while respecting privacy concerns, which have often beenexpressed when such functions have been discussed in the past.
Because many messages are sent between the Internet and othermessaging systems (such as X.400 or the proprietary "LAN-based"systems), the MDN protocol is designed to be useful in amultiprotocol messaging environment. To this end, the protocoldescribed 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" offoreign notifications through Internet Mail.
This document is an Internet Standard. It obsoletes RFC 3798 andupdates RFC 2046 (message/partial media type handling) and RFC 3461(Original-Recipient header field generation requirement).
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.