RFC 3887: Message Tracking Query Protocol

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…

Read RFC 3887 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 2246: The TLS Protocol Version 1.0
Normative reference — RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
Normative reference — RFC 2234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Normative reference — RFC 2821: Simple Mail Transfer Protocol
Normative reference — RFC 2554: SMTP Service Extension for Authentication
Normative reference — RFC 3885: SMTP Service Extension for Message Tracking
Normative reference — RFC 3886: An Extensible Message Format for Message Tracking Responses
Informative reference — RFC 3280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Informative reference — RFC 3174: US Secure Hash Algorithm 1 (SHA1)
Informative reference — RFC 3207: SMTP Service Extension for Secure SMTP over Transport Layer Security
Informative reference — RFC 977: Network News Transfer Protocol

Incoming relationships (5 related RFCs)

Updated by, Normatively referenced by — RFC 8996: Deprecating TLS 1.0 and TLS 1.1
Updated by, Informatively referenced by — RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
Normatively referenced by — RFC 3885: SMTP Service Extension for Message Tracking
Normatively referenced by — RFC 3886: An Extensible Message Format for Message Tracking Responses
Informatively referenced by — RFC 3888: Message Tracking Model and Requirements