RFC 3886: An Extensible Message Format for Message Tracking Responses
In plain English — editorial summary, not part of the RFC
Message Tracking is expected to be used to determine the status of undelivered e-mail upon request. Tracking is used in conjunction with Delivery Status Notifications (DSN) and Message Disposition Notifications (MDN); generally, a message tracking request will be issued only when a DSN or MDN has not been received within a reasonable timeout period. This memo defines a MIME content-type for message tracking status in the same spirit as RFC 3464, "An Extensible Message Format for Delivery Status Notifications". It is to be issued upon a request as described in "Message Tracking Query Protocol". This memo defines only the format of the status information. An extension to SMTP to label messages for further tracking and request tracking status is defined in a separate memo. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3886
- Published
- September 2004
- Authors
- E. Allman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 3463
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 2530Indicating Supported Media Features Using Extensions to DSN and MDNCurrent
March 1999
- RFC 3798Message Disposition NotificationObsoleted
May 2004
- RFC 3464An Extensible Message Format for Delivery Status NotificationsUpdated
January 2003
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 2298An Extensible Message Format for Message Disposition NotificationsObsoleted
March 1998
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?