draft-ietf-sieve-external-lists-05.txt   draft-ietf-sieve-external-lists-06.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: September 2, 2011 Huawei Technologies Expires: September 30, 2011 Huawei Technologies
March 1, 2011 March 29, 2011
Sieve Extension: Externally Stored Lists Sieve Extension: Externally Stored Lists
draft-ietf-sieve-external-lists-05 draft-ietf-sieve-external-lists-06
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
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 "ab" to represent the user's personal address book.
o Do we want to have the :list test set variables? See Ned's
comments in the text.
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 September 2, 2011. This Internet-Draft will expire on September 30, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions used in this document . . . . . . . . . . . . 4 1.1. Conventions Used In This Document . . . . . . . . . . . . 3
2. Extlists extension . . . . . . . . . . . . . . . . . . . . 4 2. Extlists Extension . . . . . . . . . . . . . . . . . . . . 3
2.1. Capability Identifier . . . . . . . . . . . . . . . . . . 4 2.1. Capability Identifier . . . . . . . . . . . . . . . . . . 3
2.2. :list match type for supported tests . . . . . . . . . . . 4 2.2. :list Match Type for Supported Tests . . . . . . . . . . . 3
2.3. :list tagged argument to the "redirect" action . . . . . . 5 2.3. :list Tagged Argument to the "redirect" Action . . . . . . 4
2.4. Other uses for external lists . . . . . . . . . . . . . . 6 2.4. Other Uses for External Lists . . . . . . . . . . . . . . 5
2.5. Syntax of an externally stored list name . . . . . . . . . 6 2.5. Syntax of an Externally Stored List Name . . . . . . . . . 5
2.6. Test valid_ext_list . . . . . . . . . . . . . . . . . . . 7 2.6. Test valid_ext_list . . . . . . . . . . . . . . . . . . . 6
2.7. Interaction with ManageSieve . . . . . . . . . . . . . . . 7 2.7. Interaction with ManageSieve . . . . . . . . . . . . . . . 6
2.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 7 2.8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . 7
2.8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 8 2.8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 8
2.8.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . . . 8 2.8.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . . . 8
3. Security Considerations . . . . . . . . . . . . . . . . . 8 3. Security Considerations . . . . . . . . . . . . . . . . . 8
4. IANA Considerations . . . . . . . . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . 9
4.1. Registration of Sieve extension . . . . . . . . . . . . . 10 4.1. Registration of Sieve Extension . . . . . . . . . . . . . 10
4.2. Registration of ManageSieve capability . . . . . . . . . . 10 4.2. Registration of ManageSieve Capability . . . . . . . . . . 10
4.3. Registration of a new URI scheme . . . . . . . . . . . . . 10 4.3. Registration of "ab" URI Scheme . . . . . . . . . . . . . 11
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 11 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Normative References . . . . . . . . . . . . . . . . . . . 11 6.1. Normative References . . . . . . . . . . . . . . . . . . . 12
6.2. Informative References . . . . . . . . . . . . . . . . . . 12 6.2. Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 14
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
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 [RFC5228] section 1.1, including Conventions for notations are as in [RFC5228] section 1.1, including
the use of [RFC5234]. 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 [RFC2119]. 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
ABNF: ABNF:
MATCH-TYPE =/ ":list" MATCH-TYPE =/ ":list"
; only valid for supported tests ; only valid for supported tests
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) in 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.
Comparators are not allowed together with the ":list" match type, so Comparators are not allowed together with the ":list" match type, so
if both are specified in a test, that MUST result in an error. if both are specified in a test, that MUST result in an error.
Queries done through list-specific mechanisms might have the effect
of built-in comparators; for example, queries to certain lists might
be case-sensitive, while queries to other lists might be done without
regard to case.
Implementations MUST support "address", "envelope" and "header" Implementations MUST support the use of :list in "address",
tests. Implementations that include the Variables extension "envelope" and "header" tests. Implementations that include the
Variables extension [RFC5229] MUST also support its use in "string"
[RFC5229] MUST also support "string" tests. 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
[RFC5463]). [RFC5463]).
For example, testing 'header ["to", "cc"]' against a list would cause For example, testing 'header ["to", "cc"]' against a list would cause
skipping to change at page 5, line 34 skipping to change at page 4, line 38
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.5 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.
[[anchor4: Ned: There's one addition I'd like to make to the list. The :list match type uses the concept of "match variables" as defined
I've proposed saying that if variables are enabled ${0} should return in Section 3.2 of the Variables extension [RFC5229]. Implementations
the thing that matched in a :list match, just like it does for that also support that extension MUST set the ${0} match variable to
:matches. ${1} and so on would return optional, list-specific the value in the list that matched the query. Other numbered match
information. In the case of pab: URLs I'd suggest defining ${1} to variables (${1}, ${2}, and so on) MAY be set with list-specific
be a sort of status for the entry returned.]] information that might be of use to the script.
[[anchor5: Alexey: Can you elaborate on what you mean by "status"
here and how would this work for other types of URIs?]]
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 the set of email addresses in the externally stored list
stored list 'ext-list-name'. This variant of the redirect command named by the ext-list-name string. This variant of the redirect
can be used to implement a personal distribution list. command can be used to implement a personal distribution list.
For this feature to work, one of the following conditions has to be For this feature to work, one of the following conditions has to be
true: true:
1. The list resolves to a list of email addresses, and the Sieve 1. The list resolves to a list of email addresses, and the Sieve
engine is able to enumerate those addresses. engine is able to enumerate those addresses.
2. The list handler is able to take care of the redirection on 2. The list handler is able to take care of the redirection on
behalf of the Sieve engine. behalf of the Sieve engine.
skipping to change at page 6, line 26 skipping to change at page 5, line 27
"*+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.5 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. 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 LDAP [RFC4510], [RFC3986]. Implementations might find URIs such as LDAP [RFC4510],
CardDAV [I-D.ietf-vcarddav-carddav], or Tag [RFC4151] to be useful CardDAV [I-D.ietf-vcarddav-carddav], or Tag [RFC4151] to be useful
for naming external lists. for naming external lists.
[[anchor7: This might have to change with the introduction of "ab:" The "tag" URI scheme [RFC4151] can be used to represent opaque, but
URIs]] user friendlier identifiers. Resolution of such identifiers is going
The "tag" URI scheme [RFC4151] MUST be supported, and can be used to to be implementation specific and it can help in hiding the
represent opaque, but user friendlier identifiers. Resolution of complexity of an implementation from end users. For example, an
such identifiers is going to be implementation specific and it can implementation can provide a web interface for managing lists of
help in hiding the complexity of an implementation from end users. users stored in LDAP. Requiring users to know generic LDAP URI
For example, an implementation can provide a web interface for syntax might not be very practical, due to its complexity. An
managing lists of users stored in LDAP. Requiring users to know implementation can instead use a fixed tag URI prefix such as "tag:
generic LDAP URI syntax might not be very practical, due to its example.com,<date>:" (where <date> can be, for example, a date
complexity. An implementation can instead use a fixed tag URI prefix generated once on installation of the web interface and left
such as "tag:example.com,<date>:" (where <date> can be, for example,
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.
The "ab" URI scheme (in particular, the URI "ab:default"), defined in
Section 4.3 MUST be supported. The mandatory-to-implement URI "ab:
default" gives access to the user's default address book (usually the
user's personal address book).
It's possible that a server will have no access to anything
resembling an address book (perhaps in an implementation where
address books are only client-side things), but the server can still
provide access to other sorts of lists -- consider the list of dates
in Example 2 (Section 2.8.2), or lists of important keywords and the
like. It might sometimes make sense to map "ab:default" into some
available list, but that might not always be reasonable. If there
really is no concept of an address book in a particular server
implementation, the server MAY support "ab:default" by having all
matches to it fail. Such an implementation SHOULD NOT be done except
as a last resort.
Queries against address books SHOULD be done without regard to case.
2.6. Test valid_ext_list 2.6. Test valid_ext_list
Usage: valid_ext_list <ext-list-names: string-list> Usage: valid_ext_list <ext-list-names: string-list>
The "valid_ext_list" test is true if all of the external list names The "valid_ext_list" test is true if all of the external list names
in the ext-list-names argument are supported, and they are valid both in the ext-list-names argument are supported, and they are valid both
syntactically (including URI parameters) and semantically (including syntactically (including URI parameters) and semantically (including
implementation-specific semantic restrictions). Otherwise the test implementation-specific semantic restrictions). Otherwise the test
returns false. returns false.
skipping to change at page 7, line 43 skipping to change at page 7, line 17
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.8. Examples 2.8. Examples
2.8.1. Example 1 2.8.1. Example 1
This example uses the "envelope" option [RFC5228] and the This example uses a personal address book, along with the Spamtest
"subaddress" extension [RFC5233]: [RFC5235] and Relational [RFC5231] extensions to give a different
level of spam tolerance to known senders.
require ["extlists", "envelope", "subaddress"]; require ["envelope", "extlists", "fileinto", "spamtest",
"relational", "comparator-i;ascii-numeric"];
if envelope :list "from" "ab:default"
{ /* Known: allow high spam score */
if spamtest :value "ge" :comparator "i;ascii-numeric" "8"
{
fileinto "spam";
}
}
elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3"
{ /* Unknown: less tolerance in spam score */
fileinto "spam";
}
# Submission from list members is sent to all members The same example can also be written another way, if the Variables
if allof (envelope :detail :list "to" extension [RFC5229] is also supported:
"tag:example.com,2009-05-28:mylist",
header :list "from" require ["envelope", "extlists", "fileinto", "spamtest",
"tag:example.com,2009-05-28:mylist") { "variables", "relational", "comparator-i;ascii-numeric"];
redirect :list "tag:example.com,2009-05-28:mylist"; if envelope :list "from" "ab:default" {
set "limit" "8"; /* Known: allow high spam score */
} else {
set "limit" "3"; /* Unknown: less tolerance in spam score */
}
if spamtest :value "ge" :comparator "i;ascii-numeric" ${limit} {
fileinto "spam";
} }
2.8.2. Example 2 2.8.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,2011-01-01:localHolidays" {
notify "xmpp:romeo@im.example.com"; notify "xmpp:romeo@im.example.com";
} }
2.8.3. Example 3 2.8.3. Example 3
This example uses a personal address book, along with spamtest This example also uses the "envelope" option [RFC5228] and the
[RFC5235] and the relational extension [RFC5231] to give a different Subaddress extension [RFC5233]. If mail is sent with the list name
level of spam tolerance to known senders. as a subaddress of the recipient (to, say, "alexey+mylist"), and the
message comes from a member of the list, it will be redirected to all
members of the list. Variants of this technique might be useful for
creating private mailing lists.
require ["envelope", "extlists", "fileinto", "spamtest", require ["extlists", "envelope", "subaddress"];
"relational", "comparator-i;ascii-numeric"];
if allof ( # Submission from list members is sent to all members
envelope :list "from" "tag:example.com,2010-04-10:pab", if allof (envelope :detail "to" "mylist",
spamtest :value "ge" :comparator "i;ascii-numeric" "8" header :list "from"
) "tag:example.com,2010-05-28:mylist") {
{ /* Known: allow high spam score */ redirect :list "tag:example.com,2010-05-28:mylist";
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 [RFC5228] also apply tests and "redirect" action discussed in Sieve [RFC5228] also apply
to this 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
skipping to change at page 10, line 5 skipping to change at page 9, line 41
be used to minimize network traffic and load on the directory be used to minimize network traffic and load on the directory
service. For example, LDAP allows for search filters. service. For example, LDAP allows for search filters.
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 Note in particular that it can be too easy for a script to use
redirect :list "ab:default";
to send messages to "everyone in your address book", and one can
easily imagine both intentional and accidental abuse. The situation
can be even worse for, say, "ab:corporate". Warnings, as well as
enforced limits, are appropriate here.
4.1. Registration of Sieve extension 4. IANA Considerations
4.1. Registration of Sieve Extension
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. This information should be
added to the list of sieve extensions given on
http://www.iana.org/assignments/sieve-extensions.
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve extension
Capability name: extlists
Description: adds the ':list' match type to certain Sieve tests, and
the ':list' argument to the 'redirect' action. The ':list' match
type changes tests to match values against values stored in one or
more externally stored lists. The ':list' argument to the redirect
action changes the redirect action to forward the message to email
addresses stored in the externally stored list.
RFC number: this RFC
Contact address:
The Sieve discussion list <sieve@ietf.org>
This information should be added to the list of sieve extensions Subject: Registration of new Sieve extension
given on http://www.iana.org/assignments/sieve-extensions.
4.2. Registration of ManageSieve capability Capability name: extlists
Description: Adds the ":list" match type to certain Sieve tests, and
the ":list" argument to the "redirect" action. The ":list" match
type changes tests to match values against values stored in one
or more externally stored lists. The ":list" argument to the
redirect action changes the redirect action to forward the
message to email addresses stored in the externally stored list.
RFC number: this RFC
Contact address: Sieve mailing list <sieve@ietf.org>
4.2. Registration of ManageSieve Capability
The following requests IANA to register a new ManageSieve Capability The following requests IANA to register a new ManageSieve Capability
according to the IANA registration template specified in [RFC5804]: according to the IANA registration template specified in [RFC5804]:
To: iana@iana.org 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.7
Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG
4.3. Registration of a new URI scheme 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.7
Person & email address to contact for further information: Sieve
mailing list <sieve@ietf.org>
Author/Change controller: IESG
4.3. Registration of "ab" URI Scheme
The following requests IANA to register a new URI scheme according to The following requests IANA to register a new URI scheme according to
the IANA registration template specified in [RFC4395]: the IANA registration template specified in [RFC4395]:
URI scheme name: ab URI scheme name: ab
Status: Permanent
Status: Permanent
URI scheme syntax: URI scheme syntax:
paburi = "ab:" addrbook [ "?" extensions ] paburi = "ab:" addrbook [ "?" extensions ]
addrbook = segment addrbook = segment
; <segment> defined in [RFC3986] ; <segment> defined in [RFC3986]
extensions = query extensions = query
; <query> defined in [RFC3986] ; <query> defined in [RFC3986]
URI scheme semantics: "ab" URIs are used for designating references
to personal address books. A personal address book is an internal URI scheme semantics: "ab" URIs are used for designating references
concept used by different applications (such as Sieve interpreters) to address books. An address book is an internal concept used by
for describing a list of named entries, and maybe translated into different applications (such as Sieve interpreters) for
other types of address books, such as LDAP Groups. describing a list of named entries, and may be translated into
Encoding considerations: Percent-encoding is allowed in "segment" and other types of address books, such as LDAP Groups. Address books
"query" components. Internationalization is handled by IRI may be private or shared; they may be personal, organizational,
processing. or perhaps even "crowdsourced".
Intended usage: An "ab" URI is designed to be used internally by
applications for referencing address books. Encoding considerations: Percent-encoding is allowed in "segment"
and "query" components. Internationalization is handled by IRI
processing.
Intended usage: An "ab" URI is designed to be used internally by
applications for referencing address books. Each URI is intended
to represent a grouping of addresses that can be logically
thought of as one "book". Any given address can belong to more
than one book -- that is, can be referred to by more than one
URI.
The URI "ab:default" is a reserved name that MUST be implemented,
representing a default grouping (book) of addresses. Other
names, representing the same or other groupings MAY be
implemented. For example, an implementation might have the
following URIs:
* ab:personal -- a book representing the user's personal
address book.
* ab:friends -- a subset of ab:personal, defined by the user.
* ab:family -- a subset of ab:personal, defined by the user.
* ab:company -- a book representing user's company's address
book.
* ab:department -- a subset of ab:company, defined by the
company.
* ab:co-workers -- a subset of ab:company, defined by the user.
* ab:default -- the default address book, a reference to ab:
personal.
Applications and/or protocols that use this URI scheme name: Applications and/or protocols that use this URI scheme name:
Currently only Sieve External List extension is using this URI Currently only the Sieve External List extension is using this
scheme. Email clients that use URIs internally might find this URI URI scheme. Email clients that use URIs internally might find
scheme to be useful as well. this URI scheme to be useful as well.
Interoperability considerations: Applications are only REQUIRED to
support "ab:default". Interoperability considerations: Applications are only REQUIRED to
Security considerations: Applications SHOULD ensure appropriate support "ab:default".
restrictions are in place to protect sensitive information that might
be revealed by "ab" URIs from access or modification by untrusted Security considerations: Applications SHOULD ensure appropriate
sources. restrictions are in place to protect sensitive information that
Relevant publications: this RFC might be revealed by "ab" URIs from access or modification by
Contact: Sieve IETF WG <sieve@ietf.org> untrusted sources.
Author/Change controller: IETF/IESG
Relevant publications: this RFC
Contact: Sieve mailing list <sieve@ietf.org>
Author/Change controller: IETF/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. Kristin Hubner also Donkin for ideas, comments and suggestions. Kristin Hubner also
helped greatly with the examples. helped greatly with the examples.
6. References 6. References
 End of changes. 40 change blocks. 
149 lines changed or deleted 230 lines changed or added

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