metasystema.org
ObsoletedDRAFT STANDARDIETF stream

RFC 3798: Message Disposition Notification

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8098.

Current document in this lineage: RFC 8098 — Message Disposition Notification

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC3798
Published
May 2004
Authors
T. Hansen; G. Vaudreuil
Status
DRAFT STANDARD
Stream
IETF
Area
—
Pages
30
Also known as
—
Obsoletes:
RFC 2298
Obsoleted by:
RFC 8098
Updates:
RFC 2046, RFC 3461
Updated by:
RFC 5337, RFC 6533

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2298 (1998)
  2. RFC 3798 (2004)
  3. RFC 8098 (2017) ✓

Read the full history of Message Disposition Notification →

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3798-message-disposition-notification