The IQ application will be briefly unavailable on Sunday, March 31st, starting at 10:00am ET. Access will be restored as quickly as possible.
Browse Prior Art Database

SMTP Service Extension for Message Tracking (RFC3885)

IP.com Disclosure Number: IPCOM000031514D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 9 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Allman: AUTHOR [+1]

Related Documents

10.17487/RFC3885: DOI


This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 21% of the total text.

Network Working Group E. Allman Request for Comments: 3885 Sendmail, Inc. Updates: 3461 T. Hansen Category: Standards Track AT&T Laboratories September 2004

SMTP Service Extension for Message Tracking

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2004).


This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking.

1. Other Documents and Conformance

The model used for Message Tracking is described in [RFC-MTRK-MODEL].

Doing a Message Tracking query is intended as a "last resort" mechanism. Normally, Delivery Status Notifications (DSNs) [RFC-DSN- SMTP] and Message Disposition Notifications (MDNs) [RFC-MDN] would provide the primary delivery status. Only if the message is not received, or there is no response from either of these mechanisms should a Message Tracking query be issued.

The definition of the base64 token is imported from section 6.8 of [RFC-MIME]. Formally,

base64 = %x2b / %x2f / %x30-39 / %x41-5a / %x61-7a

Allman & Hansen Standards Track [Page 1]

RFC 3885 Message Tracking ESMTP Extension September 2004

The definition of the DIGIT token is imported from [RFC-MSGFMT]. Formally,

DIGIT = %x30-39

Syntax notation in this document conforms to [RFC-ABNF].

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC-KEYWORDS].

2. SMTP Extension Overview

The Message Tracking SMTP service extension uses the SMTP service extension mechanism described in [RFC-ESMTP]. The following service extension is hereby defined:

(1) The name of the SMTP service extension is "Message Tracking".

(2) The EHLO keyword value associated with this extension is "MTRK".

(3) No parameters are allowed with this EHLO keyword value. Future documents may extend this specification by specifying parameters to this keyword value.

(4) One optional parameter using the keyword "MTRK" is added to the MAIL command. In addition, the ENVID parameter of the MAIL command (as defined in RFC 3461) MUST be supported, with extensions as described below. The ORCPT parameter of the RCPT command (as defined in RFC 3461) MUST also be supported. All semantics associated with ENVID and ORCPT described in RFC 3461 MUST be supported as part of this extension.

(5) The maximum length of a MAIL command line is increased by 40 characters by the possible addition of the MTRK keyword and value. Note that the 507 character extension of RCPT commands for the ORCPT parameter and the 107 character extension of MAIL commands for the ENVID parameter as...