draft-freed-sieve-notary-01.txt   draft-freed-sieve-notary-02.txt 
Network Working Group N. Freed Network Working Group N. Freed
Internet-Draft Sun Microsystems Internet-Draft Sun Microsystems
Expires: February 1, 2009 July 31, 2008 Expires: May 21, 2009 November 17, 2008
Sieve Email Filtering: Notary Extension Sieve Email Filtering: Delivery Status Notifications Extension
draft-freed-sieve-notary-01 draft-freed-sieve-notary-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 February 1, 2009. This Internet-Draft will expire on May 21, 2009.
Abstract Abstract
This document describes the "dsn-envelope" and "dsn-redirect" This document describes the "dsn-envelope" and "dsn-redirect"
extensions to the Sieve email filtering language. The "dsn-envelope" extensions to the Sieve email filtering language. The "dsn-envelope"
extension provides access to additional envelope information provided extension provides access to additional envelope information provided
by the delivery status notification extension to SMTP defined in RFC by the delivery status notification extension to SMTP defined in RFC
3461. The "dsn-redirect" extension extends Sieve's redirect action 3461. The "dsn-redirect" extension extends Sieve's redirect action
to provide control over delivery status notification parameters. to provide control over delivery status notification parameters.
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Added the dsn-redirect extension. Added the dsn-redirect 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 dsn-envelope extension. envelope-part strings defined by the dsn-envelope extension.
Fleshed out the dsn-redirect extension. Fleshed out the dsn-redirect extension.
Changed document title to agree with new extension names.
Added some examples.
Fixed more typos.
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 2, line 42 skipping to change at page 2, line 48
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
specification of the new recipient address. The "dsn-redirect" specification of the new recipient address. The "dsn-redirect"
extension extends redirect to allow specification of some fields extension extends redirect to allow specification of some fields
defined by the delivery status notification SMTP extension. defined by the delivery status notification SMTP extension.
2. Conventions used in this document 2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]. document are to be interpreted as described in [RFC2119].
The terms used to describe the various components of the Sieve The terms used to describe the various components of the Sieve
language are taken from Section 1.1 of [RFC5228]. language are taken from Section 1.1 of [RFC5228].
This document uses the ABNF notation specified in [RFC5234] and This document uses the ABNF notation specified in [RFC5234] and
refers to the ABNF production notify-esmtp-value defined in Section refers to the ABNF production notify-esmtp-value defined in Section
4.1 of [RFC3461]. 4.1 of [RFC3461].
3. Capability Identifier 3. Capability Identifier
skipping to change at page 4, line 12 skipping to change at page 4, line 19
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.
The "relational" extension [RFC5231] adds a match type called The "relational" extension [RFC5231] adds a match type called
":count". The count of an envelope test of with an envelope-part of ":count". The count of an envelope test of with an envelope-part of
"orcpt", "ret", and "envid" is 1 if the corresponding SMTP parameter "orcpt", "ret", and "envid" is 1 if the corresponding SMTP parameter
is present and 0 otherwise. The count of an envelope test with an is present and 0 otherwise. The count of an envelope test with an
envelope-part of "notify" is equal to the number of notification envelope-part of "notify" is equal to the number of notification
conditions specified and 0 if the NOTIFY parameter is not present. conditions specified and 0 if the NOTIFY parameter is not present.
4.1. Examples
The fact that the notify envelope-part operates on a list of values
makes it easy to check to see if a given value is present without
havingt to worry about other values:
require ["envelope", "dsn-envelope"];
# Check whether SUCCESS notifications were requested,
# irrespective of any other requests that were made
if envelope "notify" "SUCCESS"
{
# do whatever
}
Checking to see if a given request is the only one present is a
little trickier, however:
require ["envelope", "dsn-envelope", "relational",
"comparator-i;ascii-numeric"];
# Check whether only FAILURE notifications were requested
if allof ( envelope "notify" "FAILURE",
envelope :comparator "i;ascii-numeric"
:count "eq" "notify" "1"
)
{
# do whatever
}
The orcpt envelope-part contains an address type indicator in
addition to an address, which must be taken into account:
require ["envelope", "dsn-envelope"];
# See if the orcpt is an RFC822 address in the example.com
# domain
if envelope :matches "orcpt" "rfc822;*@example.com"
{
# do whatever
}
5. Dsn-redirect extension 5. Dsn-redirect extension
The "dsn-redirect" extension does not define any new tests or The "dsn-redirect" extension does not define any new tests or
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] [RET] <address: string> Usage: redirect [NOTIFY] [RET] <address: string>
The syntax for the NOTIFY and RET arguments are: The syntax for the NOTIFY and RET arguments are:
skipping to change at page 4, line 50 skipping to change at page 6, line 5
The dsn-envelope extension provides access to additional message The dsn-envelope extension provides access to additional message
envelope information. This is not believed to raise any additional envelope information. This is not believed to raise any additional
security issues beyond those for the Sieve "envelope" test. security issues beyond those for the Sieve "envelope" test.
The dsn-redirect extension allows specification of the delivery The dsn-redirect extension allows specification of the delivery
status notification's NOTIFY parameter which can cause the generation status notification's NOTIFY parameter which can cause the generation
of notification messages that might otherwise not be generated, of notification messages that might otherwise not be generated,
especially if notification in the event of successful delivery is especially if notification in the event of successful delivery is
required. Sites which limit the ability to request success required. Sites which limit the ability to request success
notifications will also need to restrict the ability to request then notifications will also need to restrict the ability to request them
using the dsn-redirect extension. using the dsn-redirect extension.
All of the security considerations given in the base Sieve All of the security considerations given in the base Sieve
specification also apply to this extension. specification also apply to this extension.
7. IANA Considerations 7. IANA Considerations
The following template specifies the IANA registration of the Sieve The following template specifies the IANA registration of the Sieve
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: dsn-envelope Capability name: dsn-envelope
Description: The "dsn-envelope" extension extends the envelope Description: The "dsn-envelope" 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 <ietf-mta-filters@imc.org>
Capability name: dsn-envelope Capability name: dsn-redirect
Description: The "dsn-redirect" extension extends the redirect Description: The "dsn-redirect" 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 <ietf-mta-filters@imc.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.
skipping to change at page 6, line 15 skipping to change at page 7, line 16
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.
8.2. Informative references 8.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.
Appendix A. Acknowledgements
Cyrus Daboo, Derek Diget, Philip Guenther, Arnt Gulbrandsen, Alexey
Melnikov, and Alexandros Vellis provided helpful suggestions and
corrections.
Author's Address Author's Address
Ned Freed Ned Freed
Sun Microsystems Sun Microsystems
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. 9 change blocks. 
7 lines changed or deleted 61 lines changed or added

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