draft-ietf-sieve-external-lists-02.txt   draft-ietf-sieve-external-lists-03.txt 
Sieve Working Group A. Melnikov Sieve Working Group A. Melnikov
Internet-Draft Isode Limited Internet-Draft Isode Limited
Intended status: Standards Track B. Leiba Intended status: Standards Track B. Leiba
Expires: November 20, 2010 Huawei Technologies Expires: April 25, 2011 Huawei Technologies
May 19, 2010 October 22, 2010
Sieve Extension: Externally Stored Lists Sieve Extension: Externally Stored Lists
draft-ietf-sieve-external-lists-02 draft-ietf-sieve-external-lists-03
Abstract Abstract
The Sieve scripting language can be used to implement whitelisting, The Sieve scripting language can be used to implement whitelisting,
blacklisting, personal distribution lists, and other sorts of list blacklisting, personal distribution lists, and other sorts of list
matching. Currently, this requires that all members of such lists be matching. Currently, this requires that all members of such lists be
hardcoded in the script itself. Whenever a member of a list is added hardcoded in the script itself. Whenever a member of a list is added
or deleted, the script needs to be updated and possibly uploaded to a or deleted, the script needs to be updated and possibly uploaded to a
mail server. mail server.
This document defines a Sieve extension for accessing externally This document defines a Sieve extension for accessing externally
stored lists -- lists whose members are stored externally to the stored lists -- lists whose members are stored externally to the
script, such as using LDAP (RFC 4510), ACAP (RFC 2244), or relational script, such as using LDAP (RFC 4510), ACAP (RFC 2244), or relational
databases. databases.
ToDo ToDo
o Need a way to advertise supported URI schemas in ManageSieve and o Do we need support for URI schemes in ihave? From IETF 77
ihave. From IETF 77 minutes: "Can use ihave to test if a URI is minutes: "Can use ihave to test if a URI is valid, both that the
valid, both that the scheme is supported and that the URI can be scheme is supported and that the URI can be retrieved/queried."
retrieved/queried."
o Do we need to say anything about comparators? We can be silent
(as now), we can say that comparators MAY be ignored as a list-
specific thing, or we can say that comparators MUST NOT be used.
o Should we add a mandatory-to-implement tag? Ned suggests (and I
agree) that it might be good to add a registry of well-defined
strings that can be used instead of URIs, and define the initial
string "pab" to represent the user's personal address book.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on November 20, 2010. This Internet-Draft will expire on April 25, 2011.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions used in this document . . . . . . . . . . . . . . 3 1.1. Conventions used in this document . . . . . . . . . . . . . 4
2. Extlists extension . . . . . . . . . . . . . . . . . . . . . 3 2. Extlists extension . . . . . . . . . . . . . . . . . . . . . 4
2.1. Capability Identifier . . . . . . . . . . . . . . . . . . . . 3 2.1. Capability Identifier . . . . . . . . . . . . . . . . . . . 4
2.2. :list match type for supported tests . . . . . . . . . . . . 3 2.2. :list match type for supported tests . . . . . . . . . . . . 4
2.3. :list tagged argument to the "redirect" action . . . . . . . 4 2.3. :list tagged argument to the "redirect" action . . . . . . . 5
2.4. Syntax of an externally stored list name . . . . . . . . . . 5 2.4. Other uses for external lists . . . . . . . . . . . . . . . 6
2.5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.5. Syntax of an externally stored list name . . . . . . . . . . 6
2.6. Interaction with ManageSieve . . . . . . . . . . . . . . . . 6
2.7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Security Considerations . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . 9
4.1. Registration of Sieve extension . . . . . . . . . . . . . . 9
4.2. Registration of ManageSieve capability . . . . . . . . . . . 9
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . . . 7 6.1. Normative References . . . . . . . . . . . . . . . . . . . . 10
6.2. Informative References . . . . . . . . . . . . . . . . . . . 8 6.2. Informative References . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
This document specifies an extension to the Sieve language [Sieve] This document specifies an extension to the Sieve language [RFC5228]
for checking membership in an external list or for redirecting for checking membership in an external list or for redirecting
messages to an external list of recipients. An "external list" is a messages to an external list of recipients. An "external list" is a
list whose members are stored externally to the Sieve script, such as list whose members are stored externally to the Sieve script, such as
using LDAP [LDAP], ACAP [ACAP], or relational databases. using LDAP [RFC4510], ACAP [RFC2244], or relational databases.
This extension adds a new match type to apply to supported tests, and This extension adds a new match type to apply to supported tests, and
a new tagged argument to the "redirect" action. a new tagged argument to the "redirect" action.
1.1. Conventions used in this document 1.1. Conventions used in this document
Conventions for notations are as in [Sieve] section 1.1, including Conventions for notations are as in [RFC5228] section 1.1, including
the use of [ABNF]. the use of [RFC5234].
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 [Kwds]. document are to be interpreted as described in [RFC2119].
2. Extlists extension 2. Extlists extension
2.1. Capability Identifier 2.1. Capability Identifier
The capability string associated with the extension defined in this The capability string associated with the extension defined in this
document is "extlists". document is "extlists".
2.2. :list match type for supported tests 2.2. :list match type for supported tests
skipping to change at page 3, line 49 skipping to change at page 4, line 49
The new ":list" match type changes the interpretation of the "key- The new ":list" match type changes the interpretation of the "key-
list" parameter (the second parameter) to supported tests. When the list" parameter (the second parameter) to supported tests. When the
match type is ":list", the key-list becomes a list of names of match type is ":list", the key-list becomes a list of names of
externally stored lists. The external lists are queried, perhaps externally stored lists. The external lists are queried, perhaps
through a list-specific mechanism, and the test evaluates to "true" through a list-specific mechanism, and the test evaluates to "true"
if any of the specified values matches any member of one or more of if any of the specified values matches any member of one or more of
the lists. the lists.
Implementations MUST support "address", "envelope" and "header" Implementations MUST support "address", "envelope" and "header"
tests. Implementations that include the Variables extension tests. Implementations that include the Variables extension
[Variables] MUST also support "string" tests. [RFC5229] MUST also support "string" tests.
Implementations MAY support other tests but MUST raise an error Implementations MAY support other tests but MUST raise an error
(which SHOULD be a compile-time error, but MAY be a runtime error) (which SHOULD be a compile-time error, but MAY be a runtime error)
when a script uses :list with a test for which it is not supported. when a script uses :list with a test for which it is not supported.
To maintain interoperability, other tests that can be used with :list To maintain interoperability, other tests that can be used with :list
SHOULD be documented in a specification that defines a capability SHOULD be documented in a specification that defines a capability
string that can be tested (in a "require" statement, or using ihave string that can be tested (in a "require" statement, or using ihave
[Ihave]). [RFC5463]).
For example, testing ':header ["to", "cc"]' against a list would For example, testing ':header ["to", "cc"]' against a list would
cause each "to" and "cc" value, ignoring leading and trailing cause each "to" and "cc" value, ignoring leading and trailing
whitespace, to be queried. When any value is found to belong to the whitespace, to be queried. If any value is found to belong to the
list, the queries stop and the test returns "true". If no value list, the test returns "true". If no value belongs to the list, the
belongs to the list, the test returns "false". test returns "false". Once a value is found in the list, there is no
need for the query mechanism to look further.
For some lists, the Sieve engine might directly retrieve the list and For some lists, the Sieve engine might directly retrieve the list and
make its own comparison. Other lists might not work that way -- they make its own comparison. Other lists might not work that way -- they
might provide a way to ask if a value is in the list, but not permit might provide a way to ask if a value is in the list, but not permit
retrieval of the list itself. It is up to the Sieve implementation retrieval of the list itself. It is up to the Sieve implementation
to understand how to interact with any supported list. If the Sieve to understand how to interact with any supported list. If the Sieve
engine is permanently unable to query the list (perhaps because the engine is permanently unable to query the list (perhaps because the
list doesn't support the required operation), the test MUST result in list doesn't support the required operation), the test MUST result in
a runtime error in the Sieve script. a runtime error in the Sieve script.
See Section 2.4 for the detailed description of syntax used for See Section 2.5 for the detailed description of syntax used for
naming externally stored lists. naming externally stored lists.
2.3. :list tagged argument to the "redirect" action 2.3. :list tagged argument to the "redirect" action
Usage: redirect :list <ext-list-name: string> Usage: redirect :list <ext-list-name: string>
The "redirect" action with the ":list" argument is used to send the The "redirect" action with the ":list" argument is used to send the
message to one or more email addresses stored in the externally message to one or more email addresses stored in the externally
stored list 'ext-list-name'. This variant of the redirect command stored list 'ext-list-name'. This variant of the redirect command
can be used to implement a personal distribution list. can be used to implement a personal distribution list.
skipping to change at page 5, line 9 skipping to change at page 6, line 9
In cases where, for example, a list contains hashed email address In cases where, for example, a list contains hashed email address
values or an email address pattern ("sz*@example.com", values or an email address pattern ("sz*@example.com",
"*+ietf@example.net"), the Sieve engine will not be able to redirect "*+ietf@example.net"), the Sieve engine will not be able to redirect
to that list, and responsibility must pass to the list handler. to that list, and responsibility must pass to the list handler.
If neither the Sieve engine nor the list handler can enumerate (or If neither the Sieve engine nor the list handler can enumerate (or
iterate) the list, or the list does not resolve to email addresses, iterate) the list, or the list does not resolve to email addresses,
the situation MUST result in a runtime error in the Sieve script. the situation MUST result in a runtime error in the Sieve script.
See Section 2.4 for the detailed description of syntax used for See Section 2.5 for the detailed description of syntax used for
naming externally stored lists. naming externally stored lists.
2.4. Syntax of an externally stored list name 2.4. Other uses for external lists
A name of an externally stored list is always an absolute URI [URI]. The uses for external lists specified here represent the useful cases
Implementations might find URLs such as [LDAP], [CardDAV], or and situations at the time of this writing. Other uses for external
[TAG-URI] to be useful for naming external lists. lists, using other Sieve features, might be devised in the future,
and such uses can be described in extensions to this document.
The "tag" URI scheme [TAG-URI] MUST be supported, and can be used to 2.5. Syntax of an externally stored list name
A name of an externally stored list is always an absolute URI
[RFC3986]. Implementations might find URIs such as [RFC4510],
[I-D.ietf-vcarddav-carddav], or [RFC4151] to be useful for naming
external lists.
The "tag" URI scheme [RFC4151] MUST be supported, and can be used to
represent opaque, but user friendlier identifiers. Resolution of represent opaque, but user friendlier identifiers. Resolution of
such identifiers is going to be implementation specific and it can such identifiers is going to be implementation specific and it can
help in hiding the complexity of an implementation from end users. help in hiding the complexity of an implementation from end users.
For example, an implementation can provide a web interface for For example, an implementation can provide a web interface for
managing lists of users stored in LDAP. Requiring users to know managing lists of users stored in LDAP. Requiring users to know
generic LDAP URL syntax might not be very practical, due to its generic LDAP URI syntax might not be very practical, due to its
complexity. An implementation can instead use a fixed tag URI prefix complexity. An implementation can instead use a fixed tag URI prefix
such as "tag:example.com,<date>:" (where <date> can be, for example, such as "tag:example.com,<date>:" (where <date> can be, for example,
a date generated once on installation of the web interface and left a date generated once on installation of the web interface and left
untouched upon upgrades) and the prefix doesn't even need to be shown untouched upon upgrades) and the prefix doesn't even need to be shown
to end users. to end users.
2.5. Examples 2.6. Interaction with ManageSieve
Example 1 uses the "envelope" option [Sieve] and the "subaddress" This extension defines the following new capability for ManageSieve
extension [Subaddress]: (see [RFC5804] section 1.7):
EXTLISTS - A space-separated list of URI schema parts [RFC3986] for
supported externally stored list types. This capability MUST be
returned if the Sieve implementation supports the "extlists"
extension defined in this document.
This also extends the ManageSieve ABNF as follows:
single-capability =/ DQUOTE "EXTLISTS" DQUOTE SP ext-list-types CRLF
; single-capability is defined in [RFC5804]
ext-list-types = string
; space separated list of URI schema parts
; for supported externally stored list types.
; MUST NOT be empty.
2.7. Examples
This example uses the "envelope" option [RFC5228] and the
"subaddress" extension [RFC5233]:
require ["extlists", "envelope", "subaddress"]; require ["extlists", "envelope", "subaddress"];
# Submission from list members is sent to all members # Submission from list members is sent to all members
if allof (envelope :detail :list "to" if allof (envelope :detail :list "to"
"tag:example.com,2009-05-28:mylist", "tag:example.com,2009-05-28:mylist",
header :list "from" header :list "from"
"tag:example.com,2009-05-28:mylist") { "tag:example.com,2009-05-28:mylist") {
redirect :list "tag:example.com,2009-05-28:mylist"; redirect :list "tag:example.com,2009-05-28:mylist";
} }
This example uses the "currentdate" test [RFC5260] and a list
containing the dates of local holidays. If today is a holiday, the
script will notify [RFC5435] the user via XMPP [RFC5437] about the
message.
require ["extlists", "date", "enotify"];
if currentdate :list "date"
"tag:example.com,2010-01-01:localHolidays" {
notify "xmpp:romeo@im.example.com";
}
This example uses a personal address book, along with spamtest
[RFC5235] and the relational extension [RFC5231] to give a different
level of spam tolerance to known senders.
require ["envelope", "extlists", "fileinto", "spamtest",
"relational", "comparator-i;ascii-numeric"];
if allof (
envelope :list "from" "tag:example.com,2010-04-10:pab",
spamtest :value "ge" :comparator "i;ascii-numeric" "8"
)
{ /* Known: allow high spam score */
fileinto "spam";
}
elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3"
{ /* Unknown: less tolerance in spam score */
fileinto "spam";
}
3. Security Considerations 3. Security Considerations
Security considerations related to the "address"/"envelope"/"header" Security considerations related to the "address"/"envelope"/"header"
tests and "redirect" action discussed in [Sieve] also apply to this tests and "redirect" action discussed in [RFC5228] also apply to this
document. document.
External list memberships ought to be treated as if they are an External list memberships ought to be treated as if they are an
integral part of the script, so a temporary failure to access an integral part of the script, so a temporary failure to access an
external list SHOULD be handled in the same way as a temporary external list SHOULD be handled in the same way as a temporary
failure to retrieve the Sieve script itself. failure to retrieve the Sieve script itself.
For example, if the Sieve script is stored in the Lightweight For example, if the Sieve script is stored in the Lightweight
Directory Access Protocol [LDAP] and the script can't be retrieved Directory Access Protocol [RFC4510] and the script can't be retrieved
when a message is processed (perhaps the LDAP server is unavailable), when a message is processed (perhaps the LDAP server is unavailable),
then the Sieve engine might delay message delivery until the script then the Sieve engine might delay message delivery until the script
can be retrieved successfully. Similarly, if an external list is can be retrieved successfully. Similarly, if an external list is
stored in LDAP and that LDAP server is unavailable, the Sieve engine stored in LDAP and that LDAP server is unavailable, the Sieve engine
would take the same action -- delay message delivery and try again would take the same action -- delay message delivery and try again
later. later.
Protocols/APIs used to retrieve/verify external list membership MUST Protocols/APIs used to retrieve/verify external list membership MUST
provide an appropriate level of confidentiality and authentication. provide an appropriate level of confidentiality and authentication.
Usually, that will be at least the same level of confidentiality as Usually, that will be at least the same level of confidentiality as
skipping to change at page 7, line 7 skipping to change at page 9, line 26
Implementations SHOULD use such features whenever they can. Implementations SHOULD use such features whenever they can.
Many organizations support external lists with thousands of Many organizations support external lists with thousands of
recipients. In order to avoid mailbombs when redirecting a message recipients. In order to avoid mailbombs when redirecting a message
to an externally stored list, implementations SHOULD enforce limits to an externally stored list, implementations SHOULD enforce limits
on the number of recipients and/or on domains to which such on the number of recipients and/or on domains to which such
recipients belong. recipients belong.
4. IANA Considerations 4. IANA Considerations
The following template specifies the IANA registration of the notify 4.1. Registration of Sieve extension
Sieve extension specified in this document:
The following template specifies the IANA registration of the Sieve
extension specified in this document:
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve extension Subject: Registration of new Sieve extension
Capability name: extlists Capability name: extlists
Description: adds the ':list' match type to certain Sieve tests, and Description: adds the ':list' match type to certain Sieve tests, and
the ':list' argument to the 'redirect' action. The ':list' match the ':list' argument to the 'redirect' action. The ':list' match
type changes tests to match values against values stored in one or type changes tests to match values against values stored in one or
more externally stored lists. The ':list' argument to the redirect more externally stored lists. The ':list' argument to the redirect
action changes the redirect action to forward the message to email action changes the redirect action to forward the message to email
addresses stored in the externally stored list. addresses stored in the externally stored list.
RFC number: this RFC RFC number: this RFC
Contact address: Contact address:
The Sieve discussion list <sieve@ietf.org> The 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.
4.2. Registration of ManageSieve capability
The following requests IANA to register a new ManageSieve Capability
according to the IANA registration template specified in [RFC5804]:
To: iana@iana.org
Subject: ManageSieve Capability Registration
Capability name: extlists
Description: This capability is returned if the server supports the
"extlists" [RFCXXXX] Sieve extension.
Relevant publications: this RFC, Section 2.6
Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG
5. Acknowledgements 5. Acknowledgements
Thanks to Alexandros Vellis, Nigel Swinson, Ned Freed, Kjetil Torgrim Thanks to Alexandros Vellis, Nigel Swinson, Ned Freed, Kjetil Torgrim
Homme, Dave Cridland, Cyrus Daboo, Pete Resnick, and Robert Burrell Homme, Dave Cridland, Cyrus Daboo, Pete Resnick, and Robert Burrell
Donkin for ideas, comments and suggestions. Donkin for ideas, comments and suggestions. Kristin Hubner also
helped greatly with the examples.
6. References 6. References
6.1. Normative References 6.1. Normative References
[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Specifications: ABNF", RFC 5234, January 2008. Requirement Levels", BCP 14, RFC 2119, March 1997.
[Kwds] Bradner, S., "Key words for use in RFCs to Indicate [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Requirement Levels", RFC 2119, March 1997. Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[Sieve] Guenther, P. and T. Showalter, "Sieve: An Email Filtering [RFC4151] Kindberg, T. and S. Hawke, "The 'tag' URI Scheme",
RFC 4151, October 2005.
[RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering
Language", RFC 5228, January 2008. Language", RFC 5228, January 2008.
[TAG-URI] Kindberg, T. and S. Hawke, "The 'tag' URI Scheme", [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
RFC 4151, October 2005. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC5804] Melnikov, A. and T. Martin, "A Protocol for Remotely
Resource Identifier (URI): Generic Syntax", STD 66, Managing Sieve Scripts", RFC 5804, July 2010.
RFC 3986, January 2005.
6.2. Informative References 6.2. Informative References
[ACAP] Newman, C. and J. Myers, "ACAP -- Application [I-D.ietf-vcarddav-carddav]
Configuration Access Protocol", RFC 2244, November 1997. Daboo, C., "vCard Extensions to WebDAV (CardDAV)",
draft-ietf-vcarddav-carddav-10 (work in progress),
[CardDAV] Daboo, C., "vCard Extensions to WebDAV (CardDAV)", work in November 2009.
progress, draft-ietf-vcarddav-carddav, November 2009.
[Ihave] Freed, N., "Sieve Email Filtering: Ihave Extension", [RFC2244] Newman, C. and J. Myers, "ACAP -- Application
RFC 5463, March 2009. Configuration Access Protocol", RFC 2244, November 1997.
[LDAP] Zeilenga, K., "Lightweight Directory Access Protocol [RFC4510] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Technical Specification Road Map", RFC 4510, (LDAP): Technical Specification Road Map", RFC 4510,
June 2006. June 2006.
[Subaddress] [RFC5229] Homme, K., "Sieve Email Filtering: Variables Extension",
Murchison, K., "Sieve Email Filtering: Subaddress RFC 5229, January 2008.
[RFC5231] Segmuller, W. and B. Leiba, "Sieve Email Filtering:
Relational Extension", RFC 5231, January 2008.
[RFC5233] Murchison, K., "Sieve Email Filtering: Subaddress
Extension", RFC 5233, January 2008. Extension", RFC 5233, January 2008.
[Variables] [RFC5235] Daboo, C., "Sieve Email Filtering: Spamtest and Virustest
Homme, K., "Sieve Email Filtering: Variables Extension", Extensions", RFC 5235, January 2008.
RFC 5229, January 2008.
[RFC5260] Freed, N., "Sieve Email Filtering: Date and Index
Extensions", RFC 5260, July 2008.
[RFC5435] Melnikov, A., Leiba, B., Segmuller, W., and T. Martin,
"Sieve Email Filtering: Extension for Notifications",
RFC 5435, January 2009.
[RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification
Mechanism: Extensible Messaging and Presence Protocol
(XMPP)", RFC 5437, January 2009.
[RFC5463] Freed, N., "Sieve Email Filtering: Ihave Extension",
RFC 5463, March 2009.
Authors' Addresses Authors' Addresses
Alexey Melnikov Alexey Melnikov
Isode Limited Isode Limited
5 Castle Business Village 5 Castle Business Village
36 Station Road 36 Station Road
Hampton, Middlesex TW12 2BX Hampton, Middlesex TW12 2BX
UK UK
 End of changes. 42 change blocks. 
72 lines changed or deleted 180 lines changed or added

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