draft-freed-sieve-notary-06.txt   draft-freed-sieve-notary-07.txt 
Network Working Group N. Freed Network Working Group N. Freed
Internet-Draft Sun Microsystems Internet-Draft Oracle
Expires: September 24, 2010 March 23, 2010 Intended status: Standards Track March 24, 2010
Expires: September 25, 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-06 draft-freed-sieve-notary-07
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
control over delivery status notification and deliver-by parameters, control over delivery status notification and deliver-by parameters,
respectively. respectively.
Change History (to be removed prior to publication as an RFC Change History (to be removed prior to publication as an RFC
Clarified orcpt decoding.
Changed the ABNF for notary values to disallow spaces.
Fixed several typos. Fixed several typos.
Changed name of extension from notary to envelope-dsn. Changed name of extension from notary to envelope-dsn.
Added the redirect-dsn extension. Added the redirect-dsn extension.
Updated references. Updated references.
Added a note about the use of ADDRESS-PART arguments with the new Added a note about the use of ADDRESS-PART arguments with the new
envelope-part strings defined by the envelope-dsn extension. envelope-part strings defined by the envelope-dsn extension.
skipping to change at page 2, line 26 skipping to change at page 2, line 31
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 24, 2010. This Internet-Draft will expire on September 25, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 3, line 13
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.
The base sieve specification defines the envelope extension and test The base sieve specification defines the envelope extension and test
to access information in the message envelope. Only information to access information in the message envelope. Only information
available in regular SMTP is provided; additional information added available in regular SMTP [RFC5321] is provided; additional
to the SMTP envelope by SMTP extensions cannot be accessed. information added to the SMTP envelope by SMTP extensions cannot be
accessed.
The "envelope-dsn" extension extends the envelope test to allow The "envelope-dsn" extension extends the envelope test to allow
access to the additional envelope fields defined by the SMTP access to the additional envelope fields defined by the SMTP
extension for delivery status notification specified in RFC 3461 extension for delivery status notification specified in RFC 3461
[RFC3461]. The "envelope-deliverby" extension extends the envelope [RFC3461]. The "envelope-deliverby" extension extends the envelope
test to allow access to the additional envelope fields defined by the test to allow access to the additional envelope fields defined by the
deliver-by SMTP extension defined in [RFC2852]. deliver-by SMTP extension defined in [RFC2852].
The base sieve specification also defines the redirect action which The base sieve specification also defines the redirect action which
sends the message to a different address. Redirect only allows sends the message to a different address. Redirect only allows
skipping to change at page 4, line 16 skipping to change at page 4, line 23
values, associated with the TO address used in the SMTP RCPT TO values, associated with the TO address used in the SMTP RCPT TO
command that resulted in this message getting delivered to this command that resulted in this message getting delivered to this
user. More than one notification condition can be in effect at user. More than one notification condition can be in effect at
once; each condition that is in effect is tested separately and once; each condition that is in effect is tested separately and
any match causes the test to succeed. The syntax and semantics of any match causes the test to succeed. The syntax and semantics of
the NOTIFY parameter are defined in Section 4.1 of RFC 3461 the NOTIFY parameter are defined in Section 4.1 of RFC 3461
[RFC3461] . Currently the possible notification condition values [RFC3461] . Currently the possible notification condition values
are "NEVER", "SUCCESS", "FAILURE" and "DELAY". Note that the are "NEVER", "SUCCESS", "FAILURE" and "DELAY". Note that the
value "NEVER" 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 orcpt - Match the original recipient, or ORCPT, value associated
form associated with the TO address used in the SMTP RCPT TO with the TO address used in the SMTP RCPT TO command that resulted
command that resulted in this message getting delivered to this in this message getting delivered to this user, with xtext
user. The syntax and semantics of the ORCPT parameter are defined encoding removed. The syntax and semantics of the ORCPT parameter
in Section 4.2 of RFC 3461 [RFC3461]. are defined 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 Section 4.3 of RFC 3461 [RFC3461]. 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 envid - Match the envelope identifier, or ENVID, value in decoded
form given in the SMTP MAIL FROM command. The syntax and form given in the SMTP MAIL FROM command. The syntax and
semantics of the ENVID parameter are defined in Section 4.4 of RFC semantics of the ENVID parameter are defined in Section 4.4 of RFC
3461 [RFC3461]. 3461 [RFC3461].
skipping to change at page 7, line 20 skipping to change at page 7, line 28
actions, rather, it adds two new arguments, NOTIFY and RET, to the actions, rather, it adds two new arguments, NOTIFY and RET, to the
redirect action defined in Section 4.2 of [RFC5228]. This updates redirect action defined in Section 4.2 of [RFC5228]. This updates
the usage description for redirect to: the usage description for redirect to:
[ [
Usage: redirect [:notify "value"] [:ret "FULL"|"HDRS"] Usage: redirect [:notify "value"] [:ret "FULL"|"HDRS"]
<address: string> <address: string>
The syntax for the NOTIFY and RET arguments are: The syntax for the NOTIFY and RET arguments are:
NOTIFY = ":notify" notify-value NOTIFY = ":notify" notify-value
notify-value = DQUOTE notify-esmtp-value DQUOTE notify-value = DQUOTE ("NEVER" / notify-esmtp-list) DQUOTE
notify-esmtp-list = notify-list-element *("," notify-list-element)
RET = ":ret" ret-value RET = ":ret" ret-value
ret-value = DQUOTE ("FULL" / "HDRS") DQUOTE ret-value = DQUOTE ("FULL" / "HDRS") DQUOTE
The notify-esmtp-value production is defined in Section 4.1 of The notify-list-element production is defined in Section 4.1 of
[RFC3461]. [RFC3461].
When these arguments are specified, they set the corresponding NOTIFY When these arguments are specified, they set the corresponding NOTIFY
ESMTP RCPT TO and RET ESMTP MAIL FROM parameters, respectively. ESMTP RCPT TO and RET ESMTP MAIL FROM parameters, respectively.
These arguments are only honored if the delivery status notification These arguments are only honored if the delivery status notification
(DSN) ESMTP extension is available. When the DSN extension is not (DSN) ESMTP extension is available. When the DSN extension is not
available, these arguments MUST be ignored and MUST NOT cause an available, these arguments MUST be ignored and MUST NOT cause an
error. error.
6.1. Example 6.1. Example
skipping to change at page 11, line 25 skipping to change at page 11, line 25
[RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering [RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering
Language", RFC 5228, January 2008. Language", RFC 5228, January 2008.
[RFC5231] Segmuller, W. and B. Leiba, "Sieve Email Filtering: [RFC5231] Segmuller, W. and B. Leiba, "Sieve Email Filtering:
Relational Extension", RFC 5231, January 2008. Relational Extension", RFC 5231, January 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
October 2008.
10.2. Informative references 10.2. Informative references
[RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", RFC 3501, March 2003. 4rev1", RFC 3501, March 2003.
[RFC3894] Degener, J., "Sieve Extension: Copying Without Side [RFC3894] Degener, J., "Sieve Extension: Copying Without Side
Effects", RFC 3894, October 2004. Effects", RFC 3894, October 2004.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Cyrus Daboo, Derek Diget, Philip Guenther, Arnt Gulbrandsen, Andrew Cyrus Daboo, Derek Diget, Philip Guenther, Arnt Gulbrandsen, Barry
McKeon, Alexey Melnikov, Chris Newman, Aaron Stone, and Alexandros Leiba, Andrew McKeon, Alexey Melnikov, Chris Newman, Aaron Stone, and
Vellis provided helpful suggestions and corrections. Alexandros Vellis provided helpful suggestions and corrections.
Author's Address Author's Address
Ned Freed Ned Freed
Sun Microsystems Oracle
800 Royal Oaks 800 Royal Oaks
Monrovia, CA 91016-6347 Monrovia, CA 91016-6347
USA USA
Phone: +1 909 457 4293 Phone: +1 909 457 4293
Email: ned.freed@mrochek.com Email: ned.freed@mrochek.com
 End of changes. 11 change blocks. 
17 lines changed or deleted 27 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/