An Extensible Message Format for Message Tracking Responses
RFC 3886, “An Extensible Message Format for Message Tracking Responses”, is a Proposed Standard document published in September 2004 by E. Allman. It updates RFC 3463. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3886 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3885 SMTP Service Extension for Message Tracking
- RFC 3887 Message Tracking Query Protocol
- RFC 3884 Use of IPsec Transport Mode for Dynamic Routing
- RFC 3888 Message Tracking Model and Requirements
- RFC 3883 Detecting Inactive Neighbors over OSPF Demand Circuits
- RFC 3882 Configuring BGP to Block Denial-of-Service Attacks
- RFC 3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol
- RFC 3881 Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications