RFC 2530: Indicating Supported Media Features Using Extensions to DSN and MDN
In plain English — editorial summary, not part of the RFC
This memo describes a format for generating Message Disposition Notifications and Delivery Status Notifications which contain such information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2530
- Published
- March 1999
- Authors
- D. Wing
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3249Implementers Guide for Facsimile Using Internet MailCurrent
September 2002
- RFC 3886An Extensible Message Format for Message Tracking ResponsesCurrent
September 2004
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 2298An Extensible Message Format for Message Disposition NotificationsObsoleted
March 1998
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 3503Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP)Current
March 2003
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
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?