Internet Engineering Task Force (IETF) A. Melnikov
Request for Comments: 6134 Isode Limited
Category: Standards Track B. Leiba
ISSN: 2070-1721 Huawei Technologies
July 2011
Internet Engineering Task Force (IETF) A. Melnikov
Request for Comments: 6134 Isode Limited
Category: Standards Track B. Leiba
ISSN: 2070-1721 Huawei Technologies
July 2011
Sieve Extension: Externally Stored Lists
筛选扩展：外部存储的列表
Abstract
摘要
The Sieve email filtering language can be used to implement email whitelisting, blacklisting, personal distribution lists, and other sorts of list matching. Currently, this requires that all members of such lists be hard-coded 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 mail server.
Sieve电子邮件过滤语言可用于实现电子邮件白名单、黑名单、个人通讯组列表和其他类型的列表匹配。目前，这需要在脚本本身中硬编码此类列表的所有成员。每当添加或删除列表的成员时，都需要更新脚本，并可能将其上载到邮件服务器。
This document defines a Sieve extension for accessing externally stored lists -- lists whose members are stored externally to the script, such as using the Lightweight Directory Access Protocol (LDAP), the Application Configuration Access Protocol (ACAP), vCard Extensions to WebDAV (CardDAV), or relational databases.
本文档定义了一个用于访问外部存储列表的筛选扩展——列表的成员存储在脚本外部，例如使用轻量级目录访问协议（LDAP）、应用程序配置访问协议（ACAP）、WebDAV vCard扩展（CardDAV）或关系数据库。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6134.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6134.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您在以下方面的权利和限制：
to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
请参阅本文件。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Extlists Extension . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Capability Identifier . . . . . . . . . . . . . . . . . . 3
2.2. :list Match Type for Supported Tests . . . . . . . . . . . 3
2.3. :list Tagged Argument to the "redirect" Action . . . . . . 5
2.4. Other Uses for External Lists . . . . . . . . . . . . . . 5
2.5. Syntax of an Externally Stored List Name . . . . . . . . . 5
2.6. Definition of "addrbook" URN Parameter . . . . . . . . . . 7
2.7. Test valid_ext_list . . . . . . . . . . . . . . . . . . . 9
2.8. Interaction with ManageSieve . . . . . . . . . . . . . . . 9
2.9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 10
2.9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 10
2.9.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . 11
2.9.4. Example 4 . . . . . . . . . . . . . . . . . . . . . . 11
2.9.5. Example 5 . . . . . . . . . . . . . . . . . . . . . . 11
3. Security Considerations . . . . . . . . . . . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
4.1. Registration of Sieve Extension . . . . . . . . . . . . . 14
4.2. Registration of ManageSieve Capability . . . . . . . . . . 14
4.3. Creation of Sieve URN Parameters Registry . . . . . . . . 15
4.4. Registration of the "addrbook" URN parameter . . . . . . . 16
4.5. Registration of "sieve" URN sub-namespace . . . . . . . . 16
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1. Normative References . . . . . . . . . . . . . . . . . . . 16
6.2. Informative References . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Extlists Extension . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Capability Identifier . . . . . . . . . . . . . . . . . . 3
2.2. :list Match Type for Supported Tests . . . . . . . . . . . 3
2.3. :list Tagged Argument to the "redirect" Action . . . . . . 5
2.4. Other Uses for External Lists . . . . . . . . . . . . . . 5
2.5. Syntax of an Externally Stored List Name . . . . . . . . . 5
2.6. Definition of "addrbook" URN Parameter . . . . . . . . . . 7
2.7. Test valid_ext_list . . . . . . . . . . . . . . . . . . . 9
2.8. Interaction with ManageSieve . . . . . . . . . . . . . . . 9
2.9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 10
2.9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 10
2.9.3. Example 3 . . . . . . . . . . . . . . . . . . . . . . 11
2.9.4. Example 4 . . . . . . . . . . . . . . . . . . . . . . 11
2.9.5. Example 5 . . . . . . . . . . . . . . . . . . . . . . 11
3. Security Considerations . . . . . . . . . . . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
4.1. Registration of Sieve Extension . . . . . . . . . . . . . 14
4.2. Registration of ManageSieve Capability . . . . . . . . . . 14
4.3. Creation of Sieve URN Parameters Registry . . . . . . . . 15
4.4. Registration of the "addrbook" URN parameter . . . . . . . 16
4.5. Registration of "sieve" URN sub-namespace . . . . . . . . 16
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1. Normative References . . . . . . . . . . . . . . . . . . . 16
6.2. Informative References . . . . . . . . . . . . . . . . . . 17
This document specifies an extension to the Sieve language [RFC5228] for checking membership in an external list or for redirecting messages to an external list of recipients. An "external list" is a list whose members are stored externally to the Sieve script, such as using LDAP [RFC4510], ACAP [RFC2244], CardDAV [CardDAV], or relational databases.
本文档指定了筛语言[RFC5228]的扩展，用于检查外部列表中的成员资格或将邮件重定向到外部收件人列表。“外部列表”是其成员存储在筛脚本外部的列表，例如使用LDAP[RFC4510]、ACAP[RFC2244]、CardDAV[CardDAV]或关系数据库。
This extension adds a new match type to apply to supported tests and a new tagged argument to the "redirect" action.
此扩展将添加一个新的匹配类型以应用于支持的测试，并将一个新的标记参数添加到“重定向”操作。
Conventions for notations are as in [RFC5228], Section 1.1, including the use of ABNF [RFC5234].
符号惯例如[RFC5228]第1.1节所述，包括ABNF[RFC5234]的使用。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The capability string associated with the extension defined in this document is "extlists".
与本文档中定义的扩展相关联的功能字符串是“extlists”。
ABNF:
荷兰银行：
MATCH-TYPE =/ ":list"
; only valid for supported tests
MATCH-TYPE =/ ":list"
; only valid for supported tests
The new ":list" match type changes the interpretation of the "key-list" parameter (the second parameter) in supported tests. When the match type is ":list", the key-list becomes a list of names of externally stored lists. The external lists are queried, perhaps 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 the lists.
新的“：list”匹配类型更改了受支持测试中“key list”参数（第二个参数）的解释。当匹配类型为“：list”时，键列表成为外部存储列表的名称列表。外部列表可能通过特定于列表的机制进行查询，如果指定的任何值与一个或多个列表的任何成员匹配，则测试将计算为“true”。
Comparators are not allowed together with the ":list" match type, so if both are specified in a test, that MUST result in an error. Queries done through list-specific mechanisms might have the effect
比较器不允许与“：list”匹配类型一起使用，所以如果在测试中同时指定了这两种类型，则必须导致错误。通过特定于列表的机制执行的查询可能会产生这种效果
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 the use of ":list" in "address", "envelope", and "header" tests. Implementations that include the Variables extension [RFC5229] MUST also support its use in "string" tests.
实现必须支持在“地址”、“信封”和“标题”测试中使用“：list”。包含变量扩展[RFC5229]的实现还必须支持在“字符串”测试中使用它。
Implementations MAY support other tests than the ones in this document. Implementations MUST report an error when a script uses ":list" with a test that does not support ":list". This error SHOULD be reported at compile-time but MAY be reported at run-time. To maintain interoperability, other tests that can be used with ":list" SHOULD be documented in a specification that defines a capability string that can be tested (in a "require" statement or using "ihave" [RFC5463]).
实现可能支持除本文档中的测试之外的其他测试。当脚本在不支持“：list”的测试中使用“：list”时，实现必须报告错误。此错误应该在编译时报告，但可以在运行时报告。为保持互操作性，可与“：list”一起使用的其他测试应记录在定义可测试的功能字符串的规范中（在“require”语句中或使用“ihave”[RFC5463]）。
For example, testing 'header ["to", "cc"]' against a list would cause each "to" and "cc" value, ignoring leading and trailing whitespace, to be queried. If any value is found to belong to the list, the test returns "true". If no value belongs to the list, the test returns "false". Once a value is found in the list, there is no need for the query mechanism to look further.
例如，针对列表测试“header[“to”，“cc”]”将导致查询每个“to”和“cc”值，忽略前导和尾随空格。如果发现任何值属于该列表，测试将返回“true”。如果列表中没有值，测试将返回“false”。一旦在列表中找到一个值，查询机制就无需进一步查找。
For some lists, the Sieve engine might directly retrieve the list and 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 retrieval of the list itself. It is up to the Sieve implementation to understand how to interact with any supported list. If the Sieve engine is permanently unable to query the list (perhaps because the list doesn't support the required operation), the test MUST result in a runtime error in the Sieve script.
对于某些列表，筛选引擎可能直接检索列表并进行自己的比较。其他列表可能不是这样工作的——它们可能提供一种询问列表中是否有值的方法，但不允许检索列表本身。如何与任何受支持的列表交互取决于Sieve实现。如果Sieve引擎永久无法查询列表（可能是因为列表不支持所需的操作），则测试必须在Sieve脚本中导致运行时错误。
See Section 2.5 for the detailed description of syntax used for naming externally stored lists.
有关用于命名外部存储列表的语法的详细说明，请参见第2.5节。
The ":list" match type uses the concept of "match variables" as defined in Section 3.2 of the Variables extension [RFC5229]. Implementations that also support that extension MUST set the ${0} match variable to the value in the list that matched the query. Other numbered match variables (${1}, ${2}, and so on) MAY be set with list-specific information that might be of use to the script.
“：list”匹配类型使用变量扩展[RFC5229]第3.2节中定义的“匹配变量”概念。也支持该扩展的实现必须将${0}match变量设置为与查询匹配的列表中的值。其他编号的匹配变量（${1}、${2}等）可以使用脚本可能使用的列表特定信息进行设置。
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 message to the set of email addresses in the externally stored list named by the ext-list-name string. This variant of the redirect command can be used to implement a personal distribution list.
带有“：list”参数的“redirect”操作用于将消息发送到外部存储列表中由ext list name字符串命名的一组电子邮件地址。重定向命令的这种变体可用于实现个人通讯组列表。
For this feature to work, one of the following conditions has to be true:
要使此功能正常工作，必须满足以下条件之一：
1. The list resolves to a list of email addresses, and the Sieve engine is able to enumerate those addresses.
1. 列表解析为电子邮件地址列表，筛选引擎能够枚举这些地址。
2. The list handler is able to take care of the redirection on behalf of the Sieve engine.
2. 列表处理程序能够代表筛选引擎处理重定向。
In cases where, for example, a list contains hashed email address values or an email address pattern ("sz*@example.com", "*+ietf@example.net"), the Sieve engine will not be able to redirect to that list, and responsibility must pass to the list handler.
例如，如果列表包含哈希电子邮件地址值或电子邮件地址模式（“sz*@example.com，”*+ietf@example.net），筛选引擎将无法重定向到该列表，并且责任必须转移到列表处理程序。
If neither the Sieve engine nor the list handler can enumerate (or iterate) the list, or the list does not resolve to email addresses, the situation MUST result in a runtime error in the Sieve script.
如果Sieve引擎和列表处理程序都无法枚举（或迭代）列表，或者列表未解析为电子邮件地址，则这种情况必须导致Sieve脚本中出现运行时错误。
See Section 2.5 for the detailed description of syntax used for naming externally stored lists.
有关用于命名外部存储列表的语法的详细说明，请参见第2.5节。
The uses for external lists specified here represent known cases and situations at the time of this writing. Other uses for external lists, employing other Sieve features, might be devised in the future, and such uses can be described in extensions to this document.
此处指定的外部列表的用途表示撰写本文时已知的情况。将来可能会设计使用其他筛选功能的外部列表的其他用途，这些用途可以在本文档的扩展部分中描述。
A name of an externally stored list is always an absolute URI [RFC3986]. Implementations might find URIs such as LDAP [RFC4510], CardDAV [CardDAV], or "tag" [RFC4151] to be useful for naming external lists.
外部存储列表的名称始终是绝对URI[RFC3986]。实现可能会发现LDAP[RFC4510]、CardDAV[CardDAV]或“tag”[RFC4151]等URI对于命名外部列表非常有用。
The "tag" URI scheme [RFC4151] can be used to represent opaque, but more user-friendly identifiers. Resolution of such identifiers is going to be implementation specific and it can help in hiding the
“标记”URI方案[RFC4151]可用于表示不透明但更用户友好的标识符。此类标识符的解析将是特定于实现的，它可以帮助隐藏
complexity of an implementation from end users. For example, an implementation can provide a web interface for managing lists of users stored in LDAP. Requiring users to know generic LDAP URI syntax might not be very practical, due to its complexity. An implementation can instead use a fixed tag URI prefix 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 to end users.
来自最终用户的实现的复杂性。例如，一个实现可以提供一个web界面来管理LDAP中存储的用户列表。由于其复杂性，要求用户了解通用LDAP URI语法可能不太实际。一个实现可以改为使用固定的标记URI前缀，例如“tag:example.com，<date>：”（其中<date>可以是一个在安装web界面时生成的日期，在升级时保持不变），并且该前缀甚至不需要向最终用户显示。
The "addrbook" URNs defined in Section 2.6 (in particular, the reserved URI "urn:ietf:params:sieve:addrbook:default") MUST be supported. To make it easier to use registered Sieve URN parameters, we define a shorthand way to specify them in a Sieve script: a list name that begins with ":" is taken as referencing a Sieve URN parameter, with the initial ":" expanding to "urn:ietf:params:sieve:". So we have the following equivalences:
必须支持第2.6节中定义的“addrbook”urn（特别是保留URI“urn:ietf:params:sieve:addrbook:default”）。为了更方便地使用已注册的Sieve-URN参数，我们定义了一种在Sieve脚本中指定这些参数的简写方法：以“：”开头的列表名被视为引用Sieve-URN参数，首字母“：”扩展为“URN:ietf:params:Sieve:”。因此，我们有以下等价物：
:addrbook:default == urn:ietf:params:sieve:addrbook:default
:addrbook:default == urn:ietf:params:sieve:addrbook:default
:addrbook:personal == urn:ietf:params:sieve:addrbook:personal
:addrbook:personal == urn:ietf:params:sieve:addrbook:personal
and so on.
等等
The mandatory-to-implement URI
实现URI所必需的
urn:ietf:params:sieve:addrbook:default
urn:ietf:params:sieve:addrbook:default
gives access to the user's default address book (usually the user's personal address book). Note that these are URIs, subject to normal URI encoding rules, including percent-encoding. The reserved name "default" MUST be considered case-insensitive after decoding. That means that the following URIs are all equivalent:
允许访问用户的默认通讯簿（通常是用户的个人通讯簿）。请注意，这些是URI，受正常URI编码规则的约束，包括百分比编码。解码后，保留名称“default”必须视为不区分大小写。这意味着以下URI都是等效的：
:addrbook:default
：addrbook:默认值
:ADDRBOOK:DEFAULT
：ADDRBOOK:默认值
:aDdRbOOk:DeFauLt
：aDdRbOOk:默认值
:AddrBook:%44%65%66ault
：地址簿：%44%65%66错误
Address book names other than "default" MAY be case-sensitive, depending upon the implementation, so their case (after URI decoding) MUST be maintained.
除“default”之外的通讯簿名称可能区分大小写，具体取决于实现，因此必须保留其大小写（URI解码后）。
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.9.2), or lists of important keywords and the like. It might sometimes make sense to map ":addrbook: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 ":addrbook:default" by having all matches to it fail. Such an implementation SHOULD NOT be done except as a last resort.
服务器可能无法访问任何类似于地址簿的东西（也许在一个地址簿只是客户端事物的实现中），但是服务器仍然可以提供对其他种类的列表的访问——考虑示例2中的日期列表（第2.9节），或重要关键字列表等。有时将“：addrbook:default”映射到某个可用列表中可能有意义，但这可能并不总是合理的。如果在特定的服务器实现中确实没有地址簿的概念，那么服务器可能会通过所有匹配失败来支持“：addrbook:default”。除非作为最后手段，否则不应执行这种执行。
Queries against address books SHOULD be done without regard to case.
对地址簿的查询应不考虑具体情况。
This section gives the details of the "addrbook" Sieve URN parameter that's registered in Section 4.4. URIs that use this parameter begin with "urn:ietf:params:sieve:addrbook:".
本节给出了在第4.4节中注册的“addrbook”参数的详细信息。使用此参数的URI以“urn:ietf:params:sieve:addrbook:”开头。
URN parameter name: addrbook
URN参数名称：addrbook
URN parameter syntax: The "addrbook" parameter is defined by the <addrbook-urn> rule, defined using ABNF [RFC5234]:
URN参数语法：“addrbook”参数由使用ABNF[RFC5234]定义的<addrbook URN>规则定义：
addrbook-urn = "addrbook:" addrbook [ "?" extensions ]
addrbook = segment
; <segment> defined in [RFC3986]
extensions = query
; <query> defined in [RFC3986]
addrbook-urn = "addrbook:" addrbook [ "?" extensions ]
addrbook = segment
; <segment> defined in [RFC3986]
extensions = query
; <query> defined in [RFC3986]
Intended usage: "addrbook" URNs are used for designating references to address books. An address book is a concept used by different applications (such as Sieve interpreters) for describing a list of named entries, and may be translated into other types of address books, such as LDAP groups. Address books may be private or shared; they may be personal, organizational, or perhaps even "crowdsourced".
预期用途：“addrbook”骨灰盒用于指定对通讯簿的引用。通讯簿是不同应用程序（如筛解释器）用于描述命名条目列表的概念，可以翻译为其他类型的通讯簿，如LDAP组。通讯簿可以是私人的，也可以是共享的；它们可能是个人的、组织的，甚至可能是“众包的”。
The address book name (the "addrbook" element in the ABNF above) refers to a specifically named address book, as defined by the implementation. A user might, for example, have access to a number of different address books, such as a personal one, a family one, a company one, and one for the town where the user lives.
地址簿名称（上面ABNF中的“addrbook”元素）指的是实现定义的特定名称的地址簿。例如，用户可以访问许多不同的地址簿，例如个人地址簿、家庭地址簿、公司地址簿和用户所在城镇的地址簿。
The extension information (the "extensions" element in the ABNF above) is available for use in future extensions. It might allow for things such as dynamic subsets of an address book -- for example, something such as this might be defined in the future:
扩展信息（上面ABNF中的“扩展”元素）可用于将来的扩展。它可能允许诸如地址簿的动态子集之类的内容，例如，将来可能会定义这样的内容：
urn:ietf:params:sieve:addrbook:personal?name.contains=fred
urn:ietf:params:sieve:addrbook:personal?name.contains=fred
There are no extensions defined at this time.
目前没有定义任何扩展。
An "addrbook" URN is designed to be used by applications for referencing address books. Each URN 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 URN.
“addrbook”URN设计用于应用程序引用地址簿。每个URN用于表示一组地址，这些地址在逻辑上可以被认为是一本“书”。任何给定的地址都可以属于多本书——也就是说，可以被多个URN引用。
The URI "urn:ietf:params:sieve:addrbook" has no meaning in itself. It MUST be used with sub-parameters representing the address book name and extension information, as shown in the ABNF above.
URI“urn:ietf:params:sieve:addrbook”本身没有任何意义。它必须与表示通讯簿名称和扩展名信息的子参数一起使用，如上面的ABNF所示。
The sub-parameter "default" (creating the URN "urn:ietf:params:sieve:addrbook:default") is a reserved (case-insensitive) 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 use the following sub-parameters:
子参数“default”（创建URN“URN:ietf:params:sieve:addrbook:default”）是必须实现的保留（不区分大小写）名称，表示地址的默认分组（book）。可以实现表示相同或其他分组的其他名称。例如，实现可能使用以下子参数：
* personal -- a book representing the user's personal address book.
* 个人——代表用户个人地址簿的一本书。
* friends -- a subset of urn:ietf:params:sieve:addrbook:personal, defined by the user.
* 朋友——urn:ietf:params:sieve:addrbook:personal的子集，由用户定义。
* family -- a subset of urn:ietf:params:sieve:addrbook:personal, defined by the user.
* family——urn:ietf:params:sieve:addrbook:personal的子集，由用户定义。
* company -- a book representing the user's company's address book.
* 公司——代表用户公司地址簿的一本书。
* department -- a subset of urn:ietf:params:sieve:addrbook:company, defined by the company.
* department——urn:ietf:params:sieve:addrbook:company的子集，由公司定义。
* co-workers -- a subset of urn:ietf:params:sieve:addrbook:company, defined by the user.
* co-workers——用户定义的urn:ietf:params:sieve:addrbook:company的子集。
* default -- the default address book, a reference to urn:ietf:params:sieve:addrbook:personal.
* default——默认地址簿，是对urn:ietf:params:sieve:addrbook:personal的引用。
Interoperability considerations: Applications are only REQUIRED to support "addrbook:default", where all cases and encodings of "default" are considered equivalent. Address book names other than "default" MAY be case-sensitive, depending upon the
互操作性注意事项：应用程序只需要支持“addrbook:default”，其中“default”的所有情况和编码都被认为是等效的。“默认”以外的通讯簿名称可能区分大小写，具体取决于
implementation, so their case (after URI decoding) MUST be maintained.
实现，因此它们的大小写（URI解码后）必须保持不变。
Security considerations: Applications SHOULD ensure appropriate restrictions are in place to protect sensitive information that might be revealed by "addrbook" URNs from access or modification by untrusted sources.
安全注意事项：应用程序应确保有适当的限制，以保护“addrbook”URN可能泄露的敏感信息不受不可信来源的访问或修改。
Contact: Sieve mailing list <sieve@ietf.org>
Contact: Sieve mailing list <sieve@ietf.org>
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 in the ext-list-names argument are supported, and they are valid both syntactically (including URI parameters) and semantically (including implementation-specific semantic restrictions). Otherwise, the test returns false.
如果ext list names参数中的所有外部列表名都受支持，并且它们在语法（包括URI参数）和语义（包括特定于实现的语义限制）上都有效，则“valid_ext_list”测试为真。否则，测试返回false。
This test MUST perform exactly the same validation of an external list name as would be performed by the "header :list" test.
此测试必须执行与“header:list”测试完全相同的外部列表名称验证。
This extension defines the following new capability for ManageSieve (see [RFC5804], Section 1.7):
此扩展为ManageSeeve定义了以下新功能（请参见[RFC5804]，第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 corresponding Sieve implementation supports the "extlists" extension defined in this document.
EXTLISTS—受支持的外部存储列表类型的URI架构部分[RFC3986]的空格分隔列表。如果相应的Sieve实现支持本文档中定义的“extlists”扩展，则必须返回此功能。
This also extends the ManageSieve ABNF as follows:
这还扩展了ManageSeeve ABNF，如下所示：
single-capability =/ DQUOTE "EXTLISTS" DQUOTE SP ext-list-types CRLF ; single-capability is defined in [RFC5804]
单功能=/DQUOTE“extlist”DQUOTE SP ext list type CRLF；[RFC5804]中定义了单一功能
ext-list-types = string
; space separated list of URI schema parts
; for supported externally stored list types.
; MUST NOT be empty.
ext-list-types = string
; space separated list of URI schema parts
; for supported externally stored list types.
; MUST NOT be empty.
This example uses a personal address book, along with the Spamtest [RFC5235] and Relational [RFC5231] extensions to give a different level of spam tolerance to known senders.
此示例使用个人通讯簿以及Spamtest[RFC5235]和关系[RFC5231]扩展为已知发件人提供不同级别的垃圾邮件容忍度。
require ["envelope", "extlists", "fileinto", "spamtest",
"relational", "comparator-i;ascii-numeric"];
if envelope :list "from" ":addrbook: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";
}
require ["envelope", "extlists", "fileinto", "spamtest",
"relational", "comparator-i;ascii-numeric"];
if envelope :list "from" ":addrbook: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";
}
The same example can also be written another way, if the Variables extension [RFC5229] is also supported:
如果还支持变量扩展[RFC5229]，也可以用另一种方式编写相同的示例：
require ["envelope", "extlists", "fileinto", "spamtest",
"variables", "relational", "comparator-i;ascii-numeric"];
if envelope :list "from" ":addrbook:default" {
set "lim" "8"; /* Known: allow high spam score */
} else {
set "lim" "3"; /* Unknown: less tolerance in spam score */
}
if spamtest :value "ge" :comparator "i;ascii-numeric" "${lim}" {
fileinto "spam";
}
require ["envelope", "extlists", "fileinto", "spamtest",
"variables", "relational", "comparator-i;ascii-numeric"];
if envelope :list "from" ":addrbook:default" {
set "lim" "8"; /* Known: allow high spam score */
} else {
set "lim" "3"; /* Unknown: less tolerance in spam score */
}
if spamtest :value "ge" :comparator "i;ascii-numeric" "${lim}" {
fileinto "spam";
}
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 (as described in [RFC5435]) the user via the Extensible Messaging and Presence Protocol (XMPP) [RFC5437] about the message.
此示例使用“currentdate”测试[RFC5260]和包含本地假日日期的列表。如果今天是假日，脚本将通过可扩展消息和状态协议（XMPP）[RFC5437]通知用户（如[RFC5435]中所述）。
require ["extlists", "date", "enotify"];
if currentdate :list "date"
"tag:example.com,2011-01-01:localHolidays" {
notify "xmpp:romeo@im.example.com";
}
require ["extlists", "date", "enotify"];
if currentdate :list "date"
"tag:example.com,2011-01-01:localHolidays" {
notify "xmpp:romeo@im.example.com";
}
This example also uses the "envelope" option [RFC5228] and the Subaddress extension [RFC5233]. If mail is sent with the list name 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.
此示例还使用“信封”选项[RFC5228]和子地址扩展[RFC5233]。如果邮件以列表名作为收件人的子地址发送（例如，“alexey+mylist”），并且邮件来自列表中的一个成员，则邮件将重定向到列表中的所有成员。这种技术的变体可能有助于创建私人邮件列表。
require ["extlists", "envelope", "subaddress"];
需要[“外部列表”、“信封”、“子地址”]；
# Submission from list members is sent to all members
if allof (envelope :detail "to" "mylist",
header :list "from"
"tag:example.com,2010-05-28:mylist") {
redirect :list "tag:example.com,2010-05-28:mylist";
}
# Submission from list members is sent to all members
if allof (envelope :detail "to" "mylist",
header :list "from"
"tag:example.com,2010-05-28:mylist") {
redirect :list "tag:example.com,2010-05-28:mylist";
}
This example uses variable matching [RFC5229] to extract the IP address from the last "Received" header field. It then checks that against a "block list" of undesirable IP addresses, and rejects the message if there's a match.
本例使用变量匹配[RFC5229]从最后一个“接收到的”报头字段中提取IP地址。然后，它根据不需要的IP地址的“阻止列表”检查该消息，如果存在匹配，则拒绝该消息。
require ["variables", "extlists", "index", "reject"];
if header :index 1 :matches "received" "*(* [*.*.*.*])*" {
set "ip" "${3}.${4}.${5}.${6}";
if string :list "${ip}"
"tag:example.com,2011-04-10:DisallowedIPs" {
reject "Message not allowed from this IP address";
}
}
require ["variables", "extlists", "index", "reject"];
if header :index 1 :matches "received" "*(* [*.*.*.*])*" {
set "ip" "${3}.${4}.${5}.${6}";
if string :list "${ip}"
"tag:example.com,2011-04-10:DisallowedIPs" {
reject "Message not allowed from this IP address";
}
}
This example uses several features of the MIME parts extension [RFC5703] to scan for unsafe attachment types. To make it easily extensible, the unsafe types are kept in an external list, which would be shared among all users and all scripts, avoiding the need to change scripts when the list changes.
本例使用MIME部件扩展[RFC5703]的几个功能来扫描不安全的附件类型。为了便于扩展，不安全类型保存在一个外部列表中，所有用户和所有脚本都将共享该列表，从而避免在列表更改时更改脚本。
[Note that this is an illustrative example, and more rigorous malware filtering is advisable. It is insufficient to base email security on checks of filenames alone.]
[请注意，这是一个说明性示例，建议进行更严格的恶意软件过滤。仅基于文件名检查是不够的。]
require [ "extlists", "foreverypart", "mime", "enclose" ];
要求[“extlist”、“foreverypart”、“mime”、“include”]；
foreverypart
{
if header :mime :param "filename"
:list ["Content-Type", "Content-Disposition"]
"tag:example.com,2011-04-10:BadFileNameExts"
{
# these attachment types are executable
enclose :subject "Warning" :text
WARNING! The enclosed message has attachments that might be unsafe.
These attachment types may contain a computer virus program
that can infect your computer and potentially damage your data.
foreverypart
{
if header :mime :param "filename"
:list ["Content-Type", "Content-Disposition"]
"tag:example.com,2011-04-10:BadFileNameExts"
{
# these attachment types are executable
enclose :subject "Warning" :text
WARNING! The enclosed message has attachments that might be unsafe.
These attachment types may contain a computer virus program
that can infect your computer and potentially damage your data.
Before clicking on these message attachments, you should verify
with the sender that this message was sent intentionally, and
that the attachments are safe to open.
.
;
break;
}
}
Before clicking on these message attachments, you should verify
with the sender that this message was sent intentionally, and
that the attachments are safe to open.
.
;
break;
}
}
Security considerations related to the "address"/"envelope"/"header" tests and "redirect" action discussed in Sieve [RFC5228] also apply to this document.
与SIVE[RFC5228]中讨论的“地址”/“信封”/“标题”测试和“重定向”操作相关的安全注意事项也适用于本文档。
External list memberships ought to be treated as if they are 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 failure to retrieve the Sieve script itself.
外部列表成员资格应被视为脚本的一个组成部分，因此访问外部列表的临时失败应以与检索脚本本身的临时失败相同的方式进行处理。
For example, if the Sieve script is stored in the Lightweight Directory Access Protocol [RFC4510] and the script can't be retrieved when a message is processed (perhaps the LDAP server is unavailable), then the Sieve engine might delay message delivery until the script can be retrieved successfully. Similarly, if an external list is stored in LDAP and that LDAP server is unavailable, the Sieve engine would take the same action -- delay message delivery and try again later.
例如，如果Sieve脚本存储在轻量级目录访问协议[RFC4510]中，并且在处理消息时无法检索该脚本（可能LDAP服务器不可用），则Sieve引擎可能会延迟消息传递，直到成功检索该脚本。类似地，如果外部列表存储在LDAP中，并且LDAP服务器不可用，则筛选引擎将执行相同的操作——延迟消息传递，然后重试。
Protocols/APIs used to retrieve/verify external list membership MUST provide an appropriate level of confidentiality and authentication. Usually, that will be at least the same level of confidentiality as protocols/APIs used to retrieve Sieve scripts, but only the implementation (or deployment) will know what is appropriate. There's a difference, for example, between making an LDAP request on a closed LAN that's only used for trusted servers (it may be that neither encryption nor authentication is needed), on a firewalled LAN internal to a company (it might be OK to skip encryption, depending upon policy), and on the open Internet (encryption and authentication are probably both required). It also matters whether the list being accessed is private or public (no encryption or authentication may be needed for public data, even on the Internet).
用于检索/验证外部列表成员资格的协议/API必须提供适当级别的保密性和身份验证。通常，这至少与用于检索筛选脚本的协议/API具有相同的保密级别，但只有实现（或部署）知道什么是合适的。例如，在仅用于受信任服务器的封闭LAN（可能不需要加密或身份验证）上发出LDAP请求，在公司内部的防火墙LAN上发出LDAP请求（可能可以跳过加密，具体取决于策略），以及在开放Internet上发出LDAP请求（可能需要加密和身份验证）。访问的列表是私有的还是公共的也很重要（即使在互联网上，公共数据也不需要加密或身份验证）。
Having the processing and outcome of a Sieve script depend on the contents of external data can allow someone with control of the external data to have unusual, and perhaps unauthorized, control of the script -- and, consequently, of the disposition of the user's email. A user using such a list for spam control, for example, might find important mail being discarded because of tampering with the list. Someone using redirect to an external list could have her email redirected to the wrong eyes because of such tampering. Security and integrity protection of external lists is as important as protection of the Sieve script itself.
让筛选脚本的处理和结果取决于外部数据的内容可以允许控制外部数据的人对脚本进行不寻常的、可能是未经授权的控制，从而控制用户电子邮件的处理。例如，使用此类列表进行垃圾邮件控制的用户可能会发现由于篡改列表而丢弃的重要邮件。由于这种篡改，使用重定向到外部列表的人可能会将她的电子邮件重定向到错误的眼睛。外部列表的安全性和完整性保护与筛选脚本本身的保护一样重要。
Implementations of this extension should keep in mind that matching values against an externally stored list can be I/O and/or CPU intensive. This can be used to deny service to the mail server and/or to servers providing access to externally stored mailing lists. A naive implementation, such as the one that tries to retrieve content of the whole list to perform matching, can make this worse.
这个扩展的实现应该记住，根据外部存储的列表匹配值可能是I/O和/或CPU密集型的。这可用于拒绝向邮件服务器和/或提供对外部存储邮件列表访问权限的服务器提供服务。一个幼稚的实现，比如试图检索整个列表的内容以执行匹配的实现，可能会使情况变得更糟。
But note that many protocols that can be used for accessing externally stored lists support flexible searching features that can be used to minimize network traffic and load on the directory service. For example, LDAP allows for search filters. Implementations SHOULD use such features whenever they can.
但请注意，许多可用于访问外部存储列表的协议支持灵活的搜索功能，这些功能可用于最小化网络流量和目录服务负载。例如，LDAP允许搜索过滤器。实现应该尽可能地使用这些特性。
Many organizations support external lists with thousands of recipients. In order to avoid mailbombs when redirecting a message to an externally stored list, implementations SHOULD enforce limits on the number of recipients and/or on domains to which such recipients belong.
许多组织支持具有数千个收件人的外部列表。为了在将邮件重定向到外部存储的列表时避免邮件炸弹，实现应该对收件人数量和/或此类收件人所属的域实施限制。
Note, in particular, that it can be too easy for a script to use redirect :list ":addrbook:default"; to send messages to "everyone in your address book", and one can
特别要注意的是，脚本使用redirect:list“：addrbook:default”可能太容易了；向“地址簿中的每个人”发送消息，您可以
easily imagine both intentional and accidental abuse. The situation can be even worse for, say, ":addrbook:corporate". Warnings, as well as enforced limits, are appropriate here.
很容易想象故意和意外的虐待。情况可能更糟，比如说，“：addrbook:corporate”。警告和强制限制在这里是合适的。
Applications SHOULD ensure appropriate restrictions are in place to protect sensitive information that might be revealed by "addrbook" URNs from access or modification by untrusted sources.
应用程序应确保有适当的限制，以保护“addrbook”URN可能泄露的敏感信息不受不可信来源的访问或修改。
The following template specifies the IANA registration of the Sieve extension specified in this document. This information has been added to the Sieve Extensions registry on http://www.iana.org.
以下模板指定了本文件中指定的筛网扩展的IANA注册。此信息已添加到上的筛选扩展注册表中http://www.iana.org.
To: iana@iana.org
致：iana@iana.org
Subject: Registration of new Sieve extension
主题：新筛网扩展的注册
Capability name: extlists
功能名称：extlist
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.
描述：将“：list”匹配类型添加到某些筛选测试中，并将“：list”参数添加到“重定向”操作中。“：list”匹配类型更改测试以将值与存储在一个或多个外部存储列表中的值进行匹配。重定向操作的“：list”参数更改重定向操作，将消息转发到外部存储列表中存储的电子邮件地址。
RFC number: RFC 6134
申请编号：RFC6134
Contact address: Sieve mailing list <sieve@ietf.org>
Contact address: Sieve mailing list <sieve@ietf.org>
IANA has registered a new ManageSieve Capability according to the IANA registration template specified in [RFC5804]:
IANA已根据[RFC5804]中指定的IANA注册模板注册了新的ManageSeeve功能：
To: iana@iana.org
致：iana@iana.org
Subject: ManageSieve Capability Registration
主题：管理能力注册
Capability name: extlists
功能名称：extlist
Description: This capability is returned if the server supports the "extlists" RFC 6134 Sieve extension.
描述：如果服务器支持“extlists”RFC 6134筛扩展，则返回此功能。
Relevant publications: RFC 6134, Section 2.8
相关出版物：RFC 6134，第2.8节
Person & email address to contact for further information:
Sieve mailing list <sieve@ietf.org>
Person & email address to contact for further information:
Sieve mailing list <sieve@ietf.org>
Author/Change controller: IESG
作者/变更控制员：IESG
IANA has created a new registry under "Sieve Extensions" for Sieve URN Parameters. Registration into this registry is according to the "Specification Required" policy [RFC5226].
IANA在“筛扩展”下为筛URN参数创建了一个新的注册表。根据“所需规范”政策[RFC5226]注册到此注册表。
The registry contains the following two items:
注册表包含以下两项：
URN parameter name: The name of the URN parameter. If the name is "paramname", the resulting top-level URN will be "urn:ietf:params:sieve:paramname".
URN参数名称：URN参数的名称。如果名称为“paramname”，则生成的顶级URN将为“URN:ietf:params:sieve:paramname”。
Reference: The document and section where the definition of the parameter can be found. Be sure to include the section number as well as the document reference, so the documentation is easy to find.
参考：可以找到参数定义的文档和部分。一定要包括章节号和文档参考，这样文档很容易找到。
The documentation -- which will be in the referenced document and section, and will not be included in the registry -- MUST include the following information (see Section 2.6 for an example):
文档（将在参考文档和章节中，不包括在注册表中）必须包括以下信息（示例见第2.6节）：
URN parameter name: The name of the URN parameter.
URN参数名称：URN参数的名称。
URN parameter syntax: The syntax of the parameter and any sub-parameters, which SHOULD be specified using ABNF [RFC5234].
URN参数语法：参数和任何子参数的语法，应使用ABNF[RFC5234]指定。
Intended usage: A detailed description of how the parameter and any sub-parameters are expected to be used. This is the place to define static sub-parameters, registries for sub-parameters, options, registries for options, and so on.
预期用途：参数和任何子参数预期使用方式的详细说明。这是定义静态子参数、子参数注册表、选项注册表、选项注册表等的地方。
Interoperability considerations: Any notes specific to interoperability issues. This is where to put mandatory-to-implement sub-parameters and the like.
互操作性注意事项：针对互操作性问题的任何注释。这是强制执行子参数等的地方。
Security considerations: Any notes specific to security and privacy issues.
安全注意事项：任何关于安全和隐私问题的说明。
Contact: Contact information, in case there are questions.
联系方式：联系方式，如有疑问。
IANA has registered a new Sieve URN parameter in the registry defined in Section 4.3.
IANA已在第4.3节定义的注册表中注册了一个新的SIFE URN参数。
URN parameter name: addrbook
URN参数名称：addrbook
Reference: RFC 6134, Section 2.6
参考：RFC 6134，第2.6节
IANA has registered a new URN sub-namespace within the IETF URN Sub-namespace for Registered Protocol Parameter Identifiers defined in [RFC3553].
IANA已在IETF URN子命名空间中注册了一个新的URN子命名空间，用于[RFC3553]中定义的已注册协议参数标识符。
Registry name: sieve
注册名称：sieve
Specification: RFC 6134
规格：RFC6134
Repository: Sieve URN Parameters registry (Section 4.3)
存储库：筛选URN参数注册表（第4.3节）
Index value: Sub-parameters MUST be specified in UTF-8, using standard URI encoding where necessary.
索引值：必须在UTF-8中指定子参数，必要时使用标准URI编码。
Thanks to Alexandros Vellis, Nigel Swinson, Ned Freed, Kjetil Torgrim Homme, Dave Cridland, Cyrus Daboo, Pete Resnick, and Robert Burrell Donkin for ideas, comments, and suggestions. Kristin Hubner also helped greatly with the examples.
感谢Alexandros Vellis、Nigel Swinson、Ned Freed、Jetil Torgrim Homme、Dave Cridland、Cyrus Daboo、Pete Resnick和Robert Burrell Donkin提供的想法、评论和建议。克里斯汀·哈伯纳在这些例子中也帮了大忙。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[RFC4151] Kindberg, T. and S. Hawke, "The 'tag' URI Scheme", RFC 4151, October 2005.
[RFC4151]Kindberg，T.和S.Hawke，“标记”URI方案”，RFC 4151，2005年10月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC5228] Guenther, P. and T. Showalter, "Sieve: An Email Filtering Language", RFC 5228, January 2008.
[RFC5228]Guenther，P.和T.Showalter，“筛选：电子邮件过滤语言”，RFC 5228，2008年1月。
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[RFC5804] Melnikov, A. and T. Martin, "A Protocol for Remotely Managing Sieve Scripts", RFC 5804, July 2010.
[RFC5804]Melnikov，A.和T.Martin，“远程管理筛选脚本的协议”，RFC 58042010年7月。
[CardDAV] Daboo, C., "vCard Extensions to WebDAV (CardDAV)", Work in Progress, November 2009.
[CardDAV]Daboo，C.，“WebDAV的vCard扩展（CardDAV）”，正在进行的工作，2009年11月。
[RFC2244] Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.
[RFC2244]Newman，C.和J.Myers，“ACAP——应用程序配置访问协议”，RFC2244，1997年11月。
[RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An IETF URN Sub-namespace for Registered Protocol Parameters", BCP 73, RFC 3553, June 2003.
[RFC3553]Mealling，M.，Masinter，L.，Hardie，T.，和G.Klyne，“注册协议参数的IETF URN子命名空间”，BCP 73，RFC 3553，2003年6月。
[RFC4510] Zeilenga, K., "Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map", RFC 4510, June 2006.
[RFC4510]Zeilenga，K.，“轻量级目录访问协议（LDAP）：技术规范路线图”，RFC45102006年6月。
[RFC5229] Homme, K., "Sieve Email Filtering: Variables Extension", RFC 5229, January 2008.
[RFC5229]Homme，K.，“筛选电子邮件过滤：变量扩展”，RFC5292008年1月。
[RFC5231] Segmuller, W. and B. Leiba, "Sieve Email Filtering: Relational Extension", RFC 5231, January 2008.
[RFC5231]Segmuler，W.和B.Leiba，“筛选电子邮件过滤：关系扩展”，RFC 52312008年1月。
[RFC5233] Murchison, K., "Sieve Email Filtering: Subaddress Extension", RFC 5233, January 2008.
[RFC5233]Murchison，K.，“筛选电子邮件过滤：子地址扩展”，RFC 52332008年1月。
[RFC5235] Daboo, C., "Sieve Email Filtering: Spamtest and Virustest Extensions", RFC 5235, January 2008.
[RFC5235]Daboo，C.，“筛选电子邮件过滤：垃圾邮件测试和病毒测试扩展”，RFC5352008年1月。
[RFC5260] Freed, N., "Sieve Email Filtering: Date and Index Extensions", RFC 5260, July 2008.
[RFC5260]Freed，N.，“筛选电子邮件过滤：日期和索引扩展”，RFC 52602008年7月。
[RFC5435] Melnikov, A., Leiba, B., Segmuller, W., and T. Martin, "Sieve Email Filtering: Extension for Notifications", RFC 5435, January 2009.
[RFC5435]Melnikov，A.，Leiba，B.，Segmuller，W.，和T.Martin，“筛选电子邮件过滤：通知扩展”，RFC 54352009年1月。
[RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)", RFC 5437, January 2009.
[RFC5437]Saint Andre，P.和A.Melnikov，“筛选通知机制：可扩展消息和存在协议（XMPP）”，RFC 5437，2009年1月。
[RFC5463] Freed, N., "Sieve Email Filtering: Ihave Extension", RFC 5463, March 2009.
[RFC5463]Freed，N.，“筛选电子邮件过滤：Ihave扩展”，RFC 54632009年3月。
[RFC5703] Hansen, T. and C. Daboo, "Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure", RFC 5703, October 2009.
[RFC5703]Hansen，T.和C.Daboo，“筛选电子邮件过滤：MIME部分测试、迭代、提取、替换和封装”，RFC 57032009年10月。
Authors' Addresses
作者地址
Alexey Melnikov Isode Limited 5 Castle Business Village 36 Station Road Hampton, Middlesex TW12 2BX UK
英国米德尔塞克斯郡汉普顿车站路36号城堡商业村5号Alexey Melnikov Isode Limited TW12 2BX
EMail: Alexey.Melnikov@isode.com
EMail: Alexey.Melnikov@isode.com
Barry Leiba Huawei Technologies
巴里·雷巴华为技术有限公司
Phone: +1 646 827 0648
EMail: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/
Phone: +1 646 827 0648
EMail: barryleiba@computer.org
URI: http://internetmessagingtechnology.org/