draft-ietf-msgtrk-trkstat-00.txt   draft-ietf-msgtrk-trkstat-01.txt 
Internet Draft E. Allman Internet Draft E. Allman
draft-ietf-msgtrk-trkstat-00.txt Sendmail, Inc. draft-ietf-msgtrk-trkstat-01.txt Sendmail, Inc.
Valid for six months December 14, 2000 Valid for six months March 20, 2001
Updates: RFC 1893 Updates: RFC 1893
The Message/Tracking-Status MIME Extension The Message/Tracking-Status MIME Extension
<draft-ietf-msgtrk-trkstat-00.txt> <draft-ietf-msgtrk-trkstat-01.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. Internet-Drafts are with all provisions of Section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also dis- areas, and its working groups. Note that other groups may also dis-
tribute working documents as Internet-Drafts. tribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
skipping to change at page 4, line 44 skipping to change at page 4, line 44
section 2.3.1 of [RFC-DSN-STAT]. This field is REQUIRED. section 2.3.1 of [RFC-DSN-STAT]. This field is REQUIRED.
3.3.2. Final-Recipient field 3.3.2. Final-Recipient field
The required Final-Recipient field is defined as in sec- The required Final-Recipient field is defined as in sec-
tion 2.3.2 of [RFC-DSN-STAT]. This field is REQUIRED. tion 2.3.2 of [RFC-DSN-STAT]. This field is REQUIRED.
3.3.3. Action field 3.3.3. Action field
The required Action field indicates the action performed The required Action field indicates the action performed
by the Reporting-MTA as a result of its attempt to delivery by the Reporting-MTA as a result of its attempt to deliver
the message to this recipient address. This field MUST be the message to this recipient address. This field MUST be
present for each recipient named in the MTSN. The syntax is present for each recipient named in the MTSN. The syntax is
as defined in section 2.3.3 of RFC 1894. This field is as defined in section 2.3.3 of RFC 1894. This field is
REQUIRED. REQUIRED.
Valid actions are: Valid actions are:
failed The message could not be delivered. If DSNs failed The message could not be delivered. If DSNs
have been enabled, a "failed" DSN should already have been enabled, a "failed" DSN should already
have been returned. have been returned.
delayed The message is currently waiting in the MTA delayed The message is currently waiting in the MTA
queue for future delivery. Essentially, this queue for future delivery. Essentially, this
action means "the message is located, and it is action means "the message is located, and it is
here." here."
delivered The message has been successfully delivered to delivered The message has been successfully delivered to
the final recipient. This includes "delivery" the final recipient. This includes "delivery"
to a mailing list exploder. No further informa- to a mailing list exploder. It does not indi-
tion is available; in particular, the tracking cate that the message has been read. No further
information is available; in particular, the
tracking agent SHOULD NOT attempt further "down-
stream" tracking requests.
expanded The message has been successfully delivered to
the recipient address as specified by the
sender, and forwarded by the Reporting-MTA
beyond that destination to multiple additional
recipient addresses. However, these additional
addresses are not trackable, and the tracking
agent SHOULD NOT attempt further "downstream" agent SHOULD NOT attempt further "downstream"
tracking requests. tracking requests.
relayed The message has been delivered into an environ- relayed The message has been delivered into an environ-
ment that does not support message tracking. No ment that does not support message tracking. No
further information is available; in particular, further information is available; in particular,
the tracking agent SHOULD NOT attempt further the tracking agent SHOULD NOT attempt further
"downstream" tracking requests. "downstream" tracking requests.
transferred The message has been transferred to another transferred The message has been transferred to another
skipping to change at page 5, line 56 skipping to change at page 6, line 10
no delivery attempts have been made or if the Action field no delivery attempts have been made or if the Action field
has value "opaque". If delivery to some agent other than an has value "opaque". If delivery to some agent other than an
MTA (for example, a Local Delivery Agent) then this field MAY MTA (for example, a Local Delivery Agent) then this field MAY
be included, giving the name of the host on which that agent be included, giving the name of the host on which that agent
was contacted. was contacted.
3.3.6. Last-Attempt-Date field 3.3.6. Last-Attempt-Date field
The Last-Attempt-Date field is defined as in section The Last-Attempt-Date field is defined as in section
Reference 2.3.7 of [RFC-DSN-STAT]. This field is REQUIRED if Reference 2.3.7 of [RFC-DSN-STAT]. This field is REQUIRED if
any delivery attempt has been made, in which case it will any delivery attempt has been made and the Action field does
specify when it last attempted to deliver this message to not have value "opaque", in which case it will specify when
another MTA or other Delivery Agent. This field MUST NOT be it last attempted to deliver this message to another MTA or
included if no delivery attempts have been made. other Delivery Agent. This field MUST NOT be included if no
delivery attempts have been made.
3.3.7. Will-Retry-Until field 3.3.7. Will-Retry-Until field
The Will-Retry-Until field is defined as in section Ref- The Will-Retry-Until field is defined as in section Ref-
erence 2.3.8 of [RFC-DSN-STAT]. This field is REQUIRED if erence 2.3.8 of [RFC-DSN-STAT]. If the message is not in the
the message is still in the MTA queue. This field MUST NOT local queue or the Action field has the value ``opaque'' the
be included if the message is not in the local queue. Will-Retry-Until field MUST NOT be included; otherwise, this
field is REQUIRED.
3.4. Extension fields 3.4. Extension fields
Future extension fields may be defined as defined in sec- Future extension fields may be defined as defined in sec-
tion 2.4 of [RFC-DSN-STAT]. tion 2.4 of [RFC-DSN-STAT].
3.5. Interaction Between MTAs and LDAs 3.5. Interaction Between MTAs and LDAs
A message that has been delivered to an LDA that under- A message that has been delivered to an LDA that under-
stands message tracking (in particular, an LDA speaking LMTP stands message tracking (in particular, an LDA speaking LMTP
skipping to change at page 7, line 47 skipping to change at page 7, line 59
[RFC-DSN-STAT] [RFC-DSN-STAT]
K. Moore and G. Vaudreuil, ``An Extensible Message Format for K. Moore and G. Vaudreuil, ``An Extensible Message Format for
Delivery Status Notifications.'' RFC 1894. January 1996. Delivery Status Notifications.'' RFC 1894. January 1996.
[RFC-EMSSC] [RFC-EMSSC]
G. Vaudreuil, ``Enhanced Mail System Status Codes.'' RFC G. Vaudreuil, ``Enhanced Mail System Status Codes.'' RFC
1893. January 1996. 1893. January 1996.
[RFC-ESMTP] [RFC-ESMTP]
Rose, M., Stefferud, E., Crocker, D., Klensin, J. and N. Rose, M., Stefferud, E., Crocker, D., Klensin, J. and N.
Freed, ``SMTP Service Extensions.'' STD 10, RFC 1869. Novem- Freed, ``SMTP Service Extensions.'' STD 10, RFC 1869.
ber 1995.
November 1995.
[RFC-HOSTREQ] [RFC-HOSTREQ]
R. Braden (ed.), ``Requirements for Internet Hosts -- Applica- R. Braden (ed.), ``Requirements for Internet Hosts -- Applica-
tion and Support.'' STD 3, RFC 1123. October 1989. tion and Support.'' STD 3, RFC 1123. October 1989.
[RFC-KEYWORDS] [RFC-KEYWORDS]
S. Bradner, ``Key words for use in RFCs to Indicate Require- S. Bradner, ``Key words for use in RFCs to Indicate Require-
ment Levels.'' RFC 2119. March 1997. ment Levels.'' RFC 2119. March 1997.
[RFC-LMTP] [RFC-LMTP]
 End of changes. 8 change blocks. 
15 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/