draft-freed-sieve-notary-05.txt   draft-freed-sieve-notary-06.txt 
Network Working Group N. Freed Network Working Group N. Freed
Internet-Draft Sun Microsystems Internet-Draft Sun Microsystems
Expires: September 25, 2009 March 24, 2009 Expires: September 24, 2010 March 23, 2010
Sieve Email Filtering: Delivery Status Notifications and Deliver-By Sieve Email Filtering: Delivery Status Notifications and Deliver-By
Extensions Extensions
draft-freed-sieve-notary-05 draft-freed-sieve-notary-06
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 25, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
This document describes the "envelope-dsn", "redirect-dsn", This document describes the "envelope-dsn", "redirect-dsn",
"envelope-deliverby", and "redirect-deliverby" extensions to the "envelope-deliverby", and "redirect-deliverby" extensions to the
Sieve email filtering language. The "envelope-dsn" and "envelope- Sieve email filtering language. The "envelope-dsn" and "envelope-
deliverby" extensions provide access to additional envelope deliverby" extensions provide access to additional envelope
information provided by the delivery status notification and information provided by the delivery status notification and
deliver-by SMTP extensions. The "redirect-dsn" and "redirect- deliver-by SMTP extensions. The "redirect-dsn" and "redirect-
deliverby" extensions extend Sieve's redirect action to provide deliverby" extensions extend Sieve's redirect action to provide
skipping to change at page 2, line 39 skipping to change at page 2, line 5
Fixed more typos. Fixed more typos.
Changed dsn-envelope and dsn-redirect to envelope-dsn and redirect- Changed dsn-envelope and dsn-redirect to envelope-dsn and redirect-
dsn, respectively. dsn, respectively.
Added a redirect-dsn example. Added a redirect-dsn example.
Added the two deliver-by extensions. Added the two deliver-by extensions.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 24, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
1. Introduction 1. Introduction
Sieve [RFC5228] is a language for filtering email messages at or Sieve [RFC5228] is a language for filtering email messages at or
around the time of final delivery. It is designed to be around the time of final delivery. It is designed to be
implementable on either a mail client or mail server. It is suitable implementable on either a mail client or mail server. It is suitable
for running on a mail server where users may not be allowed to for running on a mail server where users may not be allowed to
execute arbitrary programs, such as on black box Internet Message execute arbitrary programs, such as on black box Internet Message
Access Protocol [RFC3501] servers, as it has no user-controlled loops Access Protocol [RFC3501] servers, as it has no user-controlled loops
or the ability to run external programs. or the ability to run external programs.
skipping to change at page 4, line 5 skipping to change at page 4, line 5
document are "envelope-dsn", "redirect-dsn", "envelope-deliverby", document are "envelope-dsn", "redirect-dsn", "envelope-deliverby",
and "redirect-deliverby". and "redirect-deliverby".
4. Envelope-dsn Extension 4. Envelope-dsn Extension
The "envelope-dsn" extension does not define any new tests or The "envelope-dsn" extension does not define any new tests or
actions, rather, it adds four values to the list of possible (case- actions, rather, it adds four values to the list of possible (case-
insensitive) envelope-part strings defined in Section 5.4 of insensitive) envelope-part strings defined in Section 5.4 of
[RFC5228]: [RFC5228]:
notify Match the list of notification conditions, or NOTIFY values, notify - Match the list of notification conditions, or NOTIFY
associated with the TO address used in the SMTP RCPT TO command values, associated with the TO address used in the SMTP RCPT TO
that resulted in this message getting delivered to this user. command that resulted in this message getting delivered to this
More than one notification condition can be in effect at once; user. More than one notification condition can be in effect at
each condition that is in effect is tested separately and any once; each condition that is in effect is tested separately and
match causes the test to succeed. The syntax and semantics of the any match causes the test to succeed. The syntax and semantics of
NOTIFY parameter are defined in RFC 3461 [RFC3461] section 4.1. the NOTIFY parameter are defined in Section 4.1 of RFC 3461
Currently the possible notification condition values are "NEVER", [RFC3461] . Currently the possible notification condition values
"SUCCESS", "FAILURE" and "DELAY". Note that the value "NEVER" are "NEVER", "SUCCESS", "FAILURE" and "DELAY". Note that the
cannot be combined with any other value. value "NEVER" cannot be combined with any other value.
orcpt Match the original recipient, or ORCPT, value in decoded form orcpt - Match the original recipient, or ORCPT, value in decoded
associated with the TO address used in the SMTP RCPT TO command form associated with the TO address used in the SMTP RCPT TO
that resulted in this message getting delivered to this user. The command that resulted in this message getting delivered to this
syntax and semantics of the ORCPT parameter are defined in Section user. The syntax and semantics of the ORCPT parameter are defined
2.2 of RFC 3461 [RFC3461]. in Section 4.2 of RFC 3461 [RFC3461].
ret Match the return of content, or RET, value given in the SMTP ret - Match the return of content, or RET, value given in the SMTP
MAIL FROM command. The syntax and semantics of the RET parameter MAIL FROM command. The syntax and semantics of the RET parameter
are defined in RFC 3461 [RFC3461] section 4.3. Currently the are defined in Section 4.3 of RFC 3461 [RFC3461]. Currently the
possible return of content values are "FULL" and "HDRS". possible return of content values are "FULL" and "HDRS".
envid Match the envelope identifier, or ENVID, value in decoded form envid - Match the envelope identifier, or ENVID, value in decoded
given in the SMTP MAIL FROM command. The syntax and semantics of form given in the SMTP MAIL FROM command. The syntax and
the ENVID parameter are defined in Section 4.4 of RFC 3461 semantics of the ENVID parameter are defined in Section 4.4 of RFC
[RFC3461]. 3461 [RFC3461].
All of these tests fail unconditionally if the specified envelope All of these tests fail unconditionally if the specified envelope
parameter does not exist for the current message or recipient. parameter does not exist for the current message or recipient.
The envelope test's ADDRESS-PART argument assumes the string being The envelope test's ADDRESS-PART argument assumes the string being
tested has the syntax of an email address. None of the new envelope tested has the syntax of an email address. None of the new envelope
parts defined here have address syntax, accordingly, it is an error parts defined here have address syntax, accordingly, it is an error
to specify an ADDRESS-PART argument in conjunction with these new to specify an ADDRESS-PART argument in conjunction with these new
envelope parts. envelope parts.
skipping to change at page 5, line 48 skipping to change at page 5, line 48
if envelope :matches "orcpt" "rfc822;*@example.com" if envelope :matches "orcpt" "rfc822;*@example.com"
{ {
# do whatever # do whatever
} }
5. Envelope-deliverby Extension 5. Envelope-deliverby Extension
The "envelope-deliverby" extension does not define any new tests or The "envelope-deliverby" extension does not define any new tests or
actions, rather, it adds three values to the list of possible (case- actions, rather, it adds three values to the list of possible (case-
insensitive) envelope-part strings defined in Section 5.4 of insensitive) envelope-part strings defined in Section 5.4 of
[RFC5228]: [RFC5228]. These new envelope parts are defined in Section 5 of
[RFC2852].
bytime Match the initial integer part of the deliver-by extension's bytime - Match the initial integer part of the deliver-by
BY parameter specified in the SMTP MAIL FROM command. extension's BY parameter specified in the SMTP MAIL FROM command.
bymde Match a string computed from the by-mode part of the bymode - Match a string computed from the by-mode part of the
deliver-by extension's BY parameter. The possible values are deliver-by extension's BY parameter. The possible values are
"notify" and "return", which correspond to the BY parameter mode "notify" and "return", which correspond to the BY parameter mode
specifier characters "N" and "R" respectively. specifier characters "N" and "R" respectively.
bytrace Match the trace modifier computed from the by-trace modifier bytrace - Match the trace modifier computed from the by-trace
on the deliver-by extension's BY parameter. The possible values modifier on the deliver-by extension's BY parameter. The possible
are "trace" and "" (the empty string). These values correspond to values are "trace" and "" (the empty string). These values
the presence or absence of the by-trace "T" modifier respectively. correspond to the presence or absence of the by-trace "T" modifier
respectively.
All of these tests fail unconditionally if the BY SMTP MAIL FROM All of these tests fail unconditionally if the BY SMTP MAIL FROM
parameter does not exist for the current message or recipient. parameter does not exist for the current message or recipient.
The envelope test's ADDRESS-PART argument assumes the string being The envelope test's ADDRESS-PART argument assumes the string being
tested has the syntax of an email address. None of the new envelope tested has the syntax of an email address. None of the new envelope
parts defined here have address syntax, accordingly, it is an error parts defined here have address syntax, accordingly, it is an error
to specify an ADDRESS-PART argument in conjunction with these new to specify an ADDRESS-PART argument in conjunction with these new
envelope parts. envelope parts.
skipping to change at page 10, line 18 skipping to change at page 10, line 18
extension specified in this document: extension specified in this document:
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve extensions Subject: Registration of new Sieve extensions
Capability name: envelope-dsn Capability name: envelope-dsn
Description: The "envelope-dsn" extension extends the envelope Description: The "envelope-dsn" extension extends the envelope
test to allow checking of information associated test to allow checking of information associated
with the DSN ESMTP extension defined in RFC 3461. with the DSN ESMTP extension defined in RFC 3461.
RFC number: RFC XXXX RFC number: RFC XXXX
Contact address: Sieve discussion list <ietf-mta-filters@imc.org> Contact address: Sieve discussion list <sieve@ietf.org>
Capability name: envelope-deliverby Capability name: envelope-deliverby
Description: The "envelope-deliverby" extension extends the Description: The "envelope-deliverby" extension extends the
envelope test to allow checking of information envelope test to allow checking of information
associated with the Deliver-By ESMTP extension associated with the Deliver-By ESMTP extension
defined in RFC 2852. defined in RFC 2852.
RFC number: RFC XXXX RFC number: RFC XXXX
Contact address: Sieve discussion list <ietf-mta-filters@imc.org> Contact address: Sieve discussion list <sieve@ietf.org>
Capability name: redirect-dsn Capability name: redirect-dsn
Description: The "redirect-dsn" extension extends the redirect Description: The "redirect-dsn" extension extends the redirect
action to allow specification of the NOTIFY and action to allow specification of the NOTIFY and
RET ESMTP parameters associated with the DSN SMTP RET ESMTP parameters associated with the DSN SMTP
extension defined in RFC 3461. extension defined in RFC 3461.
RFC number: RFC XXXX RFC number: RFC XXXX
Contact address: Sieve discussion list <ietf-mta-filters@imc.org> Contact address: Sieve discussion list <sieve@ietf.org>
Capability name: redirect-deliverby Capability name: redirect-deliverby
Description: The "redirect-deliverby" extension extends the Description: The "redirect-deliverby" extension extends the
redirect action to allow specification of the BY redirect action to allow specification of the BY
ESMTP parameter associated with the Deliver-By SMTP ESMTP parameter associated with the Deliver-By SMTP
extension defined in RFC 2852. extension defined in RFC 2852.
RFC number: RFC XXXX RFC number: RFC XXXX
Contact address: Sieve discussion list <ietf-mta-filters@imc.org> Contact address: Sieve discussion list <sieve@ietf.org>
This information should be added to the list of sieve extensions This information should be added to the list of sieve extensions
given on http://www.iana.org/assignments/sieve-extensions. given on http://www.iana.org/assignments/sieve-extensions.
10. References 10. References
10.1. Normative references 10.1. Normative references
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
 End of changes. 16 change blocks. 
69 lines changed or deleted 75 lines changed or added

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