An Extensible Message Format for Message Tracking Responses
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- 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]
- Publication Date
- 2004-09-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3886- Link
- https://doi.org/10.17487/RFC3886
- Author(s)
- Eric P. Allman
- Keyword(s)
- DSN, Message Disposition Notifications, MDN
Latest version of IETF RFC 3886
Document Versions — IETF RFC 3886
-
▶ IETF RFC 3886 (2004-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1123 [Active*]
- IETF RFC 1869 [Superseded*]
- IETF RFC 2033 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2234 [Superseded*]
- IETF RFC 2387 [Active*]
- IETF RFC 2822 [Superseded*]
- IETF RFC 3461 [Active*]
- IETF RFC 3463 [Active*]
- IETF RFC 3464 [Active*]
- IETF RFC 3798 [Superseded*]
- IETF RFC 3885 [Active*]
- IETF RFC 3887 [Active*]
- IETF RFC 3888 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3886.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3886, An Extensible Message Format for Message Tracking Responses. Available at https://doi.org/10.17487/RFC3886
Snippet:
IETF RFC 3886, An Extensible Message Format for Message Tracking Responses. Available at https://doi.org/10.17487/RFC3886
HTML (ISO 690 compliant)
Preview:
IETF RFC 3886, An Extensible Message Format for Message Tracking Responses. Available at https://doi.org/10.17487/RFC3886
Snippet:
<span class="citation"><cite>IETF RFC 3886</cite>, An Extensible Message Format for Message Tracking Responses. Available at <a href="https://doi.org/10.17487/RFC3886" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3886</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3886, An Extensible Message Format for Message Tracking Responses
doi: 10.17487/RFC3886
url: https://doi.org/10.17487/RFC3886
doi: 10.17487/RFC3886
url: https://doi.org/10.17487/RFC3886
Snippet:
<li> <cite id="bib-rfc3886">IETF RFC 3886</cite>, An Extensible Message Format for Message Tracking Responses <span class="doi">10.17487/RFC3886</span> </li>
Referenced By
- IETF RFC 3887 [Active*]
- IETF RFC 5248 [Active*]