Skip to main content

An Extensible Message Format for Message Tracking Responses
RFC 3886

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Message Tracking is expected to be used to determine the status of undelivered e-mail upon request. …
Received changes through RFC Editor sync (changed abstract to '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]')
2015-10-14
(System) Notify list changed from , to
2004-10-01
Amy Vezza [Note]: 'RFC 3886' added by Amy Vezza
2004-10-01
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2004-09-29
(System) RFC published