draft-ietf-sieve-external-lists-03.txt   draft-ietf-sieve-external-lists-04.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: April 25, 2011 Huawei Technologies Expires: May 12, 2011 Huawei Technologies
October 22, 2010 November 8, 2010
Sieve Extension: Externally Stored Lists Sieve Extension: Externally Stored Lists
draft-ietf-sieve-external-lists-03 draft-ietf-sieve-external-lists-04
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.
skipping to change at page 2, line 11 skipping to change at page 2, line 11
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 April 25, 2011. This Internet-Draft will expire on May 12, 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 . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions used in this document . . . . . . . . . . . . . 4 1.1. Conventions used in this document . . . . . . . . . . . . 4
2. Extlists extension . . . . . . . . . . . . . . . . . . . . . 4 2. Extlists extension . . . . . . . . . . . . . . . . . . . . 4
2.1. Capability Identifier . . . . . . . . . . . . . . . . . . . 4 2.1. Capability Identifier . . . . . . . . . . . . . . . . . . 4
2.2. :list match type for supported tests . . . . . . . . . . . . 4 2.2. :list match type for supported tests . . . . . . . . . . . 4
2.3. :list tagged argument to the "redirect" action . . . . . . . 5 2.3. :list tagged argument to the "redirect" action . . . . . . 5
2.4. Other uses for external lists . . . . . . . . . . . . . . . 6 2.4. Other uses for external lists . . . . . . . . . . . . . . 6
2.5. Syntax of an externally stored list name . . . . . . . . . . 6 2.5. Syntax of an externally stored list name . . . . . . . . . 6
2.6. Interaction with ManageSieve . . . . . . . . . . . . . . . . 6 2.6. Interaction with ManageSieve . . . . . . . . . . . . . . . 6
2.7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Security Considerations . . . . . . . . . . . . . . . . . . 8 3. Security Considerations . . . . . . . . . . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . 9
4.1. Registration of Sieve extension . . . . . . . . . . . . . . 9 4.1. Registration of Sieve extension . . . . . . . . . . . . . 9
4.2. Registration of ManageSieve capability . . . . . . . . . . . 9 4.2. Registration of ManageSieve capability . . . . . . . . . . 9
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 10
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Normative References . . . . . . . . . . . . . . . . . . . . 10 6.1. Normative References . . . . . . . . . . . . . . . . . . . 10
6.2. Informative References . . . . . . . . . . . . . . . . . . . 10 6.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
This document specifies an extension to the Sieve language [RFC5228] 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 [RFC4510], ACAP [RFC2244], 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
skipping to change at page 6, line 22 skipping to change at page 6, line 22
2.4. Other uses for external lists 2.4. Other uses for external lists
The uses for external lists specified here represent the useful cases The uses for external lists specified here represent the useful cases
and situations at the time of this writing. Other uses for external and situations at the time of this writing. Other uses for external
lists, using other Sieve features, might be devised in the future, lists, using other Sieve features, might be devised in the future,
and such uses can be described in extensions to this document. and such uses can be described in extensions to this document.
2.5. Syntax of an externally stored list name 2.5. Syntax of an externally stored list name
A name of an externally stored list is always an absolute URI A name of an externally stored list is always an absolute URI
[RFC3986]. Implementations might find URIs such as [RFC4510], [RFC3986]. Implementations might find URIs such as LDAP [RFC4510],
[I-D.ietf-vcarddav-carddav], or [RFC4151] to be useful for naming CardDAV [I-D.ietf-vcarddav-carddav], or Tag [RFC4151] to be useful
external lists. for naming external lists.
The "tag" URI scheme [RFC4151] MUST be supported, and can be used to 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 URI 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,
skipping to change at page 7, line 15 skipping to change at page 7, line 15
single-capability =/ DQUOTE "EXTLISTS" DQUOTE SP ext-list-types CRLF single-capability =/ DQUOTE "EXTLISTS" DQUOTE SP ext-list-types CRLF
; single-capability is defined in [RFC5804] ; single-capability is defined in [RFC5804]
ext-list-types = string ext-list-types = string
; space separated list of URI schema parts ; space separated list of URI schema parts
; for supported externally stored list types. ; for supported externally stored list types.
; MUST NOT be empty. ; MUST NOT be empty.
2.7. Examples 2.7. Examples
2.7.1. Example 1
This example uses the "envelope" option [RFC5228] and the This example uses the "envelope" option [RFC5228] and the
"subaddress" extension [RFC5233]: "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";
} }
2.7.2. Example 2
This example uses the "currentdate" test [RFC5260] and a list This example uses the "currentdate" test [RFC5260] and a list
containing the dates of local holidays. If today is a holiday, the containing the dates of local holidays. If today is a holiday, the
script will notify [RFC5435] the user via XMPP [RFC5437] about the script will notify [RFC5435] the user via XMPP [RFC5437] about the
message. message.
require ["extlists", "date", "enotify"]; require ["extlists", "date", "enotify"];
if currentdate :list "date" if currentdate :list "date"
"tag:example.com,2010-01-01:localHolidays" { "tag:example.com,2010-01-01:localHolidays" {
notify "xmpp:romeo@im.example.com"; notify "xmpp:romeo@im.example.com";
} }
2.7.3. Example 3
This example uses a personal address book, along with spamtest This example uses a personal address book, along with spamtest
[RFC5235] and the relational extension [RFC5231] to give a different [RFC5235] and the relational extension [RFC5231] to give a different
level of spam tolerance to known senders. level of spam tolerance to known senders.
require ["envelope", "extlists", "fileinto", "spamtest", require ["envelope", "extlists", "fileinto", "spamtest",
"relational", "comparator-i;ascii-numeric"]; "relational", "comparator-i;ascii-numeric"];
if allof ( if allof (
envelope :list "from" "tag:example.com,2010-04-10:pab", envelope :list "from" "tag:example.com,2010-04-10:pab",
spamtest :value "ge" :comparator "i;ascii-numeric" "8" spamtest :value "ge" :comparator "i;ascii-numeric" "8"
) )
skipping to change at page 8, line 22 skipping to change at page 8, line 22
fileinto "spam"; fileinto "spam";
} }
elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3" elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3"
{ /* Unknown: less tolerance in spam score */ { /* Unknown: less tolerance in spam score */
fileinto "spam"; 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 [RFC5228] also apply to this tests and "redirect" action discussed in Sieve [RFC5228] also apply
document. to this 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 [RFC4510] 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
 End of changes. 15 change blocks. 
28 lines changed or deleted 37 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/