draft-freed-sieve-notary-07.txt   draft-freed-sieve-notary-08.txt 
Network Working Group N. Freed Network Working Group N. Freed
Internet-Draft Oracle Internet-Draft Oracle
Intended status: Standards Track March 24, 2010 Intended status: Standards Track May 3, 2010
Expires: September 25, 2010 Expires: November 4, 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-07 draft-freed-sieve-notary-08
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, respectively. The "redirect-dsn" and
deliverby" extensions extend Sieve's redirect action to provide "redirect-deliverby" extensions extend Sieve's redirect action to
control over delivery status notification and deliver-by parameters, provide control over delivery status notification and deliver-by
respectively. parameters, respectively.
Change History (to be removed prior to publication as an RFC Change History (to be removed prior to publication as an RFC
Correct RFC 2852 section reference.
Removed some extraneous [ characters from a couple of figures.
Clarified orcpt decoding. Clarified orcpt decoding.
Changed the ABNF for notary values to disallow spaces. 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.
skipping to change at page 2, line 10 skipping to change at page 2, line 14
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.
Added requirements text regarding envelope sender address selection.
Added various clarifications about negative by-time values.
Added a pointer to the conventions section to where Sieve errors are
discussed.
Clearified test failure text in both envelope extensions.
Addeed the ability to deal with by-times as either absolute ISO 8601
or relative integer values.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 31 skipping to change at page 2, line 47
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 25, 2010. This Internet-Draft will expire on November 4, 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 24 skipping to change at page 3, line 38
information added to the SMTP envelope by SMTP extensions cannot be information added to the SMTP envelope by SMTP extensions cannot be
accessed. 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
specification of the new recipient address. The "redirect-dsn" specification of the new recipient address. The "redirect-dsn"
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.
"redirect-deliverby" in turn provides the ability to set a time limit "redirect-deliverby" in turn provides the ability to set a time limit
for delivery as specified in RFC 2852 [RFC2852]. for delivery as specified in RFC 2852 [RFC2852].
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 [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]. The nature and
handling of Sieve errors is described in Section 2.10.6.
This document uses the ABNF notation specified in [RFC5234], and This document uses the ABNF notation specified in [RFC5234], and
refers to the ABNF productions notify-esmtp-value defined in Section refers to the ABNF productions notify-esmtp-value defined in Section
4.1 of [RFC3461]. 4.1 of [RFC3461].
3. Capability Identifier 3. Capability Identifiers
The capability strings associated with the extensions defined in this The capability strings associated with the extensions defined in this
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
skipping to change at page 4, line 21 skipping to change at page 4, line 35
notify - Match the list of notification conditions, or NOTIFY notify - Match the list of notification conditions, or NOTIFY
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" is never combined with any other value.
orcpt - Match the original recipient, or ORCPT, value associated orcpt - Match the original recipient, or ORCPT, value associated
with the TO address used in the SMTP RCPT TO command that resulted with the TO address used in the SMTP RCPT TO command that resulted
in this message getting delivered to this user, with xtext in this message getting delivered to this user, with xtext
encoding removed. The syntax and semantics of the ORCPT parameter encoding removed. The syntax and semantics of the ORCPT parameter
are defined 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]. The possible
possible return of content values are "FULL" and "HDRS". 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].
All of these tests fail unconditionally if the specified envelope The envelope test fails unconditionally for each of these envelope-
parameter does not exist for the current message or recipient. part strings if the specified envelope 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.
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 with an envelope-part of ":count". The count of an envelope test 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
skipping to change at page 6, line 8 skipping to change at page 6, line 33
# See if the orcpt is an RFC822 address in the example.com # See if the orcpt is an RFC822 address in the example.com
# domain # domain
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 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]. These new envelope parts are defined in Section 5 of [RFC5228] and an optional :zone tagged argument. This updates the
[RFC2852]. usage description for envelope to:
bytime - Match the initial integer part of the deliver-by Usage: envelope [COMPARATOR] [ADDRESS-PART]
extension's BY parameter specified in the SMTP MAIL FROM command. [MATCH-TYPE] [:zone <time-zone: string>]
<envelope-part: string-list>
<key-list: string-list>
These new envelope parts correspond to the new MAIL FROM parameters
defined in Section 4 of [RFC2852]. They are:
bytimeabsolute - Match the current value of the initial integer part
of the deliver-by extension's BY parameter on the SMTP MAIL FROM
command, converted into an absolute time represented in restricted
ISO 8601 format. The restricted ISO 8601 format is specified by
the date-time ABNF production given in [RFC3339], Section 5.6,
with the added restrictions that the letters "T" and "Z" MUST be
in upper case, and a time zone offset of zero MUST be represented
by "Z" and not "+00:00".
bytimerelative - Match the current value of the initial integer part
of the deliver-by extension's BY parameter specified in the SMTP
MAIL FROM command.
bymode - 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 bytrace - Match the trace modifier computed from the by-trace
modifier on the deliver-by extension's BY parameter. The possible modifier on the deliver-by extension's BY parameter. The possible
values are "trace" and "" (the empty string). These values values are "trace" and "" (the empty string). These values
correspond to the presence or absence of the by-trace "T" modifier correspond to the presence or absence of the by-trace "T" modifier
respectively. respectively.
All of these tests fail unconditionally if the BY SMTP MAIL FROM The envelope test fails unconditionally for each of these envelope-
parameter does not exist for the current message or recipient. part strings if the BY SMTP MAIL FROM parameter does not exist for
the current message or recipient.
The new :zone argument specifies a time zone offset string that any
bytimeabsolute value is to be shifted to prior to testing. :zone has
no effect on envelope-parts other than bytimeabsolute. The value of
time zone offset string MUST be an offset relative to UTC with the
following syntax:
time-zone = ( "+" / "-" ) 4DIGIT
The "+" or "-" indicates whether the time-of-day is ahead of (i.e.,
east of) or behind (i.e., west of) UTC. The first two digits
indicate the number of hours difference from Universal Time, and the
last two digits indicate the number of minutes difference from
Universal Time. Note that this agrees with the RFC 2822 format for
time zone offsets, not the ISO 8601 format. The local time zone MUST
be used for bytimeabsolute if the :zone argument is omitted.
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.
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 with an envelope-part of ":count". The count of an envelope test with an envelope-part of
"bytime", "bymode", and "bytrace" is 1 if the BY parameter is present "bytime", "bymode", and "bytrace" is 1 if the BY parameter is present
and 0 otherwise. and 0 otherwise.
It should be noted that the deliver-by by-time is decremented as the It is important to note that the deliver-by by-time is decremented as
message passes through the transport infrastructure. Accordingly, it the message passes through the transport infrastructure.
is not possible to tell what the message originator set the value to, Accordingly, it is not possible to tell what the message originator
only the amount of time remaining at the moment the sieve is run. set the value to, only the amount of time remaining at the moment the
sieve is run. Additionally, note that bytimerelative values can be
negative, making it necessary to either perform additional checks or
else use a comparator which, unlike i;ascii-numeric, is capable of
handling signed integers.
5.1. Example 5.1. Example
As noted above, this extension does not provide access to the As noted above, this extension does not provide access to the
originator's initial by-time setting for the simple reason that this originator's initial by-time setting for the simple reason that this
information is not part of the envelope. It can, however, be used to information is not part of the envelope. It can, however, be used to
check and see if the message was delivered within the alloted time. check and see if the message was delivered within the alloted time.
Note the additional check to see if the value is negative.
require ["envelope", "envelope-deliverby", "relational", require ["envelope", "envelope-deliverby", "relational",
"comparator-i;ascii-numeric"]; "comparator-i;ascii-numeric"];
# Check to see if this message didn't make it in the time alloted by # Check to see if this message didn't make it in the time alloted by
# the originator. # the originator.
if envelope :value "eq" :comparator "i;ascii-numeric" "bytime" "0" if anyof (envelope :contains "bytimerelative" "-",
envelope :value "eq" :comparator "i;ascii-numeric"
"bytimerelative" "0")
{ {
# do whatever # do whatever
} }
This operation can be done more simply if the date and variables
extensions are available:
require ["envelope", "envelope-deliverby", "relational", "date"
"variables"];
# Check to see if this message didn't make it in the time alloted by
# the originator.
if currentdate :matches "iso8601" "*" {
set "cdate" "${0}";
if envelope :value "ge" "bytimeabsolute" "${cdate}")
{
# do whatever
}
}
6. redirect-dsn extension 6. redirect-dsn extension
The "redirect-dsn" extension does not define any new tests or The "redirect-dsn" 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 "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 ("NEVER" / notify-esmtp-list) DQUOTE notify-value = DQUOTE ("NEVER" / notify-esmtp-list) DQUOTE
notify-esmtp-list = notify-list-element *("," notify-list-element) notify-esmtp-list = notify-list-element *("," notify-list-element)
RET = ":ret" ret-value RET = ":ret" ret-value
skipping to change at page 7, line 44 skipping to change at page 9, line 34
The notify-list-element 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. MAIL FROM address selection
RFC 5228 does not require any particular envelope sender address be
associated with redirected messages. However, the redirect-dsn
extension isn't terribly useful if the place where the delivery
status notifications are sent isn't known. Accordingly, when either
:notify or :ret is specified and the envelope sender address isn't
empty, implementations MUST set the envelope sender address to the
address of the sieve owner.
6.2. Example
One possible use of :notify on redirect is to combine the copy One possible use of :notify on redirect is to combine the copy
extension [RFC3894] with the ability to suppress nondelivery extension [RFC3894] with the ability to suppress nondelivery
notifications to generate a private copy of selected messages with no notifications to generate a private copy of selected messages with no
side effects or error notifications: side effects or error notifications:
require ["copy", "redirect-dsn"]; require ["copy", "redirect-dsn"];
# Make a private copy of messages from user@example.com # Make a private copy of messages from user@example.com
if address "from" "user@example.com" if address "from" "user@example.com"
{ {
redirect :copy :notify "NEVER" "elsewhere@example.com"; redirect :copy :notify "NEVER" "elsewhere@example.com";
} }
7. redirect-deliverby extension 7. redirect-deliverby extension
The "redirect-deliverby" extension does not define any new tests or The "redirect-deliverby" extension does not define any new tests or
actions, rather, it adds three new arguments, BYTIME, BYMODE, and actions, rather, it adds three new arguments, BYTIME, BYMODE, and
BYTRACE, to the redirect action defined in Section 4.2 of [RFC5228]. BYTRACE, to the redirect action defined in Section 4.2 of [RFC5228].
This updates the usage description for redirect to: This updates the usage description for redirect to:
[
Usage: redirect [:bytime <limit: number> Usage: redirect [:bytimerelative <rlimit: number> /
:bytimeabsolute <alimit:string>
[:bymode "notify"|"return"] [:bytrace]] [:bymode "notify"|"return"] [:bytrace]]
<address: string> <address: string>
:bytime specifies the number of seconds within which the message :bytimerelative specifies the number of seconds within which the
should be delivered. :bymode specifies whether a notification should message should be delivered. This parameter does not allow
be sent or the message simply returned if the time limit is exceeded. specification of negative values; it should not be necessary specify
The default is "return" if :bymode is not specified. See The such values in this context. :bytimeabsolute specifies an absolute
semantics of delivery time limits are specified and discussed at time limit on delivery. The limit in this case is specified in the
length in [RFC2852]. restricted ISO 8601 format specified by the date-time ABN production
given in [RFC3339]
It is an error to specify :bymode and :bytrace without :bytime. :bymode specifies whether a notification should be sent or the
message simply returned if the time limit is exceeded. The default
is "return" if :bymode is not specified. :bytrace, if specified,
activiates message tracing.
The semantics of delivery time limits and these parameters are
specified and discussed at length in [RFC2852].
It is an error to specify either :bymode or :bytrace without either
:bytimeabsolute or :bytimerelative.
When these arguments are specified, they are used to construct the When these arguments are specified, they are used to construct the
corresponding BY ESMTP MAIL FROM parameter. The :bytime value corresponding BY ESMTP MAIL FROM parameter. The :bytimeabsolute or
becomes the by-time, the :bymode becomes the by-mode value, and :bytimerelative value becomes the by-time, the :bymode becomes the
:bytrace sets the by-trace modifier. If the deliver-by extension is by-mode value, and :bytrace sets the by-trace modifier. If the
unavailable, the handling of reredirected message MUST conform to the deliver-by extension is unavailable, the handling of reredirected
semantics specified in [RFC2852] section 4.1.4 for relaying to a message MUST conform to the semantics specified in [RFC2852] section
server that does not support the deliver-by SMTP extension. 4.1.4 for relaying to a server that does not support the deliver-by
SMTP extension.
7.1. Example 7.1. MAIL FROM address selection
RFC 5228 does not require any particular envelope sender address be
associated with redirected messages. However, the redirect-deliverby
extension, like the redirect-dsn extension, isn't terribly useful if
the place where any delivery status notifications are sent isn't
known. Accordingly, when :bymode is specified and the envelope
sender address isn't empty, implementations MUST set the envelope
sender address to the address of the sieve owner.
7.2. Example
The obvious use of "redirect-deliverby" is to specify a limit on The obvious use of "redirect-deliverby" is to specify a limit on
delivery attempts for a redirected message: delivery attempts for a redirected message:
require ["copy", "redirect-deliverby"]; require ["copy", "redirect-deliverby"];
# Send a copy to my cell phone, time out after 10 minutes # Send a copy to my cell phone, time out after 10 minutes
if address "from" "user@example.com" if address "from" "user@example.com"
{ {
redirect :copy :bytime 600 "cellphone@example.com"; redirect :copy :bytimerelative 600 "cellphone@example.com";
}
Limits on delivery after a particular time of day may also be
constructed:
require ["copy", "redirect-deliverby", "date", "variables",
"relational", "comparator-i;ascii-numeric"];
# Send a copy to my cell phone to be delivered before 10PM
if currentdate :value "lt"
:comparator "i;ascii-numeric" "hour" "22"
{
if currentdate :matches "date" "*" {set "date" "${0}";}
if currentdate :matches "zone" "*" {set "zone" "${0}";}
redirect :copy :bytimeabsolute "${date}T20:00:00${zone}"
:bymode "return" "cellphone@example.com";
} }
8. Security Considerations 8. Security Considerations
The envelope-dsn and envelope-deliverby extensions provide access to The envelope-dsn and envelope-deliverby extensions provide access to
additional message envelope information. This is not believed to additional message envelope information. This is not believed to
raise any additional security issues beyond those for the Sieve raise any additional security issues beyond those for the Sieve
"envelope" test. "envelope" test.
The redirect-dsn extension allows specification of the delivery The redirect-dsn extension allows specification of the delivery
skipping to change at page 11, line 12 skipping to change at page 14, line 12
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.
[RFC2852] Newman, D., "Deliver By SMTP Service Extension", RFC 2852, [RFC2852] Newman, D., "Deliver By SMTP Service Extension", RFC 2852,
June 2000. June 2000.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002.
[RFC3461] Moore, K., "Simple Mail Transfer Protocol (SMTP) Service [RFC3461] Moore, K., "Simple Mail Transfer Protocol (SMTP) Service
Extension for Delivery Status Notifications (DSNs)", Extension for Delivery Status Notifications (DSNs)",
RFC 3461, January 2003. RFC 3461, January 2003.
[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.
skipping to change at page 11, line 38 skipping to change at page 14, line 41
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, Barry Cyrus Daboo, Derek Diget, Philip Guenther, Arnt Gulbrandsen, Tero
Leiba, Andrew McKeon, Alexey Melnikov, Chris Newman, Aaron Stone, and Kivinen, Barry Leiba, Andrew McKeon, Alexey Melnikov, Chris Newman,
Alexandros Vellis provided helpful suggestions and corrections. Aaron Stone, and Alexandros Vellis provided helpful suggestions and
corrections.
Author's Address Author's Address
Ned Freed Ned Freed
Oracle 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
 End of changes. 31 change blocks. 
50 lines changed or deleted 177 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/