metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3887: Message Tracking Query Protocol

Still current, but amended. Parts of this document are changed or extended by RFC 8553, RFC 8996. Read both.

In plain English — editorial summary, not part of the RFC

Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document describes the Message Tracking Query Protocol that is used in conjunction with extensions to the ESMTP protocol to provide a complete message tracking solution for the Internet. [STANDARDS-TRACK]

Document record

Document ID
RFC3887
Published
September 2004
Authors
T. Hansen
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
23
Also known as
—
Updated by:
RFC 8553, RFC 8996

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3887-message-tracking-query-protocol