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) media 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 media type with respect to delivery status reports, mail processing programs will benefit if a single media type is used for all kinds of reports. This memo obsoletes "The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages", RFC 3462, and marks RFC 3462 and its predecessor as "Historic". [STANDARDS-TRACK]
Document record
- Document ID
- RFC6522
- Published
- January 2012
- Authors
- M. Kucherawy
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- STD73
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1892 (1996)
- RFC 3462 (2003)
- RFC 6522 (2012)
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.
- RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent
September 2002
- RFC 4288Media Type Specifications and Registration ProceduresObsoleted
December 2005
- RFC 3870application/rdf+xml Media Type RegistrationCurrent
September 2004
- RFC 3855Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400Current
July 2004
- RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current
July 2004
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 3745MIME Type Registrations for JPEG 2000 (ISO/IEC 15444)Current
April 2004
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?