Internet Engineering Task Force (IETF) K. Murchison
Request for Comments: 8580 B. Gondwana
Updates: 5230, 5435 FastMail
Category: Standards Track May 2019
ISSN: 2070-1721
Internet Engineering Task Force (IETF) K. Murchison
Request for Comments: 8580 B. Gondwana
Updates: 5230, 5435 FastMail
Category: Standards Track May 2019
ISSN: 2070-1721
Sieve Extension: File Carbon Copy (FCC)
筛网扩展：文件副本（FCC）
Abstract
摘要
The Sieve email filtering language provides a number of action commands, some of which can generate additional messages on behalf of the user. This document defines an extension to such commands to allow a copy of any generated message to be filed into a target mailbox.
Sieve电子邮件过滤语言提供了许多操作命令，其中一些命令可以代表用户生成其他消息。本文档定义了此类命令的扩展，以允许将生成的任何邮件的副本归档到目标邮箱中。
This document updates RFCs 5230 and 5435 by adding a new tagged argument to the Vacation and Notify actions, respectively.
本文档通过分别向休假和通知操作添加新的标记参数来更新RFCs 5230和5435。
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 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8580.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8580.
Copyright Notice
版权公告
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.
版权（c）2019 IETF信托基金和被确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Tagged Argument ":fcc" . . . . . . . . . . . . . . . . . . . 3
3.1. Interaction with Extensions to the Fileinto Action . . . 3
3.1.1. Imap4flags Extension . . . . . . . . . . . . . . . . 4
3.1.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 4
3.1.3. Special-Use Extension . . . . . . . . . . . . . . . . 4
3.2. Collected Grammar . . . . . . . . . . . . . . . . . . . . 5
4. Format of FCC Messages . . . . . . . . . . . . . . . . . . . 5
5. Interaction with the Vacation Action . . . . . . . . . . . . 6
6. Interaction with the Notify Action . . . . . . . . . . . . . 7
6.1. Notification-Capability "fcc" . . . . . . . . . . . . . . 7
7. Compatibility with the Reject and Extended Reject
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Compatibility with Other Actions . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
11.1. Registration of New Sieve Extension . . . . . . . . . . 9
11.2. Registration of New Notification-Capability
Parameter . . . . . . . . . . . . . . . . . . . . . . . 10
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
12.1. Normative References . . . . . . . . . . . . . . . . . . 10
12.2. Informative References . . . . . . . . . . . . . . . . . 12
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Tagged Argument ":fcc" . . . . . . . . . . . . . . . . . . . 3
3.1. Interaction with Extensions to the Fileinto Action . . . 3
3.1.1. Imap4flags Extension . . . . . . . . . . . . . . . . 4
3.1.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 4
3.1.3. Special-Use Extension . . . . . . . . . . . . . . . . 4
3.2. Collected Grammar . . . . . . . . . . . . . . . . . . . . 5
4. Format of FCC Messages . . . . . . . . . . . . . . . . . . . 5
5. Interaction with the Vacation Action . . . . . . . . . . . . 6
6. Interaction with the Notify Action . . . . . . . . . . . . . 7
6.1. Notification-Capability "fcc" . . . . . . . . . . . . . . 7
7. Compatibility with the Reject and Extended Reject
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Compatibility with Other Actions . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 9
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
11.1. Registration of New Sieve Extension . . . . . . . . . . 9
11.2. Registration of New Notification-Capability
Parameter . . . . . . . . . . . . . . . . . . . . . . . 10
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
12.1. Normative References . . . . . . . . . . . . . . . . . . 10
12.2. Informative References . . . . . . . . . . . . . . . . . 12
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
The Sieve email filtering language [RFC5228] provides a number of action commands, some of which can generate additional messages on behalf of the user. It is sometimes desirable for a Sieve user to maintain an archive of the messages generated by these commands.
Sieve电子邮件过滤语言[RFC5228]提供了许多操作命令，其中一些命令可以代表用户生成其他消息。有时，Sieve用户需要维护由这些命令生成的消息的存档。
This extension defines ":fcc", a new optional tagged argument for action commands that generate additional messages. This argument allows a copy of the generated message to be filed into a target mailbox.
此扩展定义“：fcc”，一个新的可选标记参数，用于生成附加消息的操作命令。此参数允许将生成邮件的副本归档到目标邮箱中。
The capability string associated with this extension is "fcc".
与此扩展关联的功能字符串为“fcc”。
Each new action that generates additional messages will need to specify how it interacts with the FCC extension. This document specifies the interaction of the FCC extension with the Vacation [RFC5230] and Notify [RFC5435] actions.
生成附加消息的每个新操作都需要指定它如何与FCC扩展交互。本文件规定了FCC扩展与休假[RFC5230]和通知[RFC5435]操作的交互。
Conventions for notations are as described in Section 1.1 of [RFC5228], including use of the "Usage:" label for the definition of the action and the syntax of tagged arguments.
注释约定如[RFC5228]第1.1节所述，包括使用“用法：”标签定义动作和标记参数的语法。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
This document specifies ":fcc", a new optional tagged argument that alters the behavior of action commands that generate additional messages on behalf of the user.
本文档指定“：fcc”，这是一个新的可选标记参数，用于改变代表用户生成附加消息的操作命令的行为。
Usage: :fcc <mailbox: string>
Usage: :fcc <mailbox: string>
The ":fcc" tagged argument instructs the Sieve interpreter to file a copy of the generated message into the mailbox provided in the subsequent argument. The semantics and treatment of the mailbox argument are defined to match those of the mailbox argument to the fileinto action specified in Section 4.1 of [RFC5228]. Specifically, use of an invalid mailbox name MAY be treated as an error or result in delivery to an implementation-defined mailbox, and if the specified mailbox doesn't exist, the implementation MAY treat it as an error, create the mailbox, or file the message into an implementation-defined mailbox.
“：fcc”标记参数指示筛解释器将生成消息的副本归档到后续参数中提供的邮箱中。邮箱参数的语义和处理定义为将邮箱参数的语义和处理与[RFC5228]第4.1节中指定的fileinto操作相匹配。具体而言，使用无效邮箱名称可能会被视为错误或导致传递到实现定义的邮箱，如果指定的邮箱不存在，则实现可能会将其视为错误、创建邮箱或将邮件归档到实现定义的邮箱中。
Some tagged arguments defined in extensions to the fileinto action can be used together with the ":fcc" tagged argument. The sections below describe these interactions. Tagged arguments in future extensions to the fileinto action need to describe their interaction with the FCC extension, if any.
fileinto操作的扩展中定义的一些标记参数可以与“：fcc”标记参数一起使用。以下各节描述了这些交互作用。fileinto操作的未来扩展中的标记参数需要描述它们与FCC扩展（如果有）的交互。
When any fileinto extension arguments are used with the FCC extension, the corresponding extension MUST be enabled, and the arguments are defined to have the same syntax, semantics, and treatment as they do with the fileinto action.
当任何fileinto扩展参数与FCC扩展一起使用时，必须启用相应的扩展，并将这些参数定义为具有与fileinto操作相同的语法、语义和处理方式。
This document extends the definition of the ":flags" tagged argument (see Section 5 of [RFC5232]) so that it can optionally be used with the ":fcc" tagged argument.
本文档扩展了“：flags”标记参数的定义（参见[RFC5232]的第5节），因此可以选择将其与“：fcc”标记参数一起使用。
Usage: :fcc <mailbox: string> [:flags <list-of-flags: string-list>]
Usage: :fcc <mailbox: string> [:flags <list-of-flags: string-list>]
If the optional ":flags" tagged argument is specified with the ":fcc" tagged argument, it instructs the Sieve interpreter to set the IMAP4 flags provided in the subsequent argument when the generated message is filed into the target mailbox.
如果可选的“：flags”taged参数与“：fcc”taged参数一起指定，则当生成的消息归档到目标邮箱时，它会指示Sieve解释器设置后续参数中提供的IMAP4标志。
This document extends the definition of the ":create" tagged argument (see Section 3.2 of [RFC5490]) so that it can optionally be used with the ":fcc" tagged argument.
本文档扩展了“：create”标记参数的定义（参见[RFC5490]的第3.2节），因此可以选择将其与“：fcc”标记参数一起使用。
Usage: :fcc <mailbox: string> [:create]
Usage: :fcc <mailbox: string> [:create]
If the optional ":create" tagged argument is specified with the ":fcc" tagged argument, it instructs the Sieve interpreter to create the target mailbox, if needed, before attempting to file the generated message into the target mailbox.
如果可选的“：create”taged参数与“：fcc”taged参数一起指定，则在尝试将生成的邮件归档到目标邮箱之前，它会指示Sieve解释器创建目标邮箱（如果需要）。
This document extends the definition of the ":specialuse" tagged argument (see Section 4 of [RFC8579]) so that it can optionally be used with the ":fcc" tagged argument.
本文档扩展了“：specialuse”标记参数的定义（参见[RFC8579]的第4节），因此可以选择将其与“：fcc”标记参数一起使用。
Usage: :fcc <mailbox: string> [:specialuse <special-use-flag: string>]
Usage: :fcc <mailbox: string> [:specialuse <special-use-flag: string>]
If the optional ":specialuse" tagged argument is specified with the ":fcc" tagged argument, it instructs the Sieve interpreter to check whether a mailbox exists with the specific special-use flag assigned to it. If such a mailbox exists, the generated message is filed into the special-use mailbox. Otherwise, the generated message is filed into the target mailbox.
如果使用“：fcc”标记参数指定了可选的“：specialuse”标记参数，它将指示Sieve解释器检查是否存在分配了特定特殊用途标志的邮箱。如果存在此类邮箱，则生成的邮件将归档到专用邮箱中。否则，生成的邮件将归档到目标邮箱中。
If the optional ":specialuse" and ":create" tagged arguments are both specified with the ":fcc" tagged argument, the Sieve interpreter is instructed to create the target mailbox per Section 4.1 of [RFC8579], if needed.
如果可选的“：specialuse”和“：create”标记的参数都是用“：fcc”标记的参数指定的，则根据[RFC8579]第4.1节的要求，筛解释器将被指示创建目标邮箱（如果需要）。
For convenience, the "FCC" syntax element is defined here using ABNF [RFC5234] so that it can be augmented by other extensions.
为了方便起见，这里使用ABNF[RFC5234]定义了“FCC”语法元素，以便可以通过其他扩展对其进行扩展。
Note that the following is the grammar of "FCC" after it has been lexically interpreted. No whitespace or comments appear below.
请注意，以下是“FCC”经过词汇解释后的语法。下面没有空白或注释。
FCC = ":fcc" string *FCC-OPTS
; per Section 2.6.2 of RFC 5228,
; the tagged arguments in FCC may appear in any order
FCC = ":fcc" string *FCC-OPTS
; per Section 2.6.2 of RFC 5228,
; the tagged arguments in FCC may appear in any order
FCC-OPTS = CREATE / IMAP-FLAGS / SPECIAL-USE
; each option MUST NOT appear more than once
FCC-OPTS = CREATE / IMAP-FLAGS / SPECIAL-USE
; each option MUST NOT appear more than once
CREATE = ":create"
IMAP-FLAGS = ":flags" string-list
SPECIAL-USE = ":specialuse" string
CREATE = ":create"
IMAP-FLAGS = ":flags" string-list
SPECIAL-USE = ":specialuse" string
Copies of messages filed into a mailbox via this extension are REQUIRED to be in the Internet Message Format [RFC5322]. Some messages generated by Sieve actions might already conform to this format and MAY be filed without modification. Messages generated in other formats MUST be encapsulated using constructs from the Internet Message Format [RFC5322] and MIME ([RFC2045], [RFC2046], [RFC2047], [RFC2231]).
通过此扩展提交到邮箱的邮件副本必须采用Internet邮件格式[RFC5322]。由筛选操作生成的某些消息可能已经符合此格式，并且可以在不进行修改的情况下归档。以其他格式生成的消息必须使用来自Internet消息格式[RFC5322]和MIME（[RFC2045]、[RFC2046]、[RFC2047]、[RFC2231]）的构造进行封装。
The general requirements for encapsulating the copies of messages to be filed are as follows:
封装要归档的消息副本的一般要求如下：
o Date: The Date header field is REQUIRED and SHOULD be set to the date and time when the message was generated.
o 日期：日期标题字段是必填字段，应设置为生成消息的日期和时间。
o From: The From header field is REQUIRED and SHOULD be set to the email address of the owner of the Sieve script, unless explicitly overridden by rules for encapsulating a particular message type.
o From：From标头字段是必需的，应设置为Sieve脚本所有者的电子邮件地址，除非封装特定消息类型的规则显式重写。
Per Erratum ID 2035 [Err2035],
根据勘误表ID 2035[Err2035]，
"Informative advice: Users often have multiple email addresses, and "the email address of the owner of the Sieve script" may offer a choice among several. If the sieve processor recognizes an address belonging to the owner of the Sieve script in the To or Cc fields of the input message, then it's
“信息性建议：用户通常有多个电子邮件地址，“筛脚本所有者的电子邮件地址”可能会提供多种选择。如果筛处理器在输入消息的“收件人”或“抄送”字段中识别出属于筛脚本所有者的地址，则该地址为
better to use that address for the From field of the generated message, rather than any other addresses the script's owner may also have".
最好将该地址用于生成的消息的“发件人”字段，而不是脚本所有者也可能拥有的任何其他地址”。
o To: The To header field is OPTIONAL and MAY be set to the email address of the recipient of the generated message, if available.
o 收件人：收件人标题字段是可选的，可以设置为生成邮件的收件人的电子邮件地址（如果可用）。
o Subject: The Subject header field is OPTIONAL and MAY be generated by setting the subject to the characters "Fcc: " followed by the subject of the message being processed by the Sieve interpreter.
o 主题：主题标题字段是可选的，可以通过将主题设置为字符“Fcc:”后接正在由Sieve解释器处理的消息的主题来生成。
o In-Reply-To: The In-Reply-To header field is OPTIONAL and MAY be set to the Message-ID of the message being processed by the Sieve interpreter.
o 回复中：回复中的标题字段是可选的，可以设置为正在由筛选解释器处理的消息的消息ID。
o Message Body: The body of the filed message is REQUIRED and is composed of one or more MIME parts containing the generated message and any related metadata. The Content-Type header field(s) MUST be set to the appropriate MIME types. If any of the MIME parts include 8-bit or binary data, the Content-Transfer-Encoding header field(s) MUST be set accordingly.
o 消息体：已归档消息的主体是必需的，由一个或多个包含生成的消息和任何相关元数据的MIME部分组成。内容类型标头字段必须设置为适当的MIME类型。如果任何MIME部分包含8位或二进制数据，则必须相应地设置内容传输编码头字段。
This document extends the Vacation [RFC5230] action (see also "Seconds" parameter [RFC6131] to optionally store a copy of the auto-reply messages into a target mailbox.
本文档扩展了休假[RFC5230]操作（另请参见“秒”参数[RFC6131]），以选择性地将自动回复邮件的副本存储到目标邮箱中。
Usage: vacation [FCC]
[":days" number | ":seconds" number]
[":subject" string]
[":from" string]
[":addresses" string-list]
[":mime"]
[":handle" string]
<reason: string>
Usage: vacation [FCC]
[":days" number | ":seconds" number]
[":subject" string]
[":from" string]
[":addresses" string-list]
[":mime"]
[":handle" string]
<reason: string>
Example (using fileinto extensions):
示例（使用fileinto扩展）：
require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"];
要求[“休假”、“fcc”、“邮箱”、“特殊用途”、“IMAP4标志”]；
vacation :days 7
:from "hemingway@example.com" "Gone Fishin'"
:specialuse "\\Sent" :create
:fcc "INBOX.Sent" :flags ["\\Seen"];
vacation :days 7
:from "hemingway@example.com" "Gone Fishin'"
:specialuse "\\Sent" :create
:fcc "INBOX.Sent" :flags ["\\Seen"];
Vacation auto-reply messages are compliant with MIME and can be filed into the target mailbox without modification.
假期自动回复邮件符合MIME，无需修改即可提交到目标邮箱。
This document extends the Notify [RFC5435] action to optionally store a copy of the notification messages into a target mailbox.
本文档扩展了Notify[RFC5435]操作，可以选择将通知消息的副本存储到目标邮箱中。
Usage: notify [FCC]
[":from" string]
[":importance" <"1" / "2" / "3">]
[":options" string-list]
[":message" string]
<method: string>
Usage: notify [FCC]
[":from" string]
[":importance" <"1" / "2" / "3">]
[":options" string-list]
[":message" string]
<method: string>
Example:
例子：
require ["enotify", "fcc"];
要求[“enotify”、“fcc”]；
notify :fcc "INBOX.Sent"
:message "You got mail!"
"mailto:ken@example.com";
notify :fcc "INBOX.Sent"
:message "You got mail!"
"mailto:ken@example.com";
Messages generated using the "mailto" [RFC5436] notification method are compliant with MIME and can be filed into the target mailbox without modification.
使用“mailto”[RFC5436]通知方法生成的邮件符合MIME，可以在不进行修改的情况下归档到目标邮箱中。
Messages generated by other notification methods (e.g., "xmpp" [RFC5437]) MUST be encapsulated per Section 4 before being filed. The body of the filed message MUST include the ":message" tagged argument and MAY include one or more of the ":from", ":importance", or ":options" tagged arguments. The MIME type(s) of the body part(s) used to encapsulate the parameters is an implementation decision.
由其他通知方法（如“xmpp”[RFC5437]）生成的消息在归档之前必须按照第4节进行封装。已存档消息的正文必须包含“：message”标记参数，并且可能包含一个或多个“：from”、“：importance”或“：options”标记参数。用于封装参数的主体部分的MIME类型是一个实现决策。
An implementation MAY only support the FCC extension in conjunction with a subset of the notification methods it supports. An error occurs if the FCC extension is used with a notification method that doesn't support it. Notification methods that support the FCC extension can be discovered at runtime using the mechanism described in Section 6.1.
实现只能支持FCC扩展及其支持的通知方法的子集。如果FCC扩展与不支持它的通知方法一起使用，则会发生错误。支持FCC扩展的通知方法可以在运行时使用第6.1节中描述的机制发现。
This document defines "fcc", a new notification-capability value for use with the notify_method_capability test (see Section 5 of [RFC5435]. For the "fcc" notification-capability, the notify_method_capability test can match one of the following key-list values:
本文件定义了“fcc”，这是一个新的通知能力值，用于notify_method_能力测试（参见[RFC5435]第5节）。对于“fcc”通知能力，notify_method_能力测试可以匹配以下关键列表值之一：
yes A copy of the notification message sent using the method identified by the notification-uri can be filed into a target mailbox.
是，可以将使用通知uri标识的方法发送的通知邮件的副本归档到目标邮箱中。
no A copy of the notification message sent using the method identified by the notification-uri cannot be filed into a target mailbox.
否无法将使用通知uri标识的方法发送的通知邮件的副本归档到目标邮箱中。
Note that the "fcc" notify_method_capability test does not require the notification-uri argument to specify anything other than a scheme.
请注意，“fcc”notify_method_能力测试不需要notification uri参数来指定方案以外的任何内容。
Example:
例子：
require ["enotify", "fcc"];
要求[“enotify”、“fcc”]；
if notify_method_capability "xmpp:" "fcc" "yes" {
notify :fcc "INBOX.Sent"
:message "You got mail"
"xmpp:ken@example.com?message;subject=SIEVE";
} else {
notify :fcc "INBOX.Sent"
:message "You got mail!"
"mailto:ken@example.com";
}
if notify_method_capability "xmpp:" "fcc" "yes" {
notify :fcc "INBOX.Sent"
:message "You got mail"
"xmpp:ken@example.com?message;subject=SIEVE";
} else {
notify :fcc "INBOX.Sent"
:message "You got mail!"
"mailto:ken@example.com";
}
Implementations MUST NOT allow use of the FCC extension with the reject and ereject [RFC5429] actions. Allowing use of the FCC extension with these actions would violate the SMTP [RFC5321] principle that a message is either delivered or bounced back to the sender. Namely, the saved copy of the rejection message will contain the original message.
实现必须不允许将FCC扩展和reject[RFC5429]操作一起使用。允许在这些操作中使用FCC扩展将违反SMTP[RFC5321]原则，即消息要么被传递，要么被反弹回发件人。即，拒绝消息的保存副本将包含原始消息。
It is an error for a script to use the ":fcc" tagged argument with either of the reject or ereject actions.
脚本将“：fcc”标记的参数与reject或ERJECT操作一起使用是错误的。
The FCC extension is not compatible with any Sieve action that does not generate an additional message on behalf of the user. It is an error for a script to use the ":fcc" tagged argument with any such action.
FCC扩展与不代表用户生成附加消息的任何筛选操作不兼容。脚本在任何此类操作中使用“：fcc”标记的参数都是错误的。
Future extensions that define actions that generate additional messages on behalf of the user need to describe their compatibility with the FCC extension and describe how to MIME-encapsulate the message, if required.
将来定义代表用户生成附加消息的操作的扩展需要描述它们与FCC扩展的兼容性，并描述如何MIME封装消息（如果需要）。
In addition to the security considerations in [RFC5228], [RFC5230], [RFC5435], and [RFC6131], it should be noted that filing copies of generated messages may cause the Sieve script owner to exceed the allocated storage (quota) on the mail system, thereby preventing delivery of future messages destined for the owner.
除了[RFC5228]、[RFC5230]、[RFC5435]和[RFC6131]中的安全注意事项外，还应注意，归档生成消息的副本可能会导致筛选脚本所有者超过邮件系统上分配的存储（配额），从而阻止将来发送给所有者的消息。
In addition to the privacy considerations in [RFC5228], [RFC5230], [RFC5435], and [RFC6131], it should be noted that a copy of a generated message filed into a shared or public mailbox (as opposed to a private mailbox) could expose private information about the Sieve script owner to third parties. For instance, users that have access to the shared/public mailbox might discover that the Sieve script owner is on holiday or might discover the owner's physical location.
除了[RFC5228]、[RFC5230]、[RFC5435]和[RFC6131]中的隐私注意事项外，还应注意，归档到共享或公共邮箱（而非私人邮箱）中的生成邮件的副本可能会向第三方公开有关筛选脚本所有者的私人信息。例如，有权访问共享/公共邮箱的用户可能会发现Sieve脚本所有者正在度假，或者可能会发现所有者的物理位置。
IANA has registered the following Sieve extension in the "Sieve Extensions" registry at <https://www.iana.org/assignments/sieve-extensions>:
IANA已在“筛网扩展”注册表中注册了以下筛网扩展：<https://www.iana.org/assignments/sieve-extensions>:
Capability name: fcc
功能名称：fcc
Description: Adds the ":fcc" parameter to Sieve action commands that generate additional messages.
描述：添加“：fcc”参数以筛选生成其他消息的操作命令。
RFC number: RFC 8580
RFC编号：RFC 8580
Contact address: The Sieve discussion list <sieve@ietf.org>
Contact address: The Sieve discussion list <sieve@ietf.org>
IANA has registered the following notification-capability parameter in the "Notification-Capability Parameters" registry at <https://www.iana.org/assignments/notification-capability-parameters>:
IANA已在“通知功能参数”注册表中注册了以下通知功能参数<https://www.iana.org/assignments/notification-capability-parameters>:
Capability Name: fcc
功能名称：fcc
Description: Returns whether a copy of the notification message sent using the method identified by the notification-uri parameter to the notify_method_capability test can be filed into a target mailbox.
描述：返回是否可以将使用notification uri参数标识的方法发送到notify_method_功能测试的通知消息副本归档到目标邮箱。
Syntax: Can contain one of two values: "yes" or "no". Values MUST be in lowercase.
语法：可以包含两个值之一：“是”或“否”。值必须为小写。
Reference: RFC 8580
参考：RFC 8580
Contact: The Sieve discussion list <sieve@ietf.org>
Contact: The Sieve discussion list <sieve@ietf.org>
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, <https://www.rfc-editor.org/info/rfc2045>.
[RFC2045]Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第一部分：互联网邮件正文格式”，RFC 2045，DOI 10.17487/RFC20451996年11月<https://www.rfc-editor.org/info/rfc2045>.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, November 1996, <https://www.rfc-editor.org/info/rfc2046>.
[RFC2046]Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第二部分：媒体类型”，RFC 2046，DOI 10.17487/RFC2046，1996年11月<https://www.rfc-editor.org/info/rfc2046>.
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047, November 1996, <https://www.rfc-editor.org/info/rfc2047>.
[RFC2047]Moore，K.，“MIME（多用途互联网邮件扩展）第三部分：非ASCII文本的消息头扩展”，RFC 2047，DOI 10.17487/RFC2047，1996年11月<https://www.rfc-editor.org/info/rfc2047>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations", RFC 2231, DOI 10.17487/RFC2231, November 1997, <https://www.rfc-editor.org/info/rfc2231>.
[RFC2231]Freed，N.和K.Moore，“MIME参数值和编码字扩展：字符集、语言和连续体”，RFC 2231，DOI 10.17487/RFC2231，1997年11月<https://www.rfc-editor.org/info/rfc2231>.
[RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email Filtering Language", RFC 5228, DOI 10.17487/RFC5228, January 2008, <https://www.rfc-editor.org/info/rfc5228>.
[RFC5228]Guenther，P.，Ed.和T.Showalter，Ed.，“筛选：电子邮件过滤语言”，RFC 5228，DOI 10.17487/RFC5228，2008年1月<https://www.rfc-editor.org/info/rfc5228>.
[RFC5230] Showalter, T. and N. Freed, Ed., "Sieve Email Filtering: Vacation Extension", RFC 5230, DOI 10.17487/RFC5230, January 2008, <https://www.rfc-editor.org/info/rfc5230>.
[RFC5230]Showalter，T.和N.Freed，编辑，“筛选电子邮件过滤：假期延长”，RFC 5230，DOI 10.17487/RFC5230，2008年1月<https://www.rfc-editor.org/info/rfc5230>.
[RFC5232] Melnikov, A., "Sieve Email Filtering: Imap4flags Extension", RFC 5232, DOI 10.17487/RFC5232, January 2008, <https://www.rfc-editor.org/info/rfc5232>.
[RFC5232]Melnikov，A.，“筛选电子邮件过滤：Imap4flags扩展”，RFC 5232，DOI 10.17487/RFC5232，2008年1月<https://www.rfc-editor.org/info/rfc5232>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <https://www.rfc-editor.org/info/rfc5234>.
[RFC5234]Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，DOI 10.17487/RFC5234，2008年1月<https://www.rfc-editor.org/info/rfc5234>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, DOI 10.17487/RFC5322, October 2008, <https://www.rfc-editor.org/info/rfc5322>.
[RFC5322]Resnick，P.，Ed.，“互联网信息格式”，RFC 5322，DOI 10.17487/RFC5322，2008年10月<https://www.rfc-editor.org/info/rfc5322>.
[RFC5429] Stone, A., Ed., "Sieve Email Filtering: Reject and Extended Reject Extensions", RFC 5429, DOI 10.17487/RFC5429, March 2009, <https://www.rfc-editor.org/info/rfc5429>.
[RFC5429]Stone，A.，Ed.“筛选电子邮件过滤：拒绝和扩展拒绝扩展”，RFC 5429，DOI 10.17487/RFC5429，2009年3月<https://www.rfc-editor.org/info/rfc5429>.
[RFC5435] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T. Martin, "Sieve Email Filtering: Extension for Notifications", RFC 5435, DOI 10.17487/RFC5435, January 2009, <https://www.rfc-editor.org/info/rfc5435>.
[RFC5435]Melnikov，A.，Ed.，Leiba，B.，Ed.，Segmuller，W.，和T.Martin，“筛选电子邮件过滤：通知扩展”，RFC 5435，DOI 10.17487/RFC5435，2009年1月<https://www.rfc-editor.org/info/rfc5435>.
[RFC5490] Melnikov, A., "The Sieve Mail-Filtering Language -- Extensions for Checking Mailbox Status and Accessing Mailbox Metadata", RFC 5490, DOI 10.17487/RFC5490, March 2009, <https://www.rfc-editor.org/info/rfc5490>.
[RFC5490]Melnikov，A.，“筛选邮件过滤语言——检查邮箱状态和访问邮箱元数据的扩展”，RFC 5490，DOI 10.17487/RFC5490，2009年3月<https://www.rfc-editor.org/info/rfc5490>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[RFC8579] Bosch, S., "Sieve Email Filtering: Delivering to Special-Use Mailboxes", RFC 8579, DOI 10.17487/RFC8579, May 2019, <https://www.rfc-editor.org/info/rfc8579>.
[RFC8579]Bosch，S.，“筛选电子邮件过滤：发送到特殊用途邮箱”，RFC 8579，DOI 10.17487/RFC8579，2019年5月<https://www.rfc-editor.org/info/rfc8579>.
[Err2035] RFC Errata, Errata ID 2035, RFC 5230, <https://www.rfc-editor.org/errata_search.php?eid=2035>.
[Err2035]RFC勘误表，勘误表ID 2035，RFC 5230<https://www.rfc-editor.org/errata_search.php?eid=2035>.
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, DOI 10.17487/RFC5321, October 2008, <https://www.rfc-editor.org/info/rfc5321>.
[RFC5321]Klensin，J.，“简单邮件传输协议”，RFC 5321DOI 10.17487/RFC5321，2008年10月<https://www.rfc-editor.org/info/rfc5321>.
[RFC5436] Leiba, B. and M. Haardt, "Sieve Notification Mechanism: mailto", RFC 5436, DOI 10.17487/RFC5436, January 2009, <https://www.rfc-editor.org/info/rfc5436>.
[RFC5436]Leiba，B.和M.Haardt，“筛选通知机制：mailto”，RFC 5436，DOI 10.17487/RFC5436，2009年1月<https://www.rfc-editor.org/info/rfc5436>.
[RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)", RFC 5437, DOI 10.17487/RFC5437, January 2009, <https://www.rfc-editor.org/info/rfc5437>.
[RFC5437]Saint Andre，P.和A.Melnikov，“筛选通知机制：可扩展消息和存在协议（XMPP）”，RFC 5437，DOI 10.17487/RFC5437，2009年1月<https://www.rfc-editor.org/info/rfc5437>.
[RFC6131] George, R. and B. Leiba, "Sieve Vacation Extension: "Seconds" Parameter", RFC 6131, DOI 10.17487/RFC6131, July 2011, <https://www.rfc-editor.org/info/rfc6131>.
[RFC6131]George，R.和B.Leiba，“筛选假期扩展：“秒”参数”，RFC 6131DOI 10.17487/RFC6131，2011年7月<https://www.rfc-editor.org/info/rfc6131>.
Acknowledgments
致谢
The authors would like to thank the following individuals for contributing their ideas and supporting this specification: Ned Freed, Stan Kalisch, and Alexey Melnikov.
作者要感谢以下个人贡献了他们的想法并支持本规范：Ned Freed、Stan Kalisch和Alexey Melnikov。
Authors' Addresses
作者地址
Kenneth Murchison FastMail US LLC 1429 Walnut Street, Suite 1201 Philadelphia, PA 19102 United States of America
Kenneth Murchison FastMail美国有限责任公司美国宾夕法尼亚州费城胡桃街1429号1201室，邮编：19102
Email: murch@fastmailteam.com
Email: murch@fastmailteam.com
Bron Gondwana FastMail Pty Ltd Level 2, 114 William Street Melbourne, VIC 3000 Australia
澳大利亚维多利亚州墨尔本威廉街114号Bron Gondwana FastMail Pty Ltd二层
Email: brong@fastmailteam.com
Email: brong@fastmailteam.com