metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 2298: An Extensible Message Format for Message Disposition Notifications

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

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 (UA) or electronic mail gateway to report the disposition of a message after it has been sucessfully delivered to a recipient. [STANDARDS-TRACK]

Document record

Document ID
RFC2298
Published
March 1998
Authors
R. Fajman
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
28
Also known as
—
Obsoleted by:
RFC 3798

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

One later RFC formally updates or obsoletes 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/2298-an-extensible-message-format-for-message-disposition-notifications