Message Tracking Query Protocol
RFC 3887, “Message Tracking Query Protocol”, is a Proposed Standard document published in September 2004 by T. Hansen. It has since been updated by RFC 8553, RFC 8996. The canonical text is published by the RFC Editor.
Abstract
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]
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 3887 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3886 An Extensible Message Format for Message Tracking Responses
- RFC 3888 Message Tracking Model and Requirements
- RFC 3885 SMTP Service Extension for Message Tracking
- RFC 3884 Use of IPsec Transport Mode for Dynamic Routing
- RFC 3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol
- RFC 3883 Detecting Inactive Neighbors over OSPF Demand Circuits
- RFC 3891 The Session Initiation Protocol "Replaces" Header
- RFC 3882 Configuring BGP to Block Denial-of-Service Attacks