metasystema.org
ObsoletedDRAFT STANDARDIETF stream

RFC 3462: The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages

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

Current document in this lineage: RFC 6522 — The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages

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

The Multipart/Report Multipurpose Internet Mail Extensions (MIME) content-type is a general "family" or "container" type for electronic mail reports of any kind. Although this memo defines only the use of the Multipart/Report content-type with respect to delivery status reports, mail processing programs will benefit if a single content-type is used to for all kinds of reports. This document is part of a four document set describing the delivery status report service. This collection includes the Simple Mail Transfer Protocol (SMTP) extensions to request delivery status reports, a MIME content for the reporting of delivery reports, an enumeration of extended status codes, and a multipart container for the delivery report, the original message, and a human-friendly summary of the failure. [STANDARDS-TRACK]

Document record

Document ID
RFC3462
Published
January 2003
Authors
G. Vaudreuil
Status
DRAFT STANDARD
Stream
IETF
Area
—
Pages
7
Also known as
—
Obsoletes:
RFC 1892
Obsoleted by:
RFC 6522
Updated by:
RFC 5337

Topics

Standards lineage

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

  1. RFC 1892 (1996)
  2. RFC 3462 (2003)
  3. RFC 6522 (2012) ✓

Read the full history of The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages →

Referenced by

2 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/3462-the-multipart-report-content-type-for-the-reporting-of-mail-system-administrativ