RFC 3885: SMTP Service Extension for Message Tracking
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3885
- Published
- September 2004
- Authors
- E. Allman; T. Hansen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 3461
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2821Simple Mail Transfer ProtocolObsoleted
April 2001
- RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent
September 2004
- RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent
July 2004
- RFC 3463Enhanced Mail System Status CodesUpdated
January 2003
- RFC 4141SMTP and MIME Extensions for Content ConversionCurrent
November 2005
- RFC 3207SMTP Service Extension for Secure SMTP over Transport Layer SecurityUpdated
February 2002
- RFC 3030SMTP Service Extensions for Transmission of Large and Binary MIME MessagesCurrent
December 2000
- RFC 2852Deliver By SMTP Service ExtensionCurrent
June 2000
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?