Network Working Group R. Gellens
Request for Comments: 5423 QUALCOMM Inc.
Category: Standards Track C. Newman
Sun Microsystems
March 2009
Network Working Group R. Gellens
Request for Comments: 5423 QUALCOMM Inc.
Category: Standards Track C. Newman
Sun Microsystems
March 2009
Internet Message Store Events
Internet消息存储事件
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托在本文件出版之日生效的与IETF文件有关的法律规定的约束(http://trustee.ietf.org/license-info). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Abstract
摘要
One of the missing features in the existing Internet mail and messaging standards is a facility for server-to-server and server-to-client event notifications related to message store events. As the scope of Internet mail expands to support more diverse media (such as voice mail) and devices (such as cell phones) and to provide rich interactions with other services (such as web portals and legal compliance systems), the need for an interoperable notification system increases. This document attempts to enumerate the types of events that interest real-world consumers of such a system.
现有Internet邮件和消息传递标准中缺少的一个功能是一个用于服务器到服务器和服务器到客户端的与消息存储事件相关的事件通知的功能。随着互联网邮件的范围扩展到支持更多样化的媒体（如语音邮件）和设备（如手机），并提供与其他服务（如门户网站和法律合规系统）的丰富交互，对可互操作通知系统的需求也随之增加。本文档试图列举此类系统的真实用户感兴趣的事件类型。
This document describes events and event parameters that are useful for several cases, including notification to administrative systems and end users. This is not intended as a replacement for a message access facility such as IMAP.
本文档描述了对几种情况有用的事件和事件参数，包括向管理系统和最终用户发出的通知。这并不是要取代IMAP等消息访问工具。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Event Model . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Event Types . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Message Addition and Deletion . . . . . . . . . . . . . . 5
4.2. Message Flags . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Access Accounting . . . . . . . . . . . . . . . . . . . . 8
4.4. Mailbox Management . . . . . . . . . . . . . . . . . . . . 8
5. Event Parameters . . . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Future Extensions . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Event Model . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Event Types . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Message Addition and Deletion . . . . . . . . . . . . . . 5
4.2. Message Flags . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Access Accounting . . . . . . . . . . . . . . . . . . . . 8
4.4. Mailbox Management . . . . . . . . . . . . . . . . . . . . 8
5. Event Parameters . . . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Future Extensions . . . . . . . . . . . . . . . . . . 17
A message store is used to organize Internet Messages [RFC5322] into one or more mailboxes (possibly hierarchical), annotate them in various ways, and provide access to these messages and associated metadata. Three different standards-based protocols have been widely deployed to remotely access a message store. The Post Office Protocol (POP) [RFC1939] provides simple download-and-delete access to a single mail drop (which is a subset of the functionality typically associated with a message store). The Internet Message Access Protocol (IMAP) [RFC3501] provides an extensible feature-rich model for online, offline, and disconnected access to a message store with minimal constraints on any associated "fat-client" user interface. Finally, mail access applications built on top of the Hypertext Transfer Protocol (HTTP) [RFC2616] that run in standards-based web browsers provide a third standards-based access mechanism for online-only access.
消息存储用于将Internet消息[RFC5322]组织到一个或多个邮箱中（可能是分层的），以各种方式对它们进行注释，并提供对这些消息和相关元数据的访问。三种不同的基于标准的协议已被广泛部署用于远程访问消息存储。邮局协议（POP）[RFC1939]提供对单个邮件投递的简单下载和删除访问（这是通常与邮件存储相关联的功能的子集）。互联网消息访问协议（IMAP）[RFC3501]为在线、离线和断开连接访问消息存储提供了一个可扩展的功能丰富的模型，对任何相关的“胖客户端”用户界面的限制最小。最后，基于超文本传输协议（HTTP）[RFC2616]构建的邮件访问应用程序在基于标准的web浏览器中运行，为仅在线访问提供了第三种基于标准的访问机制。
While simple and/or ad-hoc mechanisms for notifications have sufficed to some degree in the past (e.g., "Simple New Mail Notification" [RFC4146], "IMAP4 IDLE Command" [RFC2177]), as the scope and importance of message stores expand, the demand for a more complete store notification system increases. Some of the driving forces behind this demand include:
虽然简单和/或特别的通知机制在过去在某种程度上已经足够（例如，“简单新邮件通知”[RFC4146]、“IMAP4空闲命令”[RFC2177]），但随着消息存储的范围和重要性的扩大，对更完整的存储通知系统的需求增加。这一需求背后的一些驱动力包括：
o Mobile devices with intermittent network connectivity that have "new mail" or "message count" indicators.
o 具有间歇性网络连接且具有“新邮件”或“邮件计数”指示器的移动设备。
o Unified messaging systems that include both Internet and voice mail require support for a message-waiting indicator on phones.
o 包括Internet和语音邮件的统一消息系统需要支持手机上的消息等待指示器。
o Interaction with systems for event-based or utility-computing billing.
o 与基于事件或效用计算计费的系统交互。
o Simplification of the process of passing message store events to non-Internet notification systems.
o 简化将消息存储事件传递给非Internet通知系统的过程。
o A calendar system may wish to subscribe to MessageNew notifications in order to support iMIP [RFC2447].
o 日历系统可能希望订阅MessageNew通知以支持iMIP[RFC2447]。
o Some jurisdictions have laws or regulations for information protection and auditing that require interoperable protocols between message stores built by messaging experts and compliance auditing systems built by compliance experts.
o 一些司法管辖区制定了信息保护和审核的法律或法规，这些法律或法规要求在由消息传递专家构建的消息存储和由法规遵从性专家构建的法规遵从性审核系统之间使用可互操作的协议。
Vendors who have deployed proprietary notification systems for their Internet message stores have seen significant demand to provide notifications for more and more events. As a first step towards building a notification system, this document attempts to enumerate the core events that real-world customers demand.
已经为其互联网消息存储部署了专有通知系统的供应商已经看到了为越来越多的事件提供通知的巨大需求。作为构建通知系统的第一步，本文档试图列举现实世界客户需要的核心事件。
This document includes those events that can be generated by the use of IMAP4rev1 [RFC3501] and some existing extensions. As new IMAP extensions are defined, or additional event types or parameters need to be added, the set specified here can be extended by means of an IANA registry with update requirements, as specified in Section 6.
本文档包括可通过使用IMAP4rev1[RFC3501]和一些现有扩展生成的事件。由于定义了新的IMAP扩展，或者需要添加额外的事件类型或参数，此处指定的集合可以通过具有更新要求的IANA注册表进行扩展，如第6节所述。
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 RFC 2119 [RFC2119]. When these words appear in lower-case or with initial capital letters, they are not RFC 2119 key words.
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。当这些单词以小写或首字母大写出现时，它们不是RFC 2119关键字。
The following terminology is used in this document:
本文件使用以下术语：
mailbox A container for Internet messages and/or child mailboxes. A mailbox may or may not permit delivery of new messages via a mail delivery agent.
邮箱用于Internet邮件和/或子邮箱的容器。邮箱可能允许也可能不允许通过邮件传递代理传递新邮件。
mailbox identifier A mailbox identifier provides sufficient information to identify a specific mailbox on a specific server instance. An IMAP URL can be a mailbox identifier.
邮箱标识符邮箱标识符提供足够的信息来标识特定服务器实例上的特定邮箱。IMAP URL可以是邮箱标识符。
message access protocols Protocols that provide clients (e.g., a mail user agent or web browser) with access to the message store, including but not limited to IMAP, POP, and HTTP.
消息访问协议为客户端（例如，邮件用户代理或web浏览器）提供对消息存储的访问权限的协议，包括但不限于IMAP、POP和HTTP。
message context As defined in [RFC3458].
[RFC3458]中定义的消息上下文。
UIDVALIDITY As defined in IMAP4rev1 [RFC3501]. UIDVALIDITY is critical to the correct operation of a caching mail client. When it changes, the client MUST flush its cache. It's particularly important to include UIDVALIDITY with event notifications related to message addition or removal in order to keep the message data correctly synchronized.
IMAP4rev1[RFC3501]中定义的UID有效性。UIDVality对于缓存邮件客户端的正确操作至关重要。当它发生更改时，客户端必须刷新其缓存。为了保持消息数据的正确同步，将UIDVality包含在与消息添加或删除相关的事件通知中尤为重要。
The events that are generated by a message store depend to some degree on the model used to represent a message store. The model the IETF has for a message store is implicit from IMAP4rev1 and extensions, so that model is assumed by this document.
消息存储生成的事件在某种程度上取决于用于表示消息存储的模型。IETF的消息存储模型来自IMAP4rev1和扩展，因此本文档采用该模型。
A message store event typically has an associated mailbox name and usually has an associated user name (or authorization identity if using the terminology from "Simple Authentication and Security Layer" (SASL) [RFC4422]). Events referring to a specific message can use an IMAP URL [RFC5092] to do so. Events referring to a set of messages can use an IMAP URL to the mailbox plus an IMAP UID (Unique Identifier) set.
消息存储事件通常具有关联的邮箱名称，并且通常具有关联的用户名（如果使用“简单身份验证和安全层”（SASL）[RFC4422]中的术语，则为授权标识）。引用特定消息的事件可以使用IMAP URL[RFC5092]来执行此操作。引用一组邮件的事件可以使用邮箱的IMAP URL和IMAP UID（唯一标识符）集。
Each notification has a type and parameters. The type determines the type of event, while the parameters supply information about the context of the event that may be used to adjust subscription preferences or may simply supply data associated with the event. The types and parameter names in this document are restricted to US-ASCII printable characters, so these events can be easily mapped to an arbitrary notification system. However, this document assumes that arbitrary parameter values (including large and multi-line values) can be encoded with the notification system. Systems which lack that feature could only implement a subset of these events.
每个通知都有一个类型和参数。类型决定事件的类型，而参数提供有关事件上下文的信息，这些信息可用于调整订阅首选项，或仅提供与事件关联的数据。本文档中的类型和参数名称仅限于US-ASCII可打印字符，因此这些事件可以轻松映射到任意通知系统。但是，本文档假定可以使用通知系统对任意参数值（包括大的和多行的值）进行编码。缺少该功能的系统只能实现这些事件的一个子集。
This document does not indicate which event parameters are mandatory or optional. That is done in documents that specify specific message formats or bindings to a notification system.
本文档未指明哪些事件参数是必需的或可选的。这是在指定特定消息格式或通知系统绑定的文档中完成的。
For scalability reasons, some degree of filtering at event generation is necessary. At the very least, the ability to turn on and off groups of related events and to suppress inclusion of large parameters (such as messageContent) is needed. A sophisticated publish/subscribe notification system may be able to propagate cumulative subscription information to the publisher.
出于可伸缩性的原因，需要在事件生成时进行一定程度的过滤。至少，需要能够打开和关闭相关事件组，并禁止包含大型参数（如messageContent）。复杂的发布/订阅通知系统可能能够将累积订阅信息传播给发布者。
Some of these events might be logically collapsed into a single event type with a required parameter to distinguish between the cases (e.g., QuotaExceed and QuotaWithin). However, until such time that an event subscription model is formulated, it's not practical to make such decisions. We thus note only the fact that some of these events may be viewed as a single event type.
其中一些事件可能在逻辑上被折叠为单个事件类型，并带有一个必需的参数来区分这些情况（例如，QuotaExceed和QuotaWithin）。然而，在制定事件订阅模型之前，做出这样的决定是不实际的。因此，我们只注意到其中一些事件可能被视为单一事件类型。
This section discusses the different types of events useful in a message store event notification system. The intention is to document the events sufficient to cover an overwhelming majority of known use cases while leaving less common event types for the future. This section mentions parameters that are important or specific to the events described here. Event parameters likely to be included in most or all notifications are discussed in the next section.
本节讨论在消息存储事件通知系统中有用的不同类型的事件。目的是记录足以覆盖绝大多数已知用例的事件，同时为将来留下不太常见的事件类型。本节提到了此处所述事件的重要或特定参数。下一节将讨论可能包含在大多数或所有通知中的事件参数。
This section includes events related to message addition and deletion.
本节包括与消息添加和删除相关的事件。
MessageAppend A message was appended or concatenated to a mailbox by a message access client. For the most part, this is identical to the MessageNew event type except that the SMTP envelope information is not included as a parameter, but information about which protocol triggered the event MAY be included. See the MessageNew event for more information.
MessageAppend消息访问客户端将消息追加或连接到邮箱。在大多数情况下，这与MessageNew事件类型相同，只是SMTP信封信息未作为参数包含，但可能包含有关触发事件的协议的信息。有关更多信息，请参阅消息new event。
MessageExpire One or more messages were expired from a mailbox due to server expiration policy and are no longer accessible by the end user.
MessageExpire由于服务器过期策略，邮箱中的一封或多封邮件已过期，最终用户无法再访问这些邮件。
The parameters include a mailbox identifier that MUST include UIDVALIDITY and a UID set that describes the messages.
这些参数包括必须包含UIDVality的邮箱标识符和描述邮件的UID集。
Information about which server expiration policy was applied may be included in the future.
将来可能会包含有关应用了哪个服务器过期策略的信息。
MessageExpunge One or more messages were expunged from a mailbox by an IMAP CLOSE/EXPUNGE, POP3 DELE+QUIT, HTTP, or equivalent client action and are no longer accessible by the end user.
MessageExpunge通过IMAP CLOSE/EXPUNGE、POP3 DELE+QUIT、HTTP或等效的客户端操作从邮箱中删除了一封或多封邮件，最终用户无法再访问这些邮件。
The parameters include a mailbox identifier that MUST include UIDVALIDITY, a UID set, and MAY also indicate which access protocol triggered the event.
这些参数包括邮箱标识符（必须包含UIDVality）、UID集，还可能指示触发事件的访问协议。
MessageNew A new message was received into a mailbox via a message delivery agent.
MessageNew通过邮件传递代理将新邮件接收到邮箱中。
The parameters include a message identifier that, for IMAP-accessible message stores, MUST include UIDVALIDITY and a UID. The parameters MAY also include an SMTP envelope and other arbitrary message and mailbox metadata. In some cases, the entire new message itself may be included. The set of parameters SHOULD be adjustable to the client's preference, with limits set by server policy. An interesting policy, for example, would be to include messages up to 2K in size with the notification, but to include a URLAUTH [RFC4467] reference for larger messages.
参数包括消息标识符，对于IMAP可访问的消息存储，该标识符必须包括UIDVality和UID。参数还可能包括SMTP信封和其他任意邮件和邮箱元数据。在某些情况下，可能会包含整个新消息本身。参数集应可根据客户端的偏好进行调整，限制由服务器策略设置。例如，一个有趣的策略是在通知中包含大小不超过2K的消息，但对于较大的消息，则包含URLAUTH[RFC4467]引用。
QuotaExceed An operation failed (typically MessageNew) because the user's mailbox exceeded one of the quotas (e.g., disk quota, message quota, quota by message context, etc.). The parameters SHOULD include at least the relevant user and quota and, optionally, the mailbox. Quota usage SHOULD be included if possible. Parameters needed to extend this to support quota by context are not presently described in this document but could be added in the future.
QuotaExceed操作失败（通常是MessageNew），因为用户的邮箱超过了一个配额（例如，磁盘配额、邮件配额、邮件上下文配额等）。参数应至少包括相关用户和配额，以及邮箱（可选）。如有可能，应包括配额使用情况。本文档目前未描述扩展此功能以支持按上下文划分的配额所需的参数，但可以在将来添加这些参数。
QuotaWithin An operation occurred (typically MessageExpunge or MessageExpire) that reduced the user's quota usage under the limit.
QuotaWithin发生的操作（通常是MessageExpunge或MessageExpire）将用户的配额使用率降低到限制以下。
QuotaChange The user's quota was changed.
QuotaChange用户的配额已更改。
This section includes events related to changes in message flags.
本节包括与消息标志更改相关的事件。
MessageRead One or more messages in the mailbox were marked as read or seen by a user. Note that POP has no concept of read or seen messages, so these events are only generated by IMAP or HTTP clients (or equivalent).
MessageRead用户已将邮箱中的一封或多封邮件标记为已读或已看到。请注意，POP没有读取或查看消息的概念，因此这些事件仅由IMAP或HTTP客户端（或等效客户端）生成。
The parameters include a mailbox identifier and a set of message UIDs.
这些参数包括邮箱标识符和一组消息UID。
MessageTrash One or more messages were marked for future deletion by the user but are still accessible over the protocol (the user's client may or may not make these messages accessible through its user interface).
MessageTrash一条或多条消息被用户标记为将来删除，但仍然可以通过协议访问（用户的客户端可以或不可以通过其用户界面访问这些消息）。
The parameters include a mailbox identifier and a set of message UIDs.
这些参数包括邮箱标识符和一组消息UID。
FlagsSet One or more messages in the mailbox had one or more IMAP flags or keywords set.
标志设置邮箱中的一封或多封邮件设置了一个或多个IMAP标志或关键字。
The parameters include a list of IMAP flag or keyword names that were set, a mailbox identifier, and the set of UIDs of affected messages. The flagNames MUST NOT include \Recent. For compatibility with simpler clients, it SHOULD be configurable whether setting the \Seen or \Deleted flags results in this event or the simpler MessageRead/MessageTrash events. By default, the simpler message forms SHOULD be used for MessageRead and MessageTrash.
这些参数包括已设置的IMAP标志或关键字名称列表、邮箱标识符以及受影响邮件的UID集。标记名不能包括\Recent。为了与更简单的客户端兼容，应可配置设置\Seen或\Deleted标志是否会导致此事件或更简单的MessageRead/MessageTrash事件。默认情况下，MessageRead和MessageTrash应该使用更简单的消息表单。
FlagsClear One or more messages in the mailbox had one or more IMAP flags or keywords cleared.
标志清除邮箱中的一封或多封邮件清除了一个或多个IMAP标志或关键字。
The parameters include a list of IMAP flag or keyword names that were cleared, a mailbox identifier, and the set of UIDs of affected messages. The flagNames parameter MUST NOT include \Recent.
这些参数包括已清除的IMAP标志或关键字名称列表、邮箱标识符以及受影响邮件的UID集。flagNames参数不能包括\Recent。
This section lists events related to message store access accounting.
本节列出与消息存储访问记帐相关的事件。
Login A user has logged into the system via IMAP, HTTP, POP, or some other mechanism.
登录用户已通过IMAP、HTTP、POP或其他机制登录到系统。
The parameters include the domain name and port used to access the server and the user's authorization identity. Additional possible parameters include the client's IP address and port, the authentication identity (if different from the authorization identity), the service name, the authentication mechanism, information about any negotiated security layers, a timestamp, and other information.
参数包括用于访问服务器的域名和端口以及用户的授权标识。其他可能的参数包括客户端的IP地址和端口、身份验证标识（如果与授权标识不同）、服务名称、身份验证机制、有关任何协商安全层的信息、时间戳和其他信息。
Logout A user has logged out or otherwise been disconnected from the message store via IMAP, HTTP, POP, or some other mechanism.
注销用户已注销或已通过IMAP、HTTP、POP或其他机制从消息存储区断开连接。
The parameters include the server domain name and the user's authorization identity. Additional parameters MAY include any of the information from the "Login" event as well as information about the type of disconnect (suggested values include graceful, abort, timeout, and security layer error), the duration of the connection or session, and other information.
参数包括服务器域名和用户的授权标识。其他参数可能包括来自“登录”事件的任何信息以及有关断开连接类型的信息（建议值包括正常、中止、超时和安全层错误）、连接或会话的持续时间以及其他信息。
This section lists events related to the management of mailboxes.
本节列出与邮箱管理相关的事件。
MailboxCreate A mailbox has been created, or an access control changed on an existing mailbox so that it is now accessible by the user. If the mailbox creation caused the creation of new mailboxes earlier in the hierarchy, separate MailboxCreate events are not generated, as their creation is implied.
MailboxCreate已创建邮箱，或已更改现有邮箱的访问控制，以便用户现在可以访问该邮箱。如果邮箱创建导致在层次结构的早期创建新邮箱，则不会生成单独的MailboxCreate事件，因为它们的创建是隐含的。
The parameters include the created mailbox identifier, its UIDVALIDITY for IMAP-accessible message stores, and MAY also indicate which access protocol triggered the event. Access and permissions information (such as Access Control List (ACL) [RFC4314] settings) require a standardized format to be included, and so are left for future extension.
这些参数包括创建的邮箱标识符、其对IMAP可访问邮件存储的UIDVality，还可能指示触发事件的访问协议。访问和权限信息（如访问控制列表（ACL）[RFC4314]设置）需要包含标准格式，因此留作将来扩展。
MailboxDelete A mailbox has been deleted, or an access control changed on an existing mailbox so that it is no longer accessible by the user. Note that if the mailbox has child mailboxes, only the specified mailbox has been deleted, not the children. The mailbox becomes \NOSELECT, and the hierarchy remains unchanged, as per the description of the DELETE command in IMAP4rev1 [RFC3501].
MailboxDelete邮箱已被删除，或者现有邮箱上的访问控制已更改，用户无法再访问该邮箱。请注意，如果邮箱具有子邮箱，则仅删除了指定的邮箱，而未删除子邮箱。根据IMAP4rev1[RFC3501]中删除命令的描述，邮箱变为\n选择，层次结构保持不变。
The parameters include the deleted mailbox identifier and MAY also indicate which access protocol triggered the event.
这些参数包括已删除的邮箱标识符，还可能指示触发事件的访问协议。
MailboxRename A mailbox has been renamed. Note that, per the description of the RENAME command in IMAP4rev1 [RFC3501], special semantics regarding the mailbox hierarchy apply when INBOX is renamed (child mailboxes are usually included in the rename, but are excluded when INBOX is renamed). When a mailbox other than INBOX is renamed and its child mailboxes are also renamed as a result, separate MailboxRename events are not generated for the child mailboxes, as their renaming is implied. If the rename caused the creation of new mailboxes earlier in the hierarchy, separate MailboxCreate events are not generated for those, as their creation is implied. When INBOX is renamed, a new INBOX is created. A MailboxCreate event is not generated for the new INBOX, since it is implied.
MailboxRename邮箱已重命名。请注意，根据IMAP4rev1[RFC3501]中重命名命令的描述，有关邮箱层次结构的特殊语义在重命名收件箱时适用（子邮箱通常包括在重命名中，但在重命名收件箱时除外）。如果重命名收件箱以外的邮箱，并且其子邮箱也因此重命名，则不会为子邮箱生成单独的MailboxRename事件，因为这意味着子邮箱的重命名。如果重命名导致在层次结构的早期创建新邮箱，则不会为这些邮箱生成单独的MailboxCreate事件，因为它们的创建是隐含的。重命名收件箱时，将创建一个新的收件箱。不会为新收件箱生成MailboxCreate事件，因为它是隐含的。
The parameters include the old mailbox identifier, the new mailbox identifier, and MAY also indicate which access protocol triggered the event.
这些参数包括旧邮箱标识符、新邮箱标识符，还可能指示触发事件的访问协议。
MailboxSubscribe A mailbox has been added to the server-stored subscription list, such as the one managed by the IMAP SUBSCRIBE and UNSUBSCRIBE commands.
MailboxSubscribe已将邮箱添加到服务器存储的订阅列表中，例如由IMAP SUBSCRIBE和UNSUBSCRIBE命令管理的邮箱。
The parameters include the user whose subscription list has been affected, the mailbox identifier, and MAY also indicate which access protocol triggered the event.
这些参数包括订阅列表受到影响的用户、邮箱标识符，还可能指示触发事件的访问协议。
MailboxUnSubscribe A mailbox has been removed from the subscription list.
邮箱取消订阅邮箱已从订阅列表中删除。
The parameters include the user whose subscription list has been affected, the mailbox identifier, and MAY also indicate which access protocol triggered the event.
这些参数包括订阅列表受到影响的用户、邮箱标识符，还可能指示触发事件的访问协议。
This section lists parameters included with these events.
本节列出了这些事件中包含的参数。
admin Included with all events generated by message access protocols.
admin包含在消息访问协议生成的所有事件中。
The authentication identity associated with this event, as distinct from the authorization identity (see "user"). This is not included when it is the same as the value of the user parameter.
与此事件关联的身份验证标识，与授权标识不同（请参阅“用户”）。如果该值与用户参数的值相同，则不包括该值。
bodyStructure May be included with MessageAppend and MessageNew.
MessageAppend和MessageNew中可能包含bodyStructure。
The IMAP BODYSTRUCTURE of the message.
消息的IMAP主体结构。
clientIP Included with all events generated by message access protocols.
clientIP包含在消息访问协议生成的所有事件中。
The IPv4 or IPv6 address of the message store access client that performed the action that triggered the notification.
执行触发通知的操作的消息存储访问客户端的IPv4或IPv6地址。
clientPort Included with all events generated by message access protocols.
clientPort包含在消息访问协议生成的所有事件中。
The port number of the message store access client that performed an action that triggered the notification (the port from which the connection occurred).
执行触发通知的操作的消息存储访问客户端的端口号（发生连接的端口）。
diskQuota Included with QuotaExceed, QuotaWithin, and QuotaChange notifications relating to a user or mailbox disk quota. May be included with other notifications.
与用户或邮箱磁盘配额相关的QuotaExceed、QuotaWithin和QuotaChange通知中包含的diskQuota。可能包括在其他通知中。
Disk quota limit in kilobytes (1024 octets).
磁盘配额限制，以千字节（1024个八位字节）为单位。
diskUsed Included with QuotaExceed and QuotaWithin notifications relating to a user or mailbox disk quota. May be included with other notifications.
diskUsed包含在与用户或邮箱磁盘配额相关的QuoteExceed和QuoteAWithin通知中。可能包括在其他通知中。
Disk space used in kilobytes (1024 octets). Only disk space that counts against the quota is included.
以千字节（1024个八位字节）为单位使用的磁盘空间。仅包括根据配额计数的磁盘空间。
envelope May be included with the MessageNew notification.
信封可能包含在MessageNew通知中。
The message transfer envelope associated with final delivery of the message for the MessageNew notification. This includes the MAIL FROM and relevant RCPT TO line(s) used for final delivery with CRLF delimiters and any ESMTP parameters.
与MessageNew通知的消息最终传递关联的消息传输信封。这包括使用CRLF定界符和任何ESMTP参数进行最终传递时使用的邮件发送行和相关RCPT发送行。
flagNames Included with FlagsSet and FlagsClear events. May be included with MessageAppend and MessageNew to indicate flags that were set initially by the APPEND command or delivery agent, respectively.
FlagsSet和FlagsClear事件中包含的FlagName。可以与MessageAppend和MessageNew一起包含，以指示最初分别由APPEND命令或传递代理设置的标志。
A list (likely to be space-separated) of IMAP flag or keyword names that were set or cleared. Flag names begin with a backslash while keyword names do not. The \Recent flag is explicitly not permitted in the list.
已设置或清除的IMAP标志或关键字名称的列表（可能以空格分隔）。标志名称以反斜杠开头，而关键字名称不以反斜杠开头。列表中明确不允许使用\Recent标志。
mailboxID Included in events that affect mailboxes. A URI describing the mailbox. In the case of MailboxRename, this refers to the new name.
影响邮箱的事件中包含mailboxID。描述邮箱的URI。对于MailboxRename，它指的是新名称。
maxMessages Included with QuotaExceed and QuotaWithin notifications relating to a user or mailbox message count quota. May be included with other notifications.
与用户或邮箱邮件计数配额相关的通知中包含的QUOTAEEXCEED和QUOTAWITIN中包含的maxMessages。可能包括在其他通知中。
Quota limit on the number of messages in the mailbox, for events referring to a mailbox.
对于引用邮箱的事件，邮箱中邮件数的配额限制。
messageContent May be included with MessageAppend and MessageNew.
messageContent可能包含在MessageAppend和MessageNew中。
The entire message itself. Size-based suppression of this SHOULD be available.
整个信息本身。应提供基于大小的抑制。
messageSize May be included with MessageAppend and MessageNew.
messageSize可能包含在MessageAppend和MessageNew中。
Size of the RFC 5322 message itself in octets. This value matches the length of the IMAP literal returned in response to an IMAP FETCH of BODY[] for the referenced message.
RFC 5322消息本身的大小（以八位字节为单位）。此值与为响应被引用消息的主体[]的IMAP获取而返回的IMAP文本的长度匹配。
messages Included with QuotaExceed and QuotaWithin notifications relating to a user or mailbox message count quota. May be included with other notifications.
与用户或邮箱邮件计数配额相关的通知中包含的QuotaExceed和QuotaWithin消息。可能包括在其他通知中。
Number of messages in the mailbox. This is typically included with message addition and deletion events.
邮箱中的邮件数。这通常包含在消息添加和删除事件中。
modseq May be included with any notification referring to one message.
modseq可包含在涉及一条消息的任何通知中。
This is the 64-bit integer MODSEQ as defined in [RFC4551]. No assumptions about MODSEQ can be made if this is omitted.
这是[RFC4551]中定义的64位整数MODSEQ。如果省略此项，则无法对MODSEQ进行任何假设。
oldMailboxID A URI describing the old name of a renamed or moved mailbox.
oldMailboxID描述重命名或移动邮箱的旧名称的URI。
pid May be included with any notification.
pid可包含在任何通知中。
The process ID of the process that generated the notification.
生成通知的进程的进程ID。
process May be included with any notification.
任何通知都可能包含该过程。
The name of the process that generated the notification.
生成通知的进程的名称。
serverDomain Included in Login and optionally in Logout or other events. The domain name or IP address (v4 or v6) used to access the server or mailbox.
serverDomain包含在登录和注销或其他事件中（可选）。用于访问服务器或邮箱的域名或IP地址（v4或v6）。
serverPort Included in Login and optionally in Logout or other events. The port number used to access the server. This is often a well-known port.
服务器端口包括在登录和注销或其他事件中（可选）。用于访问服务器的端口号。这通常是一个著名的港口。
serverFQDN May be included with any notification.
serverFQDN可能包含在任何通知中。
The fully qualified domain name of the server that generated the event. Note that this may be different from the server name used to access the mailbox included in the mailbox identifier.
生成事件的服务器的完全限定域名。请注意，这可能与用于访问邮箱标识符中包含的邮箱的服务器名称不同。
service May be included with any notification.
服务可能包括在任何通知中。
The name of the service that triggered the event. Suggested values include "imap", "pop", "http", and "admincli" (for an administrative client).
触发事件的服务的名称。建议的值包括“imap”、“pop”、“http”和“admincli”（适用于管理客户端）。
tags May be included with any notification.
标签可能包含在任何通知中。
A list of UTF-8 tags (likely to be comma-separated). One or more tags can be set at the time a notification criteria or notification subscription is created. Subscribers can use tags for additional client-side filtering or dispatch of events.
UTF-8标记列表（可能以逗号分隔）。可以在创建通知条件或通知订阅时设置一个或多个标记。订阅者可以使用标记进行额外的客户端筛选或事件分派。
timestamp May be included with any notification.
时间戳可以包括在任何通知中。
The time at which the event occurred that triggered the notification (the underlying protocol carrying the notification may contain a timestamp for when the notification was generated). This MAY be an approximate time.
触发通知的事件发生的时间（承载通知的基础协议可能包含生成通知的时间戳）。这可能是一个大概的时间。
Timestamps are expressed in local time and contain the offset from UTC (this information is used in several places in Internet mail) and are normally in [RFC3339] format.
时间戳以本地时间表示，包含UTC的偏移量（此信息在Internet邮件中的多个位置使用），通常采用[RFC3339]格式。
uidnext May be included with any notification referring to a mailbox.
uidnext可能包含在任何涉及邮箱的通知中。
The UID that is projected to be assigned next in the mailbox. This is typically included with message addition and deletion events. This is equivalent to the UIDNEXT status item in the IMAP STATUS command.
计划在邮箱中下一个分配的UID。这通常包含在消息添加和删除事件中。这相当于IMAP status命令中的UIDNEXT status项。
uidset Included with MessageExpires, MessageExpunges, MessageRead, MessageTrash, FlagsSet, and FlagsClear.
MessageExpires、MessageExpunges、MessageRead、MessageTrash、FlagsSet和FlagsClear附带的uidset。
This includes the set of IMAP UIDs referenced.
这包括引用的IMAP UID集。
uri Included with all notifications. A reference to the IMAP server, a mailbox, or a message.
uri包含在所有通知中。对IMAP服务器、邮箱或邮件的引用。
Typically an IMAP URL. This can include the name of the server used to access the mailbox/message, the mailbox name, the UIDVALIDITY of the mailbox, and the UID of a specific message.
通常是一个IMAP URL。这可能包括用于访问邮箱/邮件的服务器名称、邮箱名称、邮箱的UID有效性以及特定邮件的UID。
user Included with all events generated by message access protocols.
包含在消息访问协议生成的所有事件中的用户。
This is the authorization identifier used when the client connected to the access protocol that triggered the event. Some protocols (for example, many SASL mechanisms) distinguish between authorization and authentication identifiers. For events associated with a mailbox, this may be different from the owner of the mailbox specified in the IMAP URL.
这是客户端连接到触发事件的访问协议时使用的授权标识符。一些协议（例如，许多SASL机制）区分授权标识符和身份验证标识符。对于与邮箱关联的事件，这可能与IMAP URL中指定的邮箱所有者不同。
The IANA has created a new registry for "Internet Message Store Events" that contains two sub-registries: event names and event parameters. For both event names and event parameters, entries that do not start with "vnd." are added by the IETF and are intended for interoperable use. Entries that start with "vnd." are intended for private use by one or more parties and are allocated to avoid collisions.
IANA为“Internet消息存储事件”创建了一个新的注册表，其中包含两个子注册表：事件名称和事件参数。对于事件名称和事件参数，IETF会添加不以“vnd.”开头的条目，以供互操作使用。以“vnd.”开头的条目旨在供一方或多方私人使用，并进行分配以避免冲突。
The initial values are contained in this document.
初始值包含在本文档中。
Using IANA Considerations [RFC5226] terminology, entries that do not start with "vnd." are allocated by IETF Consensus, while those starting with "vnd." are allocated First Come First Served.
使用IANA注意事项[RFC5226]术语，不以“vnd.”开头的条目由IETF协商一致分配，而以“vnd.”开头的条目分配先到先得。
Notifications can produce a large amount of traffic and expose sensitive information. When notification mechanisms are used to maintain state between different entities, the ability to corrupt or manipulate notification messages could enable an attacker to modulate the state of these entities. For example, if an attacker were able to modify notifications sent from a message store to an auditing server, he could modify the "user" and "messageContent" parameters in MessageNew notifications to create false audit log entries.
通知可能会产生大量流量并暴露敏感信息。当通知机制用于维护不同实体之间的状态时，破坏或操纵通知消息的能力可能使攻击者能够调整这些实体的状态。例如，如果攻击者能够修改从消息存储发送到审核服务器的通知，他可以修改MessageNew notifications中的“user”和“messageContent”参数，以创建错误的审核日志条目。
A competent transfer protocol for notifications must consider authentication, authorization, privacy, and message integrity, as well as denial-of-service issues. While the IETF has adequate tools and experience to address these issues for mechanisms that involve only one TCP connection, notification or publish/subscribe protocols that are more sophisticated than a single end-to-end TCP connection will need to pay extra attention to these issues and carefully balance requirements to successfully deploy a system with security and privacy considerations.
通知的有效传输协议必须考虑认证、授权、隐私和消息完整性以及拒绝服务问题。虽然IETF拥有足够的工具和经验来解决仅涉及一个TCP连接的机制的这些问题，比单个端到端TCP连接更复杂的通知或发布/订阅协议将需要特别注意这些问题，并仔细平衡要求，以便成功部署具有安全和隐私考虑的系统。
Alexey Melnikov, Arnt Gulbrandsen, and Zoltan Ordogh have reviewed and offered improvements to this document. Richard Barnes did a nice review during Last Call.
Alexey Melnikov、Arnt Gulbrandsen和Zoltan Ordogh对本文件进行了审查并提出了改进意见。理查德·巴恩斯在上次通话中做了一次很好的回顾。
[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月。
[RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", RFC 3501, March 2003.
[RFC3501]Crispin，M.，“互联网消息访问协议-版本4rev1”，RFC 35012003年3月。
[RFC5092] Melnikov, A. and C. Newman, "IMAP URL Scheme", RFC 5092, November 2007.
[RFC5092]Melnikov，A.和C.Newman，“IMAP URL方案”，RFC 5092，2007年11月。
[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月。
[RFC1939] Myers, J. and M. Rose, "Post Office Protocol - Version 3", STD 53, RFC 1939, May 1996.
[RFC1939]迈尔斯，J.和M.罗斯，“邮局协议-第3版”，STD 53，RFC 1939，1996年5月。
[RFC2177] Leiba, B., "IMAP4 IDLE command", RFC 2177, June 1997.
[RFC2177]Leiba，B.，“IMAP4空闲命令”，RFC2177，1997年6月。
[RFC2447] Dawson, F., Mansour, S., and S. Silverberg, "iCalendar Message-Based Interoperability Protocol (iMIP)", RFC 2447, November 1998.
[RFC2447]Dawson，F.，Mansour，S.和S.Silverberg，“iCalendar基于消息的互操作性协议（iMIP）”，RFC 2447，1998年11月。
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, July 2002.
[RFC3339]Klyne，G.，Ed.和C.Newman，“互联网上的日期和时间：时间戳”，RFC33392002年7月。
[RFC3458] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message Context for Internet Mail", RFC 3458, January 2003.
[RFC3458]Burger，E.，Candell，E.，Eliot，C.，和G.Klyne，“互联网邮件的消息上下文”，RFC 3458，2003年1月。
[RFC4146] Gellens, R., "Simple New Mail Notification", RFC 4146, August 2005.
[RFC4146]Gellens，R.，“简单的新邮件通知”，RFC4146，2005年8月。
[RFC4314] Melnikov, A., "IMAP4 Access Control List (ACL) Extension", RFC 4314, December 2005.
[RFC4314]Melnikov，A.，“IMAP4访问控制列表（ACL）扩展”，RFC 4314，2005年12月。
[RFC4422] Melnikov, A. and K. Zeilenga, "Simple Authentication and Security Layer (SASL)", RFC 4422, June 2006.
[RFC4422]Melnikov，A.和K.Zeilenga，“简单身份验证和安全层（SASL）”，RFC 4422，2006年6月。
[RFC4467] Crispin, M., "Internet Message Access Protocol (IMAP) - URLAUTH Extension", RFC 4467, May 2006.
[RFC4467]Crispin，M.，“互联网消息访问协议（IMAP）-URLAUTH扩展”，RFC 4467，2006年5月。
[RFC4551] Melnikov, A. and S. Hole, "IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization", RFC 4551, June 2006.
[RFC4551]Melnikov，A.和S.Hole，“条件存储操作或快速标志更改再同步的IMAP扩展”，RFC 45512006年6月。
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, October 2008.
[RFC5322]Resnick，P.，Ed.“互联网信息格式”，RFC5222008年10月。
This document specifies core functionality based on events that are believed to be well understood, have known use cases, and are implemented by at least one deployed real-world Internet message store. (A few events are exceptions to the last test only: FlagsSet, FlagsClear, MailboxCreate, MailboxDelete, MailboxRename, MailboxSubscribe, and MailboxUnSubscribe.)
本文档指定了基于事件的核心功能，这些事件被认为是众所周知的，具有已知的用例，并且至少由一个部署的真实Internet消息存储实现。（只有少数事件是上一次测试的例外：FlagsSet、FlagsClear、MailboxCreate、MailboxDelete、MailboxRename、MailboxSubscribe和MailboxUnSubscribe。）
Some events have been suggested but are postponed to future extensions because they do not meet this criteria. These events include messages that have been moved to archive storage and may require extra time to access, quota by message context, authentication failure, user mail account disabled, annotations, and mailbox ACL or metadata change. The descriptions of several events note additional parameters that are likely candidates for future inclusion. See Section 6 for how the list of events and parameters can be extended.
已经建议了一些活动，但由于不符合此标准，因此推迟到以后的延期。这些事件包括已移动到存档存储且可能需要额外时间访问的邮件、邮件上下文配额、身份验证失败、禁用用户邮件帐户、批注以及邮箱ACL或元数据更改。几个事件的描述说明了未来可能包含的其他参数。有关如何扩展事件和参数列表，请参见第6节。
In order to narrow the scope of this document to something that can be completed, only events generated from the message store (by a message access module, administrative module, or message delivery agent) are considered. A complete mail system is normally linked with an identity system that would also publish events of interest to a message store event subscriber. Events of interest include account created/deleted/disabled and password changed/expired.
为了将本文档的范围缩小到可以完成的范围，只考虑从消息存储（由消息访问模块、管理模块或消息传递代理）生成的事件。一个完整的邮件系统通常与一个标识系统链接，该标识系统还将向消息存储事件订阅者发布感兴趣的事件。感兴趣的事件包括创建/删除/禁用帐户和更改/过期密码。
Authors' Addresses
作者地址
Randall Gellens QUALCOMM Incorporated 5775 Morehouse Drive San Diego, CA 92651 USA
美国加利福尼亚州圣地亚哥Morehouse大道5775号兰德尔盖伦高通公司，邮编92651
Phone:
EMail: rg+ietf@qualcomm.com
Phone:
EMail: rg+ietf@qualcomm.com
Chris Newman Sun Microsystems 800 Royal Oaks Monrovia, CA 91016-6347 USA
克里斯纽曼太阳微系统800皇家橡树园蒙罗维亚，加利福尼亚州91016-6347美国
Phone: EMail: chris.newman@sun.com
电话：电子邮件：克里斯。newman@sun.com