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: 2004-Sep-28
Document File: 10 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Allman: AUTHOR [+2]

Abstract

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

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 16% 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).

Abstract

   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 paramete...