Network Working Group M. Gahrns
Request for Comments: 2342 Microsoft
Category: Standards Track C. Newman
Innosoft
May 1998
Network Working Group M. Gahrns
Request for Comments: 2342 Microsoft
Category: Standards Track C. Newman
Innosoft
May 1998
IMAP4 Namespace
IMAP4命名空间
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) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
IMAP4 [RFC-2060] does not define a default server namespace. As a result, two common namespace models have evolved:
IMAP4[RFC-2060]未定义默认服务器命名空间。因此，出现了两种常见的命名空间模型：
The "Personal Mailbox" model, in which the default namespace that is presented consists of only the user's personal mailboxes. To access shared mailboxes, the user must use an escape mechanism to reach another namespace.
“个人邮箱”模型，其中显示的默认命名空间仅由用户的个人邮箱组成。要访问共享邮箱，用户必须使用转义机制访问另一个命名空间。
The "Complete Hierarchy" model, in which the default namespace that is presented includes the user's personal mailboxes along with any other mailboxes they have access to.
“完整层次结构”模型，其中显示的默认命名空间包括用户的个人邮箱以及他们可以访问的任何其他邮箱。
These two models, create difficulties for certain client operations. This document defines a NAMESPACE command that allows a client to discover the prefixes of namespaces used by a server for personal mailboxes, other users' mailboxes, and shared mailboxes. This allows a client to avoid much of the manual user configuration that is now necessary when mixing and matching IMAP4 clients and servers.
这两种模式为某些客户端操作带来了困难。本文档定义了一个NAMESPACE命令，该命令允许客户端发现服务器用于个人邮箱、其他用户邮箱和共享邮箱的命名空间前缀。这使得客户机可以避免在混合和匹配IMAP4客户机和服务器时所需的大量手动用户配置。
In examples, "C:" and "S:" indicate lines sent by the client and server respectively. If such lines are wrapped without a new "C:" or "S:" label, then the wrapping is for editorial clarity and is not part of the command.
在示例中，“C:”和“S:”分别表示客户端和服务器发送的行。如果这些行没有新的“C:”或“S:”标签而被换行，则换行是为了编辑清晰，而不是命令的一部分。
Personal Namespace: A namespace that the server considers within the personal scope of the authenticated user on a particular connection. Typically, only the authenticated user has access to mailboxes in their Personal Namespace. It is the part of the namespace that belongs to the user that is allocated for mailboxes. If an INBOX exists for a user, it MUST appear within the user's personal namespace. In the typical case, there SHOULD be only one Personal Namespace on a server.
个人名称空间：服务器在特定连接上已验证用户的个人范围内考虑的名称空间。通常，只有经过身份验证的用户才能访问其个人命名空间中的邮箱。它是为邮箱分配的属于用户的命名空间的一部分。如果存在用户的收件箱，则它必须出现在用户的个人命名空间中。在典型情况下，服务器上应该只有一个个人名称空间。
Other Users' Namespace: A namespace that consists of mailboxes from the Personal Namespaces of other users. To access mailboxes in the Other Users' Namespace, the currently authenticated user MUST be explicitly granted access rights. For example, it is common for a manager to grant to their secretary access rights to their mailbox. In the typical case, there SHOULD be only one Other Users' Namespace on a server.
其他用户的命名空间：由来自其他用户的个人命名空间的邮箱组成的命名空间。要访问其他用户命名空间中的邮箱，必须显式授予当前经过身份验证的用户访问权限。例如，经理通常会向其秘书授予对其邮箱的访问权限。在典型情况下，服务器上应该只有一个其他用户的命名空间。
Shared Namespace: A namespace that consists of mailboxes that are intended to be shared amongst users and do not exist within a user's Personal Namespace.
共享名称空间：由用户之间共享的邮箱组成的名称空间，不存在于用户的个人名称空间中。
The namespaces a server uses MAY differ on a per-user basis.
服务器使用的名称空间可能因每个用户而异。
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC-2119]中所述进行解释。
Clients often attempt to create mailboxes for such purposes as maintaining a record of sent messages (e.g. "Sent Mail") or temporarily saving messages being composed (e.g. "Drafts"). For these clients to inter-operate correctly with the variety of IMAP4 servers available, the user must enter the prefix of the Personal Namespace used by the server. Using the NAMESPACE command, a client is able to automatically discover this prefix without manual user configuration.
客户端通常会尝试创建邮箱，以便维护已发送邮件的记录（例如“已发送邮件”）或临时保存正在编写的邮件（例如“草稿”）。要使这些客户端与各种可用的IMAP4服务器正确交互，用户必须输入服务器使用的个人名称空间的前缀。使用NAMESPACE命令，客户端能够自动发现此前缀，而无需手动用户配置。
In addition, users are often required to manually enter the prefixes of various namespaces in order to view the mailboxes located there. For example, they might be required to enter the prefix of #shared to view the shared mailboxes namespace. The NAMESPACE command allows a client to automatically discover the namespaces that are available on a server. This allows a client to present the available namespaces to the user in what ever manner it deems appropriate. For example, a
此外，用户通常需要手动输入各种名称空间的前缀，以便查看位于其中的邮箱。例如，他们可能需要输入前缀#shared来查看共享邮箱名称空间。NAMESPACE命令允许客户端自动发现服务器上可用的名称空间。这允许客户端以其认为合适的方式向用户呈现可用的名称空间。例如，一个
client could choose to initially display only personal mailboxes, or it may choose to display the complete list of mailboxes available, and initially position the user at the root of their Personal Namespace.
客户端可以选择最初仅显示个人邮箱，也可以选择显示可用邮箱的完整列表，并将用户最初定位在其个人命名空间的根位置。
A server MAY choose to make available to the NAMESPACE command only a subset of the complete set of namespaces the server supports. To provide the ability to access these namespaces, a client SHOULD allow the user the ability to manually enter a namespace prefix.
服务器可以选择仅向NAMESPACE命令提供服务器支持的完整名称空间集的子集。要提供访问这些名称空间的能力，客户端应允许用户手动输入名称空间前缀。
IMAP4 servers that support this extension MUST list the keyword NAMESPACE in their CAPABILITY response.
支持此扩展的IMAP4服务器必须在其功能响应中列出关键字命名空间。
The NAMESPACE command is valid in the Authenticated and Selected state.
NAMESPACE命令在已验证和选定状态下有效。
Arguments: none
论点：无
Response: an untagged NAMESPACE response that contains the prefix and hierarchy delimiter to the server's Personal Namespace(s), Other Users' Namespace(s), and Shared Namespace(s) that the server wishes to expose. The response will contain a NIL for any namespace class that is not available. Namespace_Response_Extensions MAY be included in the response. Namespace_Response_Extensions which are not on the IETF standards track, MUST be prefixed with an "X-".
Response：一个未标记的命名空间响应，其中包含服务器希望公开的个人命名空间、其他用户命名空间和共享命名空间的前缀和层次分隔符。对于任何不可用的命名空间类，响应将包含NIL。响应中可能包含名称空间\响应\扩展。不在IETF标准轨道上的名称空间\响应\扩展必须以“X-”作为前缀。
Result: OK - Command completed
NO - Error: Can't complete command
BAD - argument invalid
Result: OK - Command completed
NO - Error: Can't complete command
BAD - argument invalid
Example 5.1:
===========
Example 5.1:
===========
< A server that supports a single personal namespace. No leading prefix is used on personal mailboxes and "/" is the hierarchy delimiter.>
<支持单个个人命名空间的服务器。个人邮箱不使用前导前缀，“/”是层次结构分隔符。>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) NIL NIL
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) NIL NIL
S: A001 OK NAMESPACE command completed
Example 5.2:
===========
Example 5.2:
===========
< A user logged on anonymously to a server. No personal mailboxes are associated with the anonymous user and the user does not have access to the Other Users' Namespace. No prefix is required to access shared mailboxes and the hierarchy delimiter is "." >
<以匿名方式登录到服务器的用户。没有与匿名用户关联的个人邮箱，并且该用户无权访问其他用户的命名空间。访问共享邮箱不需要前缀，层次结构分隔符为“.”>
C: A001 NAMESPACE
S: * NAMESPACE NIL NIL (("" "."))
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE NIL NIL (("" "."))
S: A001 OK NAMESPACE command completed
Example 5.3:
===========
Example 5.3:
===========
< A server that contains a Personal Namespace and a single Shared Namespace. >
<包含个人命名空间和单个共享命名空间的服务器。>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) NIL (("Public Folders/" "/"))
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) NIL (("Public Folders/" "/"))
S: A001 OK NAMESPACE command completed
Example 5.4:
===========
Example 5.4:
===========
< A server that contains a Personal Namespace, Other Users' Namespace and multiple Shared Namespaces. Note that the hierarchy delimiter used within each namespace can be different. >
<包含个人命名空间、其他用户命名空间和多个共享命名空间的服务器。请注意，每个名称空间中使用的层次分隔符可能不同。>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("~" "/")) (("#shared/" "/")
("#public/" "/")("#ftp/" "/")("#news." "."))
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("~" "/")) (("#shared/" "/")
("#public/" "/")("#ftp/" "/")("#news." "."))
S: A001 OK NAMESPACE command completed
The prefix string allows a client to do things such as automatically creating personal mailboxes or LISTing all available mailboxes within a namespace.
前缀字符串允许客户端执行一些操作，例如自动创建个人邮箱或列出命名空间中的所有可用邮箱。
Example 5.5:
===========
Example 5.5:
===========
< A server that supports only the Personal Namespace, with a leading prefix of INBOX to personal mailboxes and a hierarchy delimiter of ".">
<仅支持个人名称空间的服务器，其前缀为INBOX to Personal mailboxes，层次结构分隔符为“.”>
C: A001 NAMESPACE
S: * NAMESPACE (("INBOX." ".")) NIL NIL
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("INBOX." ".")) NIL NIL
S: A001 OK NAMESPACE command completed
< Automatically create a mailbox to store sent items.>
<自动创建邮箱以存储发送的邮件。>
C: A002 CREATE "INBOX.Sent Mail"
S: A002 OK CREATE command completed
C: A002 CREATE "INBOX.Sent Mail"
S: A002 OK CREATE command completed
Although typically a server will support only a single Personal Namespace, and a single Other User's Namespace, circumstances exist where there MAY be multiples of these, and a client MUST be prepared for them. If a client is configured such that it is required to create a certain mailbox, there can be circumstances where it is unclear which Personal Namespaces it should create the mailbox in. In these situations a client SHOULD let the user select which namespaces to create the mailbox in.
虽然服务器通常只支持单个个人名称空间和单个其他用户的名称空间，但在某些情况下可能会有多个名称空间，并且必须为它们准备一个客户端。如果客户机被配置为需要创建特定邮箱，则在某些情况下，可能不清楚应该在哪些个人名称空间中创建邮箱。在这些情况下，客户机应该让用户选择在哪些名称空间中创建邮箱。
Example 5.6:
===========
Example 5.6:
===========
< In this example, a server supports 2 Personal Namespaces. In addition to the regular Personal Namespace, the user has an additional personal namespace to allow access to mailboxes in an MH format mailstore. >
<在本例中，服务器支持2个个人名称空间。除了常规的个人名称空间外，用户还有一个额外的个人名称空间，允许访问MH格式邮件存储中的邮箱。>
< The client is configured to save a copy of all mail sent by the user into a mailbox called 'Sent Mail'. Furthermore, after a message is deleted from a mailbox, the client is configured to move that message to a mailbox called 'Deleted Items'.>
<客户端配置为将用户发送的所有邮件的副本保存到名为“已发送邮件”的邮箱中。此外，从邮箱中删除邮件后，客户端被配置为将该邮件移动到名为“已删除邮件”的邮箱中。>
< Note that this example demonstrates how some extension flags can be passed to further describe the #mh namespace. >
<注意，这个示例演示了如何传递一些扩展标志来进一步描述#mh名称空间。>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")("#mh/" "/" "X-PARAM" ("FLAG1" "FLAG2")))
NIL NIL
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")("#mh/" "/" "X-PARAM" ("FLAG1" "FLAG2")))
NIL NIL
S: A001 OK NAMESPACE command completed
< It is desired to keep only one copy of sent mail. It is unclear which Personal Namespace the client should use to create the 'Sent Mail' mailbox. The user is prompted to select a namespace and only one 'Sent Mail' mailbox is created. >
<希望只保留一份已发送邮件的副本。不清楚客户端应使用哪个个人命名空间来创建“已发送邮件”邮箱。系统将提示用户选择名称空间，并且只创建一个“已发送邮件”邮箱。>
C: A002 CREATE "Sent Mail"
S: A002 OK CREATE command completed
C: A002 CREATE "Sent Mail"
S: A002 OK CREATE command completed
< The client is designed so that it keeps two 'Deleted Items' mailboxes, one for each namespace. >
<客户端设计为保留两个“已删除邮件”邮箱，每个名称空间一个。>
C: A003 CREATE "Delete Items"
S: A003 OK CREATE command completed
C: A003 CREATE "Delete Items"
S: A003 OK CREATE command completed
C: A004 CREATE "#mh/Deleted Items"
S: A004 OK CREATE command completed
C: A004 CREATE "#mh/Deleted Items"
S: A004 OK CREATE command completed
The next level of hierarchy following the Other Users' Namespace prefix SHOULD consist of <username>, where <username> is a user name as per the IMAP4 LOGIN or AUTHENTICATE command.
其他用户名称空间前缀后面的下一级层次结构应由<username>组成，其中<username>是根据IMAP4 LOGIN或AUTHENTICATE命令的用户名。
A client can construct a LIST command by appending a "%" to the Other Users' Namespace prefix to discover the Personal Namespaces of other users that are available to the currently authenticated user.
客户端可以通过在其他用户的名称空间前缀中添加“%”来构造列表命令，以发现当前已验证用户可用的其他用户的个人名称空间。
In response to such a LIST command, a server SHOULD NOT return user names that have not granted access to their personal mailboxes to the user in question.
作为对此类LIST命令的响应，服务器不应将未授予相关用户访问其个人邮箱权限的用户名返回给该用户。
A server MAY return a LIST response containing only the names of users that have explicitly granted access to the user in question.
服务器可能会返回一个列表响应，其中只包含明确授予相关用户访问权限的用户的姓名。
Alternatively, a server MAY return NO to such a LIST command, requiring that a user name be included with the Other Users' Namespace prefix before listing any other user's mailboxes.
或者，服务器可以对这样的LIST命令返回NO，要求在列出任何其他用户的邮箱之前，将用户名包括在其他用户的名称空间前缀中。
Example 5.7:
===========
Example 5.7:
===========
< A server that supports providing a list of other user's mailboxes that are accessible to the currently logged on user. >
<支持提供当前登录用户可访问的其他用户邮箱列表的服务器。>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("Other Users/" "/")) NIL
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("Other Users/" "/")) NIL
S: A001 OK NAMESPACE command completed
C: A002 LIST "" "Other Users/%"
S: * LIST () "/" "Other Users/Mike"
S: * LIST () "/" "Other Users/Karen"
S: * LIST () "/" "Other Users/Matthew"
S: * LIST () "/" "Other Users/Tesa"
S: A002 OK LIST command completed
C: A002 LIST "" "Other Users/%"
S: * LIST () "/" "Other Users/Mike"
S: * LIST () "/" "Other Users/Karen"
S: * LIST () "/" "Other Users/Matthew"
S: * LIST () "/" "Other Users/Tesa"
S: A002 OK LIST command completed
Example 5.8:
===========
Example 5.8:
===========
< A server that does not support providing a list of other user's mailboxes that are accessible to the currently logged on user. The mailboxes are listable if the client includes the name of the other user with the Other Users' Namespace prefix. >
<不支持提供当前登录用户可访问的其他用户邮箱列表的服务器。如果客户端包含具有其他用户名称空间前缀的其他用户的名称，则邮箱是可列出的。>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("#Users/" "/")) NIL
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("#Users/" "/")) NIL
S: A001 OK NAMESPACE command completed
< In this example, the currently logged on user has access to the Personal Namespace of user Mike, but the server chose to suppress this information in the LIST response. However, by appending the user name Mike (received through user input) to the Other Users' Namespace prefix, the client is able to get a listing of the personal mailboxes of user Mike. >
<在本例中，当前登录的用户可以访问用户Mike的个人名称空间，但服务器选择在列表响应中抑制此信息。但是，通过将用户名Mike（通过用户输入接收）附加到其他用户的名称空间前缀，客户端可以获得用户Mike的个人邮箱列表。>
C: A002 LIST "" "#Users/%"
S: A002 NO The requested item could not be found.
C: A002 LIST "" "#Users/%"
S: A002 NO The requested item could not be found.
C: A003 LIST "" "#Users/Mike/%"
S: * LIST () "/" "#Users/Mike/INBOX"
S: * LIST () "/" "#Users/Mike/Foo"
S: A003 OK LIST command completed.
C: A003 LIST "" "#Users/Mike/%"
S: * LIST () "/" "#Users/Mike/INBOX"
S: * LIST () "/" "#Users/Mike/Foo"
S: A003 OK LIST command completed.
A prefix string might not contain a hierarchy delimiter, because in some cases it is not needed as part of the prefix.
前缀字符串可能不包含层次分隔符，因为在某些情况下，它不需要作为前缀的一部分。
Example 5.9:
===========
Example 5.9:
===========
< A server that allows access to the Other Users' Namespace by
prefixing the others' mailboxes with a '~' followed by <username>,
where <username> is a user name as per the IMAP4 LOGIN or
AUTHENTICATE command.>
< A server that allows access to the Other Users' Namespace by
prefixing the others' mailboxes with a '~' followed by <username>,
where <username> is a user name as per the IMAP4 LOGIN or
AUTHENTICATE command.>
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("~" "/")) NIL
S: A001 OK NAMESPACE command completed
C: A001 NAMESPACE
S: * NAMESPACE (("" "/")) (("~" "/")) NIL
S: A001 OK NAMESPACE command completed
< List the mailboxes for user mark >
<列出用户标记的邮箱>
C: A002 LIST "" "~mark/%"
S: * LIST () "/" "~mark/INBOX"
S: * LIST () "/" "~mark/foo"
S: A002 OK LIST command completed
C: A002 LIST "" "~mark/%"
S: * LIST () "/" "~mark/INBOX"
S: * LIST () "/" "~mark/foo"
S: A002 OK LIST command completed
Historical convention has been to start all namespaces with the "#" character. Namespaces that include the "#" character are not IMAP URL [IMAP-URL] friendly requiring the "#" character to be represented as %23 when within URLs. As such, server implementers MAY instead consider using namespace prefixes that do not contain the "#" character.
历史惯例是以“#”字符开始所有名称空间。包含“#”字符的命名空间对IMAP URL[IMAP-URL]不友好，在URL中需要将“#”字符表示为%23。因此，服务器实现者可能会考虑使用名称空间前缀，这些命名空间前缀不包含“γ”字符。
The following syntax specification uses the augmented Backus-Naur Form (BNF) as described in [ABNF].
以下语法规范使用[ABNF]中所述的增广巴科斯诺尔形式（BNF）。
atom = <atom>
; <atom> as defined in [RFC-2060]
atom = <atom>
; <atom> as defined in [RFC-2060]
Namespace = nil / "(" 1*( "(" string SP (<"> QUOTED_CHAR <"> /
nil) *(Namespace_Response_Extension) ")" ) ")"
Namespace = nil / "(" 1*( "(" string SP (<"> QUOTED_CHAR <"> /
nil) *(Namespace_Response_Extension) ")" ) ")"
Namespace_Command = "NAMESPACE"
Namespace_Command = "NAMESPACE"
Namespace_Response_Extension = SP string SP "(" string *(SP string) ")"
名称空间\响应\扩展名=SP string SP”（“string*（SP string）”）
Namespace_Response = "*" SP "NAMESPACE" SP Namespace SP Namespace SP Namespace
Namespace_Response=“*”SP“Namespace”SP Namespace SP Namespace SP Namespace
; The first Namespace is the Personal Namespace(s)
; The second Namespace is the Other Users' Namespace(s)
; The third Namespace is the Shared Namespace(s)
; The first Namespace is the Personal Namespace(s)
; The second Namespace is the Other Users' Namespace(s)
; The third Namespace is the Shared Namespace(s)
nil = <nil>
; <nil> as defined in [RFC-2060]
nil = <nil>
; <nil> as defined in [RFC-2060]
QUOTED_CHAR = <QUOTED_CHAR>
; <QUOTED_CHAR> as defined in [RFC-2060]
QUOTED_CHAR = <QUOTED_CHAR>
; <QUOTED_CHAR> as defined in [RFC-2060]
string = <string>
; <string> as defined in [RFC-2060]
; Note that the namespace prefix is to a mailbox and following
; IMAP4 convention, any international string in the NAMESPACE
; response MUST be of modified UTF-7 format as described in
; [RFC-2060].
string = <string>
; <string> as defined in [RFC-2060]
; Note that the namespace prefix is to a mailbox and following
; IMAP4 convention, any international string in the NAMESPACE
; response MUST be of modified UTF-7 format as described in
; [RFC-2060].
In response to a LIST command containing an argument of the Other Users' Namespace prefix, a server SHOULD NOT list users that have not granted list access to their personal mailboxes to the currently authenticated user. Providing such a list, could compromise security by potentially disclosing confidential information of who is located on the server, or providing a starting point of a list of user accounts to attack.
作为对包含其他用户名称空间前缀参数的LIST命令的响应，服务器不应列出尚未向当前经过身份验证的用户授予对其个人邮箱的LIST访问权限的用户。提供这样的列表，可能会泄露服务器上用户的机密信息，或提供要攻击的用户帐户列表的起点，从而危及安全。
[RFC-2060], Crispin, M., "Internet Message Access Protocol Version 4rev1", RFC 2060, December 1996.
[RFC-2060]，Crispin，M.，“互联网消息访问协议版本4rev1”，RFC 2060，1996年12月。
[RFC-2119], Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2119]，Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[ABNF] Crocker, D., Editor, and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[ABNF]Crocker，D.，编辑和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
[IMAP-URL], Newman, C., "IMAP URL Scheme", RFC 2192, September 1997.
[IMAP-URL]，纽曼，C.，“IMAP URL方案”，RFC 2192192191997年9月。
Many people have participated in the discussion of IMAP namespaces on the IMAP mailing list. In particular, the authors would like to thank Mark Crispin for many of the concepts relating to the Personal Namespace and accessing the Personal Namespace of other users, Steve Hole for summarizing the two namespace models, John Myers and Jack De Winter for their work in a preceding effort trying to define a standardized personal namespace, and Larry Osterman for his review and collaboration on this document.
许多人参与了关于IMAP邮件列表上IMAP名称空间的讨论。特别是，作者要感谢Mark Crispin提出了许多与个人名称空间和访问其他用户的个人名称空间相关的概念，感谢Steve Hole总结了两个名称空间模型，感谢John Myers和Jack De Winter在之前试图定义标准化个人名称空间的工作中所做的工作，以及拉里·奥斯特曼对本文件的审查和合作。
Mike Gahrns Microsoft One Microsoft Way Redmond, WA, 98072, USA
Mike Gahrns美国华盛顿州雷德蒙德市微软一号，邮编：98072
Phone: (425) 936-9833 EMail: mikega@microsoft.com
电话：（425）936-9833电子邮件：mikega@microsoft.com
Chris Newman Innosoft International, Inc. 1050 East Garvey Ave. South West Covina, CA, 91790, USA
Chris Newman Innosoft International，Inc.美国加利福尼亚州西南科维纳东加维大道1050号，邮编：91790
EMail: chris.newman@innosoft.com
EMail: chris.newman@innosoft.com
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。