RFC 3462
The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages, January 2003
- File formats:
- Status:
- DRAFT STANDARD
- Obsoletes:
- RFC 1892
- Obsoleted by:
- RFC 6522
- Updated by:
- RFC 5337
- Author:
- G. Vaudreuil
- Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3462
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3462
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.