Network Working Group G. Vaudreuil
Request for Comments: 2421 Lucent Technologies
Obsoletes: 1911 G. Parsons
Category: Standards Track Northern Telecom
September 1998
Network Working Group G. Vaudreuil
Request for Comments: 2421 Lucent Technologies
Obsoletes: 1911 G. Parsons
Category: Standards Track Northern Telecom
September 1998
Voice Profile for Internet Mail - version 2
Internet邮件的语音配置文件-版本2
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年）。版权所有。
Overview
概述
This document profiles Internet mail for voice messaging. It obsoletes RFC 1911 which describes version 1 of the profile. A list of changes from that document are noted in Appendix F. As well, Appendix A summarizes the protocol profiles of this version of VPIM.
本文档介绍用于语音消息的Internet邮件。它淘汰了描述概要文件版本1的RFC 1911。该文件的变更列表见附录F。附录A也总结了该版本VPIM的协议概要。
Please send comments on this document to the EMA VPIM Work Group
mailing list: <vpim-l@ema.org>
Please send comments on this document to the EMA VPIM Work Group
mailing list: <vpim-l@ema.org>
Working Group Summary
工作组摘要
This profile is not the product of an IETF working group, though several have reviewed the document. It is instead the product of the VPIM Work Group of the Electronic Messaging Association (EMA). This work group, which has representatives from most major voice mail vendors and several email vendors, has held several interoperability demonstrations between voice messaging vendors and is currently promoting VPIM trials and deployment.
该概要文件不是IETF工作组的产品，尽管有几个工作组已经审查了该文件。它是电子信息协会（EMA）VPIM工作组的产品。该工作组由大多数主要语音邮件供应商和多家电子邮件供应商的代表组成，已经在语音邮件供应商之间举行了几次互操作性演示，目前正在推动VPIM的试用和部署。
Table of Contents
目录
1. ABSTRACT .........................................................3
2. SCOPE ............................................................3
2.1 Voice Messaging System Limitations ............................3
2.2 Design Goals ..................................................4
3. PROTOCOL RESTRICTIONS ............................................5
4. VOICE MESSAGE INTERCHANGE FORMAT .................................6
4.1 Message Addressing Formats ....................................6
4.2 Message Header Fields .........................................9
4.3 Voice Message Content Types ..................................15
4.4 Other Message Content Types ..................................21
4.5 Forwarded Messages ...........................................23
4.6 Reply Messages ...............................................23
4.7 Notification Messages ........................................24
5. MESSAGE TRANSPORT PROTOCOL ......................................24
5.1 ESMTP Commands ...............................................25
5.2 ESMTP Keywords ...............................................27
5.3 ESMTP Parameters - MAIL FROM .................................28
5.4 ESMTP Parameters - RCPT TO ...................................29
5.5 ESMTP - SMTP Downgrading .....................................29
6. DIRECTORY ADDRESS RESOLUTION ....................................30
7. IMAP ............................................................30
8. MANAGEMENT PROTOCOLS ............................................30
8.1 Network Management ...........................................31
9. CONFORMANCE REQUIREMENTS ........................................31
10. SECURITY CONSIDERATIONS ........................................32
10.1 General Directive ...........................................32
10.2 Threats and Problems ........................................32
10.3 Security Techniques .........................................33
11. REFERENCES .....................................................33
12. ACKNOWLEDGMENTS ................................................36
13. AUTHORS' ADDRESSES .............................................36
14. APPENDIX A - VPIM REQUIREMENTS SUMMARY .........................37
15. APPENDIX B - EXAMPLE VOICE MESSAGES ............................45
16. APPENDIX C - EXAMPLE ERROR VOICE PROCESSING ERROR CODES ........50
17. APPENDIX D - EXAMPLE VOICE PROCESSING DISPOSITION TYPES ........51
18. APPENDIX E - IANA REGISTRATIONS ................................52
18.1 vCard EMAIL Type Definition for VPIM ........................52
18.2 Voice Content-Disposition Parameter Definition ..............52
19. APPENDIX F - CHANGE HISTORY: RFC 1911 TO THIS DOCUMENT .........54
20. FULL COPYRIGHT NOTICE ..........................................56
1. ABSTRACT .........................................................3
2. SCOPE ............................................................3
2.1 Voice Messaging System Limitations ............................3
2.2 Design Goals ..................................................4
3. PROTOCOL RESTRICTIONS ............................................5
4. VOICE MESSAGE INTERCHANGE FORMAT .................................6
4.1 Message Addressing Formats ....................................6
4.2 Message Header Fields .........................................9
4.3 Voice Message Content Types ..................................15
4.4 Other Message Content Types ..................................21
4.5 Forwarded Messages ...........................................23
4.6 Reply Messages ...............................................23
4.7 Notification Messages ........................................24
5. MESSAGE TRANSPORT PROTOCOL ......................................24
5.1 ESMTP Commands ...............................................25
5.2 ESMTP Keywords ...............................................27
5.3 ESMTP Parameters - MAIL FROM .................................28
5.4 ESMTP Parameters - RCPT TO ...................................29
5.5 ESMTP - SMTP Downgrading .....................................29
6. DIRECTORY ADDRESS RESOLUTION ....................................30
7. IMAP ............................................................30
8. MANAGEMENT PROTOCOLS ............................................30
8.1 Network Management ...........................................31
9. CONFORMANCE REQUIREMENTS ........................................31
10. SECURITY CONSIDERATIONS ........................................32
10.1 General Directive ...........................................32
10.2 Threats and Problems ........................................32
10.3 Security Techniques .........................................33
11. REFERENCES .....................................................33
12. ACKNOWLEDGMENTS ................................................36
13. AUTHORS' ADDRESSES .............................................36
14. APPENDIX A - VPIM REQUIREMENTS SUMMARY .........................37
15. APPENDIX B - EXAMPLE VOICE MESSAGES ............................45
16. APPENDIX C - EXAMPLE ERROR VOICE PROCESSING ERROR CODES ........50
17. APPENDIX D - EXAMPLE VOICE PROCESSING DISPOSITION TYPES ........51
18. APPENDIX E - IANA REGISTRATIONS ................................52
18.1 vCard EMAIL Type Definition for VPIM ........................52
18.2 Voice Content-Disposition Parameter Definition ..............52
19. APPENDIX F - CHANGE HISTORY: RFC 1911 TO THIS DOCUMENT .........54
20. FULL COPYRIGHT NOTICE ..........................................56
A class of special-purpose computers has evolved to provide voice messaging services. These machines generally interface to a telephone switch and provide call answering and voice messaging services. Traditionally, messages sent to a non-local machine are transported using analog networking protocols based on DTMF signaling and analog voice playback. As the demand for networking increases, there is a need for a standard high-quality digital protocol to connect these machines. The following document is a profile of the Internet standard MIME and ESMTP protocols for use as a digital voice messaging networking protocol. The profile is referred to as VPIM (Voice Profile for Internet Mail) in this document.
一类特殊用途的计算机已经发展为提供语音信息服务。这些机器通常与电话交换机连接，并提供电话应答和语音信息服务。传统上，发送到非本地机器的消息使用基于DTMF信令和模拟语音回放的模拟网络协议进行传输。随着网络需求的增加，需要一个标准的高质量数字协议来连接这些机器。以下文档是用作数字语音消息网络协议的Internet标准MIME和ESMTP协议的概要。此配置文件在本文档中称为VPIM（Internet邮件语音配置文件）。
This profile is based on earlier work in the Audio Message Interchange Specification (AMIS) group that defined a voice messaging protocol based on X.400 technology. This profile is intended to satisfy the user requirements statement from that earlier work with the industry standard ESMTP/MIME mail protocol infrastructures already used within corporate intranets. This second version of VPIM is based on implementation experience and obsoletes RFC 1911 which describes version 1 of the profile.
此配置文件基于音频消息交换规范（AMIS）组的早期工作，该组定义了基于X.400技术的语音消息协议。此配置文件旨在满足先前使用企业内部网中已使用的行业标准ESMTP/MIME邮件协议基础架构的用户需求声明。VPIM的第二个版本基于实施经验，淘汰了RFC 1911，RFC 1911描述了概要文件的第1个版本。
MIME is the Internet multipurpose, multimedia messaging standard. This document explicitly recognizes its capabilities and provides a mechanism for the exchange of various messaging technologies, primarily voice and facsimile.
MIME是Internet多用途的多媒体消息标准。本文件明确承认了其功能，并为各种消息传递技术（主要是语音和传真）的交换提供了一种机制。
This document specifies a restricted profile of the Internet multimedia messaging protocols for use between voice processing server platforms. These platforms have historically been special-purpose computers and often do not have the same facilities normally associated with a traditional Internet Email-capable computer. As a result, VPIM also specifies additional functionality as it is needed. This profile is intended to specify the minimum common set of features to allow interworking between compliant systems.
本文档规定了在语音处理服务器平台之间使用的Internet多媒体消息协议的受限配置文件。这些平台在历史上一直是专用计算机，通常没有与传统的支持Internet电子邮件的计算机相关的相同设施。因此，VPIM还根据需要指定其他功能。此配置文件旨在指定允许兼容系统之间互通的最小通用功能集。
The following are typical limitations of voice messaging platform which were considered in creating this baseline profile.
以下是创建此基线配置文件时考虑的语音消息平台的典型限制。
1) Text messages are not normally received and often cannot be easily displayed or viewed. They can often be processed only via text-to-speech or text-to-fax features not currently present in many of these machines.
1) 文本消息通常不会被接收，并且通常无法轻松显示或查看。它们通常只能通过文本到语音或文本到传真功能进行处理，而这些功能目前在这些机器中并不存在。
2) Voice mail machines usually act as an integrated Message Transfer Agent, Message Store and User Agent. There is no relaying of messages, and RFC 822 header fields may have limited use in the context of the limited messaging features currently deployed.
2) 语音邮件机通常充当集成的消息传输代理、消息存储和用户代理。没有消息中继，RFC 822头字段在当前部署的有限消息功能上下文中的使用可能有限。
3) Voice mail message stores are generally not capable of preserving the full semantics of an Internet message. As such, use of a voice mail machine for gatewaying is not supported. In particular, storage of recipient lists, "Received" lines, and "Message-ID" may be limited.
3) 语音邮件消息存储通常无法保留Internet消息的完整语义。因此，不支持使用语音邮件机进行网关连接。具体而言，收件人列表、“已接收”行和“消息ID”的存储可能受到限制。
4) Internet-style distribution/exploder mailing lists are not typically supported. Voice mail machines often implement only local alias lists, with error-to-sender and reply-to-sender behavior. Reply-all capabilities using a CC list are not generally available.
4) 通常不支持Internet样式的分发/爆炸邮件列表。语音邮件机器通常只实现本地别名列表，并具有错误发送和回复发送行为。使用CC列表回复所有功能通常不可用。
5) Error reports must be machine-parsable so that helpful responses can be voiced to users whose only access mechanism is a telephone.
5) 错误报告必须是机器可解析的，以便能够向只有电话访问机制的用户发出有用的响应。
6) The voice mail systems generally limit address entry to 16 or fewer numeric characters, and normally do not support alphanumeric mailbox names. Alpha characters are not generally used for mailbox identification as they cannot be easily entered from a telephone terminal.
6) 语音邮件系统通常将地址输入限制为16个或更少的数字字符，并且通常不支持字母数字邮箱名称。字母字符通常不用于邮箱识别，因为它们无法从电话终端轻松输入。
It is a goal of this profile to make as few restrictions and additions to the existing Internet mail protocols as possible while satisfying the requirements for interoperability with current generation voice messaging systems. This goal is motivated by the desire to increase the accessibility to digital messaging by enabling the use of proven existing networking software for rapid development.
本概要文件的目标是尽可能减少对现有Internet邮件协议的限制和添加，同时满足与当前一代语音消息系统的互操作性要求。这一目标的动机是希望通过使用经过验证的现有网络软件进行快速开发，从而提高数字信息的可访问性。
This specification is intended for use on a TCP/IP network; however, it is possible to use the SMTP protocol suite over other transport protocols. The necessary protocol parameters for such use is outside the scope of this document.
本规范适用于TCP/IP网络；但是，可以在其他传输协议上使用SMTP协议套件。此类使用的必要协议参数不在本文件范围内。
This profile is intended to be robust enough to be used in an environment, such as the global Internet with installed-base gateways which do not understand MIME, though typical use is expected to be within corporate intranets. Full functionality, such as reliable error messages and binary transport, will require careful selection of gateways (e.g., via MX records) to be used as VPIM forwarding agents. Nothing in this document precludes use of general purpose MIME email packages to read and compose VPIM messages. While no
此配置文件旨在足够健壮，以便在环境中使用，例如安装了不理解MIME的基本网关的全球互联网，尽管典型的使用预期是在公司内部网中。完整的功能，如可靠的错误消息和二进制传输，需要仔细选择用作VPIM转发代理的网关（例如，通过MX记录）。本文档中的任何内容都不排除使用通用MIME电子邮件包来阅读和撰写VPIM消息。而不是
special configuration is required to receive VPIM compliant messages, some may be required to originate compliant structures.
接收VPIM兼容消息需要特殊配置，有些可能需要创建兼容结构。
It is expected that a VPIM messaging system will be managed by a system administrator who can perform TCP/IP network configuration. When using facsimile or multiple voice encodings, it is suggested that the system administrator maintain a list of the capabilities of the networked mail machines to reduce the sending of undeliverable messages due to lack of feature support. Configuration, implementation and management of these directory listing capabilities are local matters.
VPIM消息传递系统预计将由能够执行TCP/IP网络配置的系统管理员管理。当使用传真或多种语音编码时，建议系统管理员维护联网邮件机的功能列表，以减少由于缺乏功能支持而无法发送的邮件。这些目录列表功能的配置、实现和管理是本地事务。
This protocol does not limit the number of recipients per message. Where possible, server implementations should not restrict the number of recipients in a single message. It is recognized that no implementation supports unlimited recipients, and that the number of supported recipients may be quite low.
此协议不限制每条邮件的收件人数量。在可能的情况下，服务器实现不应限制单个消息中的收件人数量。人们认识到，没有任何实现支持无限的收件人，而且受支持的收件人数量可能非常少。
This protocol does not limit the maximum message length. Implementers should understand that some machines will be unable to accept excessively long messages. A mechanism is defined in the RFC 1425 SMTP service extensions to declare the maximum message size supported.
此协议不限制最大消息长度。实现者应该理解，有些机器将无法接受过长的消息。RFC 1425 SMTP服务扩展中定义了一种机制，用于声明支持的最大邮件大小。
The message size indicated in the ESMTP SIZE parameter is in bytes, not minutes or seconds. The number of bytes varies by voice encoding format and includes the MIME wrapper overhead. If the length must be known before sending, an approximate translation into minutes or seconds can be performed if the voice encoding is known.
ESMTP size参数中指示的消息大小以字节为单位，而不是以分钟或秒为单位。字节数因语音编码格式而异，包括MIME包装开销。如果发送前必须知道长度，如果已知语音编码，则可以执行分或秒的近似翻译。
The following sections describe the restrictions and additions to Internet mail protocols that are required to be compliant with this VPIM v2 profile. Though various SMTP, ESMTP and MIME features are described here, the implementer is referred to the relevant RFCs for complete details. It is also advisable to check for IETF drafts of various Internet Mail specifications that are later than the most recent RFCs since, for example, MIME has yet to be published as a full IETF Standard. The table in Appendix A summarizes the protocol details of this profile.
以下各节描述了符合此VPIM v2配置文件所需的Internet邮件协议的限制和添加。虽然这里描述了各种SMTP、ESMTP和MIME特性，但实现者可以参考相关RFC以获得完整的详细信息。还建议检查各种Internet邮件规范的IETF草案是否晚于最新的RFC，例如，MIME尚未作为完整的IETF标准发布。附录A中的表格总结了该概要文件的协议细节。
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 [REQ].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[REQ]中的说明进行解释。
The voice message interchange format is a profile of the Internet Mail Protocol Suite. Any Internet Mail message containing the format defined in this section is referred to as a VPIM Message in this document. As a result, this document assumes an understanding of the Internet Mail specifications. Specifically, VPIM references components from the message format standard for Internet messages [RFC822], the Multipurpose Internet Message Extensions [MIME], the X.400 gateway specification [X.400], delivery status and message disposition notifications [REPORT][DSN][DRPT][STATUS][MDN], and the electronic business card [MIMEDIR][VCARD].
语音消息交换格式是Internet邮件协议套件的一种配置文件。任何包含本节定义格式的Internet邮件在本文档中称为VPIM邮件。因此，本文档假定您了解Internet邮件规范。具体而言，VPIM引用了互联网消息的消息格式标准[RFC822]、多用途互联网消息扩展[MIME]、X.400网关规范[X.400]、传递状态和消息处置通知[REPORT][DSN][DRPT][status][MDN]和电子名片[MIMEDIR][VCARD]中的组件。
RFC 822 addresses are based on the domain name system. This naming system has two components: the local part, used for username or mailbox identification; and the host part, used for global machine identification.
RFC 822地址基于域名系统。此命名系统有两个组件：本地部分，用于用户名或邮箱标识；主机部分，用于全局机器识别。
The local part of the address shall be a US-ASCII string uniquely identifying a mailbox on a destination system. For voice messaging, the local part is a printable string containing the mailbox ID of the originator or recipient. While alpha characters and long mailbox identifiers are permitted, most voice mail networks rely on numeric mailbox identifiers to retain compatibility with the limited 10 digit telephone keypad. As a result, some voice messaging systems may only be able to handle a numeric local part. The reception of alphanumeric local parts on these systems may result in the address being mapped to some locally unique (but confusing to the recipient) number or, in the worst case the address could be deleted making the message un-replyable. Additionally, it may be difficult to create messages on these systems with an alphanumeric local part without complex key sequences or some form of directory lookup (see 6).
地址的本地部分应为唯一标识目标系统上邮箱的US-ASCII字符串。对于语音消息，本地部分是一个可打印的字符串，其中包含发起者或收件人的邮箱ID。虽然允许使用字母字符和长邮箱标识符，但大多数语音邮件网络依靠数字邮箱标识符来保持与有限的10位电话键盘的兼容性。因此，某些语音消息系统可能只能处理数字本地部分。在这些系统上接收字母数字的本地部分可能会导致地址被映射到某些本地唯一的（但收件人会感到困惑）号码，或者在最坏的情况下，地址可能会被删除，从而使邮件无法回复。此外，在这些系统上，如果没有复杂的键序列或某种形式的目录查找，可能很难使用字母数字本地部分创建消息（请参见6）。
The use of the domain naming system should be transparent to the user. It is the responsibility of the voice mail machine to lookup the fully-qualified domain name (FQDN) based on the address entered by the user (see 6).
域命名系统的使用应该对用户透明。语音邮件机负责根据用户输入的地址查找完全限定的域名（FQDN）（参见6）。
In the absence of a global directory, specification of the local part is expected to conform to international or private telephone numbering plans. It is likely that private numbering plans will prevail and these are left for local definition. However, it is RECOMMENDED that public telephone numbers be noted according to the international numbering plan described in [E.164]. The indication
在没有全球目录的情况下，本地部分的规格应符合国际或私人电话编号计划。可能会以私人编号计划为准，这些计划留待当地定义。但是，建议根据[E.164]中所述的国际编号计划注明公共电话号码。指征
that the local part is a public telephone number is given by a preceding `+' (the `+' would not be entered from a telephone keypad, it is added by the system as a flag). Since the primary information in the numeric scheme is contained by the digits, other character separators (e.g. `-') may be ignored (i.e. to allow parsing of the numeric local mailbox) or may be used to recognize distinct portions of the telephone number (e.g. country code). The specification of the local part of a VPIM address can be split into the four groups described below:
本地部分是公共电话号码，由前面的“+”给出（不会从电话键盘输入“+”，而是由系统添加为标志）。由于数字方案中的主要信息包含在数字中，因此可以忽略其他字符分隔符（例如，“-”）（即，允许解析数字本地邮箱），或可用于识别电话号码的不同部分（例如，国家代码）。VPIM地址的本地部分的规范可分为以下四组：
1) mailbox number - for use as a private numbering plan (any number of digits) - e.g. 2722@lucent.com
1) 邮箱号码-用作专用编号计划（任意位数）-例如。2722@lucent.com
2) mailbox number+extension
- for use as a private numbering plan with extensions
any number of digits, use of `+' as separator
- e.g. 2722+111@Lucent.com
2) mailbox number+extension
- for use as a private numbering plan with extensions
any number of digits, use of `+' as separator
- e.g. 2722+111@Lucent.com
3) +international number - for international telephone numbers conforming to E.164 maximum of 15 digits - e.g. +16137637582@vm.nortel.ca
3) +国际号码-适用于符合E.164的国际电话号码，最多15位-例如+16137637582@vm.nortel.ca
4) - for international telephone numbers conforming to E.164 maximum of 15 digits, with an extension (e.g. behind a PBX) that has a maximum of 15 digits. - e.g. +17035245550+230@ema.org
4) -适用于符合E.164标准的国际电话号码，最多15位，分机（如PBX后）最多15位。-e、 g.+17035245550+230@ema.org
Note that this address format is designed to be compatible with current usage within the voice messaging industry. It is not compatible with the addressing formats of RFCs 2303-2304. It is expected that as telephony services become more widespread on the Internet, these addressing formats will converge.
请注意，此地址格式旨在与语音信息行业的当前使用情况兼容。它与RFCs 2303-2304的寻址格式不兼容。预计随着电话服务在互联网上越来越普及，这些寻址格式将趋同。
Special addresses are provided for compatibility with the conventions of Internet mail. These addresses do not use numeric local addresses, both to conform to current Internet practice and to avoid conflict with existing numeric addressing plans. Two special addresses are RESERVED for use as follows:
提供特殊地址以与Internet邮件的约定兼容。这些地址不使用数字本地地址，既符合当前的互联网实践，又避免与现有的数字寻址计划冲突。保留两个特殊地址供使用，如下所示：
postmaster@domain
postmaster@domain
By convention, a special mailbox named "postmaster" MUST exist on all systems. This address is used for diagnostics and should be checked regularly by the system manager. This mailbox is particularly likely
按照惯例，所有系统上都必须存在一个名为“postmaster”的特殊邮箱。此地址用于诊断，应由系统管理员定期检查。这个邮箱特别可能
to receive text messages, which is not normal on a voice processing platform. The specific handling of these messages is an individual implementation choice.
接收文字信息，这在语音处理平台上是不正常的。这些消息的具体处理是一个单独的实现选择。
non-mail-user@domain
非邮件-user@domain
If a reply to a message is not possible, such as a telephone answering message, then the special address "non-mail-user" must be used as the originator's address. Any text name such as "Telephone Answering", or the telephone number if it is available, is permitted. This special address is used as a token to indicate an unreachable originator. For compatibility with the installed base of mail user agents, implementations that generate this special address MUST send a negative delivery status notification (DSN) for reply messages sent to the undeliverable address. The status code for such NDN's is 5.1.1 "Mailbox does not exist".
如果无法回复邮件，例如电话应答邮件，则必须使用特殊地址“非邮件用户”作为发起者的地址。允许使用任何文本名称，如“电话应答”或电话号码（如果有）。此特殊地址用作令牌，表示无法访问的发起者。为了与已安装的邮件用户代理兼容，生成此特殊地址的实现必须为发送到无法送达地址的回复消息发送负面送达状态通知（DSN）。此类NDN的状态代码为5.1.1“邮箱不存在”。
Example:
例子：
From: Telephone Answering <non-mail-user@mycompany.com>
From: Telephone Answering <non-mail-user@mycompany.com>
There are many ways to handle distribution list (DL) expansions and none are 'standard'. Simple alias is a behavior closest to what most voice mail systems do today and what is to be used with VPIM messages. That is:
有很多方法可以处理通讯组列表（DL）扩展，但没有一种是“标准”的。简单别名是一种最接近当今大多数语音邮件系统的行为，以及VPIM消息的使用方式。即:
Reply to the originator - (Address in the RFC822 Reply-to or From field) Errors to the submitter - (Address in the MAIL FROM: field of the ESMTP exchange and the Return-Path: RFC 822 field)
回复发起人-（RFC822回复到或来自字段中的地址）提交人错误-（ESMTP交换的邮件发件人字段中的地址和返回路径：RFC 822字段）
Some proprietary voice messaging protocols include only the recipient of the particular copy in the envelope and include no "header fields" except date and per-message features. Most voice messaging systems do not provide for "Header Information" in their messaging queues and only include delivery information. As a result, recipient information MAY be in either the To or CC header fields. If all recipients cannot be presented (e.g. unknown DL expansion) then the recipient header fields MUST be omitted to indicate that an accurate list of recipients (e.g. for use with a reply-all capability) is not known.
一些专有语音消息协议仅包括信封中特定副本的收件人，不包括除日期和每条消息功能以外的“标题字段”。大多数语音消息传递系统在其消息传递队列中不提供“标题信息”，只包含传递信息。因此，收件人信息可能位于收件人或抄送标头字段中。如果无法显示所有收件人（例如，未知的DL扩展），则必须省略收件人标题字段，以表明不知道收件人的准确列表（例如，用于回复所有功能）。
Internet messages contain a header information block. This header block contains information required to identify the sender, the list of recipients, the message send time, and other information intended for user presentation. Except for specialized gateway and mailing list cases, header fields do not indicate delivery options for the transport of messages.
Internet消息包含标题信息块。此标题块包含标识发件人、收件人列表、邮件发送时间所需的信息，以及用于用户演示的其他信息。除专用网关和邮件列表情况外，标题字段不表示邮件传输的传递选项。
Distribution list processors are noted for modifying or adding to the header fields of messages that pass through them. VPIM systems MUST be able to accept and ignore header fields that are not defined here.
通讯组列表处理程序以修改或添加通过它们的消息的标题字段而著称。VPIM系统必须能够接受和忽略此处未定义的标题字段。
The following header lines are permitted for use with VPIM voice messages:
以下标题行允许与VPIM语音消息一起使用：
The originator's fully-qualified domain address (a mailbox address followed by the fully-qualified domain name). The user listed in this field should be presented in the voice message envelope as the originator of the message.
发端人的完全限定域名（邮箱地址后跟完全限定域名）。此字段中列出的用户应作为消息的发起人出现在语音消息信封中。
Systems compliant with this profile SHOULD provide the text personal name of the voice message originator in a quoted phrase, if the name is available. Text names of corporate or positional mailboxes MAY be provided as a simple string. From [RFC822]
符合此配置文件的系统应在引用的短语中提供语音消息发起人的文本个人名称（如果名称可用）。公司邮箱或位置邮箱的文本名称可以作为简单字符串提供。来自[RFC822]
Example:
例子：
From: "Joe S. User" <12145551212@mycompany.com>
From: "Joe S. User" <12145551212@mycompany.com>
From: Technical Support <611@serviceprovider.com>
From: Technical Support <611@serviceprovider.com>
The From address SHOULD be used for replies (see 4.6). However, if the From address contains <non-mail-user@domain>, the user SHOULD NOT be offered the option to reply, nor should notifications be sent to this address.
发件人地址应用于回复（见4.6）。但是，如果发件人地址包含<非邮件-user@domain>，不应向用户提供回复选项，也不应向此地址发送通知。
Voice mail machines may not be able to support separate attributes for the FROM, REPLY-TO, and SENDER header field and the SMTP MAIL FROM command, VPIM conforming systems SHOULD set these values to the same address. Use of addresses different than those present in the From header field address may result in unanticipated behavior.
语音邮件计算机可能无法支持“发件人”、“回复收件人”和“发件人”标题字段的单独属性以及“SMTP邮件发件人”命令，符合VPIM的系统应将这些值设置为相同的地址。使用不同于From标头字段地址中的地址可能会导致意外行为。
The To header contains the recipient's fully-qualified domain address. There may be one or more To: fields in any message.
收件人标头包含收件人的完全限定域地址。任何消息中可能有一个或多个“收件人：”字段。
Example:
例子：
To: +12145551213@mycompany.com
To: +12145551213@mycompany.com
Systems compliant to this profile SHOULD provide a list of recipients only if all recipients are provided. The To header MUST NOT be included in the message if the sending message transport agent (MTA) cannot resolve all the addresses in it, e.g. if an address is a DL alias for which the expansion is unknown (see 4.1.3). If present, the addresses in the To header MAY be used for a reply message to all recipients.
仅当提供了所有收件人时，符合此配置文件的系统才应提供收件人列表。如果发送邮件的传输代理（MTA）无法解析邮件中的所有地址，例如，如果某个地址是扩展未知的DL别名，则收件人标头不得包含在邮件中（请参阅4.1.3）。如果存在，收件人标头中的地址可用于向所有收件人发送回复消息。
Systems compliant to this profile MAY also discard the To addresses of incoming messages because of the inability to store the information. This would, of course, make a reply-to-all capability impossible.
符合此配置文件的系统也可能因为无法存储信息而丢弃传入消息的to地址。当然，这将使对所有能力的回答变得不可能。
The cc header contains additional recipients' fully-qualified domain addresses. Many voice mail systems maintain only sufficient envelope information for message delivery and are not capable of storing or providing a complete list of recipients.
cc标头包含其他收件人的完全限定域地址。许多语音邮件系统仅保留足够的信封信息用于邮件传递，无法存储或提供完整的收件人列表。
Systems compliant to this profile SHOULD provide a list of recipients only if all disclosed recipients can be provided. The list of disclosed recipients does not include those sent via a blind copy. If not, systems SHOULD omit the To and Cc header fields to indicate that the full list of recipients is unknown.
只有在可以提供所有披露的收件人的情况下，符合此配置文件的系统才应提供收件人列表。披露的收件人列表不包括通过盲拷贝发送的收件人。如果没有，系统应省略“收件人”和“抄送头”字段，以指示收件人的完整列表未知。
Example:
例子：
Cc: +12145551213@mycompany.com
Cc: +12145551213@mycompany.com
Systems compliant to this profile MAY discard the Cc addresses of incoming messages as necessary. If a list of Cc or to addresses is present, these addresses MAY be used for a reply message to all recipients.
符合此配置文件的系统可根据需要丢弃传入消息的Cc地址。如果存在抄送或收件人地址列表，则这些地址可用于向所有收件人发送回复消息。
The Date header contains the date, time, and time zone in which the message was sent by the originator. The time zone SHOULD be represented in a four-digit time zone offset, such as -0500 for North American Eastern Standard Time. This may be supplemented by a time zone name in parentheses, e.g., "-0900 (PDT)". Compliant implementations SHOULD be able to convert RFC 822 date and time stamps into local time.
日期标题包含发端人发送邮件的日期、时间和时区。时区应以四位时区偏移量表示，如北美东部标准时间为-0500。这可以用括号中的时区名称来补充，例如“-0900（PDT）”。兼容的实现应该能够将RFC 822日期和时间戳转换为本地时间。
Example:
例子：
Date: Wed, 28 Jul 96 10:08:49 -0800 (PST)
Date: Wed, 28 Jul 96 10:08:49 -0800 (PST)
The sending system MUST report the time the message was sent. If the VPIM sender is relaying a message from a system which does not provide a time stamp, the time of arrival at the VPIM system SHOULD be used as the date. From [RFC822]
发送系统必须报告消息的发送时间。如果VPIM发送方正在中继来自未提供时间戳的系统的消息，则到达VPIM系统的时间应作为日期。来自[RFC822]
The Sender header field contains the actual address of the originator if the message is sent by an agent on behalf of the author indicated in the From: field. This header field MAY be sent by VPIM conforming system. If it is present in a VPIM message, the receiving VPIM implementation may ignore the field and only present the From header field.
如果邮件是由代理代表发件人：字段中指定的作者发送的，则发件人标头字段包含发端人的实际地址。该标题字段可由符合VPIM的系统发送。如果它存在于VPIM消息中，则接收VPIM实现可能会忽略该字段，而只显示From标头字段。
The Return-path header is added by the final delivering SMTP server. If present, it contains the address from the MAIL FROM parameter of the ESMTP exchange (see 5.1.2). Any error messages resulting from the delivery failure MUST be sent to this address (see [DRPT] for additional details). Note that if the Return-path is null ("<>"), e.g. no path, loop prevention or confidential, a notification MUST NOT be sent. If the Return path address is not available (either from this header or the MAIL FROM parameter) the From address may be used to deliver notifications.
返回路径头由最终的SMTP服务器添加。如果存在，则包含来自ESMTP交换的MAIL from参数的地址（见5.1.2）。由于传递失败而产生的任何错误消息都必须发送到此地址（有关更多详细信息，请参阅[DRPT]）。请注意，如果返回路径为null（“<>”），例如无路径、循环预防或机密，则不得发送通知。如果返回路径地址不可用（来自此标头或MAIL from参数），则可以使用发件人地址发送通知。
The Message-id header contains a unique per-message identifier. A unique message-id MUST be generated for each message sent from a compliant implementation.
消息id标头包含每个消息的唯一标识符。必须为从兼容实现发送的每条消息生成唯一的消息id。
The message-id is not required to be stored on the receiving system. This identifier MAY be used for tracking, auditing, and returning
消息id不需要存储在接收系统上。此标识符可用于跟踪、审核和返回
receipt notification reports. From [RFC822]
接收通知报告。来自[RFC822]
Example:
例子：
Message-id: <12345678@mycompany.com>
Message-id: <12345678@mycompany.com>
If present, the reply-to header provides a preferred address to which reply messages should be sent (see 4.6). Typically, voice mail systems can only support one originator of a message so it is unlikely that this field can be supported. A compliant system SHOULD NOT send a Reply-To header. However, if a reply-to header is present, a reply-to sender message MAY be sent to the address specified (that is, overwriting From). From [RFC822] This preferred address of the originator must also be provided in the originator's vCard EMAIL attribute, if present (see 4.3.3).
如果存在，回复头提供了回复消息应发送到的首选地址（见4.6）。通常，语音邮件系统只能支持一条消息的一个发起人，因此不太可能支持此字段。符合要求的系统不应向标头发送回复。但是，如果存在回复标头，则回复发件人消息可能会发送到指定的地址（即，从覆盖）。[RFC822]发端人的首选地址也必须在发端人的vCard电子邮件属性中提供（如有）（见4.3.3）。
The Received header contains trace information added to the beginning of a RFC 822 message by MTAs. This is the only header permitted to be added by an MTA. Information in this header is useful for debugging when using an US-ASCII message reader or a header parsing tool.
收到的标头包含MTA添加到RFC 822邮件开头的跟踪信息。这是MTA允许添加的唯一标头。当使用US-ASCII消息读取器或标头解析工具时，此标头中的信息对于调试非常有用。
A compliant system MUST add Received header fields when acting as a gateway and MUST NOT remove any Received fields when relaying messages to other MTAs or gateways.. These header fields MAY be ignored or deleted when the message is received at the final destination. From [RFC822]
兼容系统在充当网关时必须添加接收的标头字段，在将邮件中继到其他MTA或网关时不得删除任何接收的字段。。当在最终目的地收到消息时，这些标题字段可能会被忽略或删除。来自[RFC822]
The MIME-Version header indicates that the message conforms to the MIME message format specification. Systems compliant with this specification SHOULD include a comment with the words "(Voice 2.0)". RFC 1911 defines an earlier version of this profile and uses the token (Voice 1.0). From [MIME1][VPIM1]
MIME版本头表示消息符合MIME消息格式规范。符合本规范的系统应包括带有“Voice 2.0”字样的注释。RFC 1911定义了此配置文件的早期版本，并使用令牌（Voice 1.0）。来自[MIME1][VPIM1]
Example:
例子：
MIME-Version: 1.0 (Voice 2.0)
MIME版本：1.0（语音2.0）
This identifier is intended for information only and SHOULD NOT be used to semantically identify the message as being a VPIM message. Instead, the presence of the content defined in [V-MSG] SHOULD be used if identification is necessary.
此标识符仅供参考，不应用于从语义上将消息标识为VPIM消息。相反，如果需要识别，则应使用[V-MSG]中定义的内容。
The content-type header declares the type of content enclosed in the message. The typical top level content in a VPIM Message SHOULD be multipart/voice-message, a mechanism for bundling several components into a single identifiable voice message. The allowable contents are detailed in section 4.3 of this document. From [MIME2]
content type标头声明消息中包含的内容类型。VPIM消息中典型的顶级内容应该是多部分/语音消息，这是一种将多个组件捆绑到单个可识别语音消息中的机制。允许的内容详见本文件第4.3节。从[MIME2]
Because Internet mail was initially specified to carry only 7-bit US-ASCII text, it may be necessary to encode voice and fax data into a representation suitable for that environment. The content-transfer-encoding header describes this transformation if it is needed. Compliant implementations MUST recognize and decode the standard encodings, "Binary", "7bit, "8bit", "Base64" and "Quoted-Printable". The allowable content-transfer-encodings are specified in section 4.3. From [MIME1]
由于最初指定Internet邮件仅携带7位US-ASCII文本，因此可能需要将语音和传真数据编码为适合该环境的表示形式。如果需要，content transfer encoding标头将描述此转换。符合要求的实现必须识别和解码标准编码、“二进制”、“7位”、“8位”、“Base64”和“可打印引用”。允许的内容传输编码在第4.3节[MIME1]中规定
The sensitivity header, if present, indicates the requested privacy level. The case-insensitive values "Personal" and "Private" are specified. If no privacy is requested, this field is omitted.
灵敏度标头（如果存在）指示请求的隐私级别。指定了不区分大小写的值“Personal”和“Private”。如果未请求隐私，则忽略此字段。
If a sensitivity header is present in the message, a compliant system MUST prohibit the recipient from forwarding this message to any other user. A compliant system, however, SHOULD allow the responder to reply to a sensitive message, but SHOULD NOT include the original message content. The sensitivity of the reply message MAY be set by the responder.
如果邮件中存在敏感度标头，则合规系统必须禁止收件人将此邮件转发给任何其他用户。但是，兼容系统应允许响应者回复敏感消息，但不应包含原始消息内容。回复消息的灵敏度可由响应者设置。
If the receiving system does not support privacy and the sensitivity is one of "Personal" or "Private", a negative delivery status notification must sent to the originator with the appropriate status code indicating that privacy could not be assured. The message contents SHOULD be returned to the sender to allow for a voice context with the notification. A non-delivery notification to a private message SHOULD NOT be tagged private since it will be sent to the originator. From: [X.400]
如果接收系统不支持隐私，且敏感度为“个人”或“私人”，则必须向发端人发送负面交付状态通知，并附上适当的状态代码，表明无法确保隐私。应将消息内容返回给发送者，以允许通知的语音上下文。私人邮件的未送达通知不应标记为私人，因为它将被发送给发端人。发件人：[X.400]
Indicates the requested importance to be given by the receiving system. The case-insensitive values "low", "normal" and "high" are specified. If no special importance is requested, this header may be omitted and the value assumed to be "normal".
指示接收系统要给出的请求重要性。指定了不区分大小写的值“低”、“正常”和“高”。如果未要求特殊重要性，则可省略该标题，并假定该值为“正常”。
Compliant implementations MAY use this header to indicate the importance of a message and may order messages in a recipient's mailbox. From: [X.400]
兼容的实现可以使用此标头指示邮件的重要性，并可以在收件人的邮箱中对邮件进行排序。发件人：[X.400]
The subject field is often provided by email systems but is not widely supported on Voice Mail platforms. For compatibility with text based mailbox interfaces, a text subject field SHOULD be generated by a compliant implementation but MAY be discarded if present by a receiving system. From [RFC822]
主题字段通常由电子邮件系统提供，但在语音邮件平台上不受广泛支持。为了与基于文本的邮箱接口兼容，文本主题字段应该由兼容的实现生成，但如果接收系统存在，则可以丢弃。来自[RFC822]
It is recommended that voice messaging systems that do not support any text user interfaces (e.g. access only by a telephone) insert a generic subject header of "VPIM Message" for the benefit of text enabled recipients.
建议不支持任何文本用户界面（例如，仅通过电话访问）的语音消息系统插入“VPIM消息”的通用主题标题，以方便启用文本的收件人。
This header MAY be present to indicate that the sender is requesting a receipt notification from the receiving user agent. This message disposition notification (MDN) is typically sent by the user agent after the user has listened to the message and consented to an MDN being sent
该报头可以存在以指示发送方正在从接收用户代理请求接收通知。此消息处置通知（MDN）通常在用户侦听消息并同意发送MDN后由用户代理发送
Example:
例子：
Disposition-notification-to: +12145551213@mycompany.com
Disposition-notification-to: +12145551213@mycompany.com
The presence of a Disposition-notification-to header in a message is merely a request for an MDN described in 4.4.5. The recipients' user agents are always free to silently ignore such a request so this header does not burden any system that does not support it. From [MDN].
消息中出现对消息头的处置通知只是对MDN的请求，如4.4.5所述。接收者的用户代理总是可以无提示地忽略这样的请求，因此此头不会给任何不支持它的系统带来负担。来自[MDN]。
This header MAY be present to define future extensions parameters for an MDN requested by the presence of the header in the previous section. Currently no parameters are defined by this document or by [MDN]. However, this header MUST be parsed if present, if MDNs are supported. If it contains a extension parameter that is required for proper MDN generation (noted with "=required"), then an MDN MUST NOT be sent if the parameter is not understood. See [MDN] for complete details.
此报头的存在可能是为了定义前一节中报头存在所请求的MDN的未来扩展参数。目前，本文档或[MDN]未定义任何参数。但是，如果支持MDN，则必须解析此标头（如果存在）。如果它包含正确生成MDN所需的扩展参数（用“=required”表示），则如果不理解该参数，则不得发送MDN。有关完整的详细信息，请参见[MDN]。
Example:
例子：
Disposition-notification-options: whizzbang=required,foo
处置通知选项：whizzbang=必需，foo
MIME, introduced in [MIME1], is a general-purpose message body format that is extensible to carry a wide range of body parts. It provides for encoding binary data so that it can be transported over the 7-bit text-oriented SMTP protocol. This transport encoding (denoted by the Content-Transfer-Encoding header field) is in addition to the audio encoding required to generate a binary object.
MIME是在[MIME1]中引入的一种通用消息正文格式，可扩展以承载广泛的正文部分。它提供二进制数据编码，以便通过7位面向文本的SMTP协议传输。此传输编码（由内容传输编码头字段表示）是生成二进制对象所需音频编码的补充。
MIME defines two transport encoding mechanisms to transform binary data into a 7 bit representation, one designed for text-like data ("Quoted-Printable"), and one for arbitrary binary data ("Base64"). While Base64 is dramatically more efficient for audio data, either will work. Where binary transport is available, no transport encoding is needed, and the data can be labeled as "Binary".
MIME定义了两种传输编码机制，用于将二进制数据转换为7位表示形式，一种用于类文本数据（“引用的可打印”），另一种用于任意二进制数据（“Base64”）。虽然Base64对音频数据的效率显著提高，但两者都可以。在二进制传输可用的情况下，不需要传输编码，数据可以标记为“二进制”。
An implementation in compliance with this profile SHOULD send audio and/or facsimile data in binary form when binary message transport is available. When binary transport is not available, implementations MUST encode the audio and/or facsimile data as Base64. The detection and decoding of "Quoted-Printable", "7bit", and "8bit" MUST be supported in order to meet MIME requirements and to preserve interoperability with the fullest range of possible devices. However, if a content is received in a transfer encoding that cannot be rendered to the user, an appropriate negative delivery status notification MUST be sent.
当二进制消息传输可用时，符合此配置文件的实现应以二进制形式发送音频和/或传真数据。当二进制传输不可用时，实现必须将音频和/或传真数据编码为Base64。必须支持检测和解码“引用可打印”、“7bit”和“8bit”，以满足MIME要求，并保持与尽可能多的设备的互操作性。但是，如果以传输编码接收的内容无法呈现给用户，则必须发送相应的负面传递状态通知。
The content types described in this section are identified for use within the multipart/voice-message content. This content, which is the fundamental part of a VPIM message, is referred to as a VPIM voice message in this document.
本节中描述的内容类型可在多部分/语音消息内容中使用。此内容是VPIM消息的基本部分，在本文档中称为VPIM语音消息。
Only the contents profiled subsequently can be sent within a VPIM voice message construct (i.e., the mulitpart/voice-message content type) to form a simple or a more complex structure (several examples are given in Appendix B). The presence of other contents within a VPIM voice message is an error condition and SHOULD result in a negative delivery status notification. When multiple contents are present within the multipart/voice-message, they SHOULD be presented to the user in the order that they appear in the message.
只有随后分析的内容才能在VPIM语音消息构造（即多部分/语音消息内容类型）内发送，以形成简单或更复杂的结构（附录B中给出了几个示例）。VPIM语音消息中存在其他内容是一种错误情况，应导致负面传递状态通知。当多部分/语音消息中存在多个内容时，应按照它们在消息中出现的顺序向用户显示这些内容。
This MIME multipart structure provides a mechanism for packaging a voice message into one container that is tagged as VPIM v2 compliant. The semantic of multipart/Voice-Message (defined in [V-MSG]) is identical to multipart/mixed and may be interpreted as that by systems that do not recognize this content-type.
此MIME多部分结构提供了一种机制，用于将语音消息打包到标记为符合VPIM v2的容器中。多部分/语音消息（在[V-MSG]中定义）的语义与多部分/混合消息相同，可能被不识别此内容类型的系统解释为语义相同。
The Multipart/Voice-Message content-type MUST only contain the profiled media and content types specified in this section (i.e. audio/*, image/*, message/rfc822 and text/directory). The most common will be: spoken name, spoken subject, the message itself, attached fax and directory info. Forwarded messages are created by simply using the message/rfc822 construct.
多部分/语音消息内容类型必须仅包含本节中指定的分析媒体和内容类型（即音频/*、图像/*、消息/rfc822和文本/目录）。最常见的是：口头姓名、口头主题、邮件本身、附加传真和目录信息。转发的消息只需使用message/rfc822构造即可创建。
Conformant implementations MUST send the multipart/voice-message in a VPIM message. In most cases, this Multipart/Voice-Message content will be the top level (i.e. in the Content-Type header). Conformant implementations MUST recognize the Multipart/Voice-Message content (whether it is a top level content or below a multipart/mixed) and be able to separate the contents (e.g. spoken name or spoken subject).
一致性实现必须在VPIM消息中发送多部分/语音消息。在大多数情况下，此多部分/语音消息内容将是顶层（即，在内容类型标头中）。一致性实现必须识别多部分/语音消息内容（无论是顶级内容还是多部分/混合内容之下的内容），并能够分离内容（例如，语音名称或语音主题）。
MIME requires support of the Message/RFC822 message encapsulation body part. This body part is used within a multipart/voice-message to forward complete messages (see 4.5) or to reply with original content (see 4.6). From [MIME2]
MIME需要消息/RFC822消息封装体部分的支持。此正文部分在多部分/语音消息中用于转发完整消息（见4.5）或以原始内容回复（见4.6）。从[MIME2]
This content allows for the inclusion of a Versit vCard [VCARD] electronic business card within a VPIM message. The format is suitable as an interchange format between applications or systems, and is defined independent of the method used to transport it. It provides a useful mechanism to transport information about the originator that can be used by the receiving VPIM system (see 6) or other local applications
此内容允许在VPIM消息中包含Version vCard[vCard]电子名片。该格式适合作为应用程序或系统之间的交换格式，并且独立于用于传输该格式的方法进行定义。它提供了一种有用的机制来传输有关发起人的信息，可供接收VPIM系统（见6）或其他本地应用程序使用
Each vCard MUST be contained within a Text/Directory content type [MIMEDIR] within a VPIM message. [MIMEDIR] requires that the character set MUST be defined as a parameter value (typically us-ascii for VPIM) and that the profile SHOULD be defined (the value MUST be vCard within VPIM messages).
每个vCard必须包含在VPIM消息中的文本/目录内容类型[MIMEDIR]中。[MIMEDIR]要求必须将字符集定义为参数值（对于VPIM，通常为us ascii），并且应定义配置文件（该值必须是VPIM消息中的vCard）。
Each VPIM message SHOULD be created with a Text/Directory (vCard profile) content type that MUST contain the preferred email address, telephone number, and text name of the message originator as well as
应使用文本/目录（vCard profile）内容类型创建每条VPIM消息，该内容类型必须包含首选电子邮件地址、电话号码和消息发起人的文本名称以及
the vCard version. The vCard SHOULD contain the spoken name and role of the originator, as well as the revision date. Any other vCard attribute MAY also be present. The intent is that the vCard be used as the source of information to contact the originator (e.g., reply, call).If the text/directory content-type is included in a VPIM message, the vCard profile [VCARD] MUST be used and MUST specify at least the following attributes:
vCard版本。vCard应包含发起者的口头姓名和角色，以及修订日期。任何其他vCard属性也可能存在。其目的是将vCard用作联系发起人的信息源（例如回复、呼叫）。如果VPIM消息中包含文本/目录内容类型，则必须使用vCard配置文件[vCard]，并且必须至少指定以下属性：
TEL - Public switched telephone number in international (E.164) format (various types, typically VOICE)
TEL-国际（E.164）格式的公共交换电话号码（各种类型，通常为语音）
EMAIL - email address (various types, typically INTERNET; the type VPIM is optionally used to denote an address that supports VPIM messages(see 18.1))
电子邮件-电子邮件地址（各种类型，通常为INTERNET；VPIM类型可选地用于表示支持VPIM消息的地址（见18.1））
VERSION - Indicates the version of the vCard profile. Version 3.0 [VCARD] MUST be used.
版本-表示vCard配置文件的版本。必须使用3.0版[VCARD]。
The following attributes SHOULD be specified:
应指定以下属性：
N - Family Name, Given Name, Additional Names, Honorific Prefixes, and Suffixes. Because it is expected that recipients using a telephone user interface will use the information in the vCard to identify the originator, and the GUI will see the information presented in the FROM line, all present components in the text name of the FROM header field MUST match the values provided by the Vcard.
N-姓、名、附加名、尊称前缀和后缀。由于预期使用电话用户界面的收件人将使用vCard中的信息来识别发起人，并且GUI将看到FROM行中显示的信息，FROM标题字段文本名称中的所有现有组件必须与vCard提供的值匹配。
ROLE - The role of the person identified in `N' or `FN', but may also be used to distinguish when the sender is a corporate or positional mailbox
角色-在“N”或“FN”中标识的人的角色，但也可用于区分发件人是公司邮箱还是职位邮箱
SOUND - spoken name sound data (various types, typically 32KADPCM)
声音-语音名称声音数据（各种类型，通常为32KADPCM）
REV - Revision of vCard in ISO 8601 date format
版次-ISO 8601日期格式的vCard版次
The vCard MAY use other attributes as defined in [VCARD] or extensions attributes not yet defined (e.g. capabilities).
vCard可以使用[vCard]中定义的其他属性或尚未定义的扩展属性（例如功能）。
If present, the spoken name attribute MUST be denoted by a content ID
pointing to an audio/* content elsewhere in the VPIM message.
If present, the spoken name attribute MUST be denoted by a content ID
pointing to an audio/* content elsewhere in the VPIM message.
A typical VPIM message (i.e. no forwarded parts), MUST only contain one vCard -- more than one is an error condition. A VPIM message that contains forwarded messages, though, may contain multiple vCards. However, these vCards MUST be associated with the originator(s) of the forwarded message(s) and the originator of the forwarding message. As a result, all forwarded vCards will be
典型的VPIM消息（即没有转发的部分）只能包含一个vCard——多个vCard是一种错误情况。但是，包含转发消息的VPIM消息可能包含多个vCard。但是，这些vCard必须与转发消息的发起人和转发消息的发起人关联。因此，所有转发的vCard都将被删除
contained in message/rfc822 contents -- only the vCard of forwarding originator will be at the top-level.
包含在message/rfc822内容中——只有转发发起人的vCard将处于顶层。
Example:
例子：
Content-Type: text/directory; charset=us-ascii; profile=vCard
Content-Transfer-Encoding: 7bit
Content-Type: text/directory; charset=us-ascii; profile=vCard
Content-Transfer-Encoding: 7bit
BEGIN:VCARD
N:Parsons;Glenn
ORG:Northern Telecom
TEL;TYPE=VOICE;MSG;WORK:+1-613-763-7582
EMAIL;TYPE=INTERNET;glenn.parsons@nortel.ca
EMAIL;TYPE=INTERNET;VPIM:6137637582@vm.nortel.ca
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part1@VM2-4321>
REV:19960831T103310Z
VERSION: 3.0
END:VCARD
BEGIN:VCARD
N:Parsons;Glenn
ORG:Northern Telecom
TEL;TYPE=VOICE;MSG;WORK:+1-613-763-7582
EMAIL;TYPE=INTERNET;glenn.parsons@nortel.ca
EMAIL;TYPE=INTERNET;VPIM:6137637582@vm.nortel.ca
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part1@VM2-4321>
REV:19960831T103310Z
VERSION: 3.0
END:VCARD
An implementation compliant to this profile MUST send Audio/32KADPCM by default for voice [ADPCM]. Receivers MUST be able to accept and decode Audio/32KADPCM. Typically this body contains several minutes of message content, however if used for spoken name or subject the content should be considerably shorter (i.e. about 10 and 20 seconds respectively).
默认情况下，符合此配置文件的实现必须为语音[ADPCM]发送音频/32KADPCM。接收机必须能够接收和解码音频/32KADPCM。通常，此正文包含几分钟的消息内容，但是如果用于口头姓名或主题，则内容应短得多（即分别约10秒和20秒）。
If an implementation can only handle one voice body, then multiple voice bodies (if present) SHOULD be concatenated, and SHOULD NOT be discarded. It is RECOMMENDED that this be done in the same order as they were sent. Note that if an Originator Spoken Name audio body and a vCard are both present in a VPIM message, the vCard SOUND attribute MUST point to this audio body (see 4.3.3).
如果一个实现只能处理一个语音体，那么应该连接多个语音体（如果存在），并且不应该丢弃。建议按照发送顺序执行此操作。请注意，如果VPIM消息中同时存在发起者语音名称音频体和vCard，则vCard SOUND属性必须指向该音频体（参见4.3.3）。
While any valid MIME body header MAY be used, several header fields have the following semantics when included with this body part:
虽然可以使用任何有效的MIME正文标题，但当包含在此正文部分时，几个标题字段具有以下语义：
4.3.4.1 Content-Description:
4.3.4.1 内容描述：
This field MAY be present to facilitate the text identification of these body parts in simple email readers. Any values may be used, though it may be useful to use values similar to those for Content-Disposition.
此字段可能用于帮助在简单电子邮件阅读器中识别这些身体部位的文本。可以使用任何值，但使用与内容处置类似的值可能会很有用。
Example:
例子：
Content-Description: Big Telco Voice Message
内容描述：大电信语音信息
4.3.4.2 Content-Disposition:
4.3.4.2 内容配置：
This field MUST be present to allow the parsable identification of these body parts. This is especially useful if, as is typical, more than one Audio/32KADPCM body occurs within a single level (e.g. multipart/voice-message). Since a VPIM voice message is intended to be automatically played upon display of the message, in the order in which the audio contents occur, the audio contents must always be of type inline. However, it is still useful to include a filename value, so this should be present if this information is available. From [DISP]
必须存在此字段，以便对这些身体部位进行可分析的识别。如果一个级别内出现多个音频/32KADPCM主体（如多部分/语音消息），这一点尤其有用。由于VPIM语音信息旨在在信息显示时自动播放，因此音频内容必须始终为内联类型。但是，包含一个文件名值仍然很有用，因此如果此信息可用，则应显示此文件名值。从[显示]
In order to distinguish between the various types of audio contents in a VPIM voice message a new disposition parameter "voice" is defined with the parameter values below to be used as appropriate (see 18.2):
为了区分VPIM语音信息中的各种类型的音频内容，定义了一个新的配置参数“voice”（语音），并根据需要使用以下参数值（见18.2）：
Voice-Message - the primary voice message, Voice-Message-Notification - a spoken delivery notification or spoken disposition notification, Originator-Spoken-Name - the spoken name of the originator, Recipient-Spoken-Name - the spoken name of the recipient if available to the originator and present if there is ONLY one recipient, Spoken-Subject- the spoken subject of the message, typically spoken by the originator
语音信息-主要语音信息，语音信息通知-口头送达通知或口头处置通知，发起者口头姓名-发起者的口头姓名，收件人口头姓名-收件人的口头姓名（如果发起者可用），如果只有一个收件人，则提供，口语主语-信息的口语主语，通常由发起者说
Note that there SHOULD only be one instance of each of these types of audio contents per message level. Additional instances of a given type (i.e., parameter value) may occur within an attached forwarded voice message.
请注意，对于每种类型的音频内容，每个消息级别应该只有一个实例。附加的转发语音消息中可能会出现给定类型（即参数值）的其他实例。
Implementations that do not understand the "voice" parameter (or the Content-Disposition header) can safely ignore it, and will present the audio bodyparts in order (but will not be able to distinguish between them).
不理解“voice”参数（或Content Disposition header）的实现可以安全地忽略它，并将按顺序显示音频身体部位（但无法区分它们）。
Example:
例子：
Content-Disposition: inline; voice=spoken-subject;
filename="msg001.726"
Content-Disposition: inline; voice=spoken-subject;
filename="msg001.726"
4.3.4.3 Content-Duration:
4.3.4.3 内容持续时间：
This field MAY be present to allow the specification of the length of the audio bodypart in seconds. The use of this field on reception is a local implementation issue. From [DUR]
此字段可用于以秒为单位指定音频车身部件的长度。在接收时使用此字段是本地实施问题。从[DUR]
Example:
例子：
Content-Duration: 33
内容持续时间：33
4.3.4.4 Content-Language:
4.3.4.4 内容语言：
This field MAY be present to allow the specification of the spoken language of the audio bodypart. The encoding is defined in [LANG]. The use of this field on reception is a local implementation issue.
此字段可用于指定音频身体部位的口语。编码在[LANG]中定义。在接收时使用此字段是本地实施问题。
Example for UK English:
英国英语示例：
Content-Language: en-UK
内容语言：英语
A common image encoding for facsimile, known as TIFF-F, is a derivative of the Tag Image File Format (TIFF) and is described in several documents. For the purposes of VPIM, the F Profile of TIFF for Facsimile (TIFF-F) is defined in [TIFF-F] and the image/tiff MIME content type is defined in [TIFFREG]. While there are several formats of TIFF, only TIFF-F is profiled for use in a VPIM voice message. Further, since the TIFF-F file format is used in a store-and-forward mode with VPIM, the image MUST be encoded so that there is only one image strip per facsimile page.
传真的通用图像编码，称为TIFF-F，是标签图像文件格式（TIFF）的衍生版本，在多个文档中进行了描述。就VPIM而言，传真用TIFF（TIFF-F）的F配置文件在[TIFF-F]中定义，图像/TIFF MIME内容类型在[TIFFREG]中定义。虽然TIFF有多种格式，但只有TIFF-F可用于VPIM语音消息。此外，由于TIFF-F文件格式在VPIM的存储转发模式下使用，因此必须对图像进行编码，以便每个传真页只有一个图像条。
All VPIM implementations that support facsimile SHOULD generate TIFF-F compatible facsimile contents in the image/tiff; application=faxbw sub-type encoding by default. An implementation MAY send this fax content in VPIM voice messages and MUST be able to recognize and display it in received messages. If a fax message is received that cannot be rendered to the user (e.g. the receiving VPIM system does not support fax), then the system MUST return the message with a negative delivery status notification with a media not supported status code.
支持传真的所有VPIM实现应在图像/TIFF中生成与TIFF-F兼容的传真内容；默认情况下，application=faxbw子类型编码。实现可以在VPIM语音消息中发送此传真内容，并且必须能够在接收到的消息中识别和显示它。如果收到的传真消息无法呈现给用户（例如，接收VPIM系统不支持传真），则系统必须返回带有“不支持媒体”状态代码的负面传递状态通知的消息。
While any valid MIME body header MAY be used (e.g., Content-Disposition to indicate the filename), none are specified to have special semantics for VPIM and MAY be ignored. Note that the content type parameter application=faxbw MUST be included in outbound messages. However, inbound messages with or without this parameter MUST be rendered to the user (if the rendering software encounters an error in the file format, some form of negative delivery status notification MUST be sent to the originator).
虽然可以使用任何有效的MIME正文头（例如，用于指示文件名的内容配置），但没有一个被指定为具有VPIM的特殊语义，可以忽略。请注意，出站消息中必须包含内容类型参数application=faxbw。但是，必须向用户呈现包含或不包含此参数的入站邮件（如果呈现软件遇到文件格式错误，则必须向发起人发送某种形式的负面传递状态通知）。
Proprietary voice or fax encoding formats or other standard formats MAY be supported under this profile provided a unique identifier is registered with the IANA prior to use (see [MIME4]). The voice encodings should be registered as sub-types of Audio and the fax encodings should be registered as sub-types of Image
如果在使用前向IANA注册了唯一标识符，则此配置文件可能支持专有语音或传真编码格式或其他标准格式（见[MIME4]）。语音编码应注册为音频的子类型，传真编码应注册为图像的子类型
Use of any other encoding except audio/32kadpcm or image/tiff; application=faxbw reduces interoperability in the absence of explicit manual system configuration. A compliant implementation MAY use any other encoding with explicit per-destination configuration.
使用除音频/32kadpcm或图像/tiff以外的任何其他编码；application=faxbw在没有明确的手动系统配置的情况下降低了互操作性。兼容的实现可以使用任何其他具有明确的每个目标配置的编码。
An implementation compliant with this profile MAY send additional contents in a VPIM message, but ONLY outside of the multipart/voice-message. The content types described in this section are identified for use with this profile. Additional contents not defined in this profile MUST NOT be used without prior explicit per-destination configuration. If an implementation receives a VPIM message that contains content types not specified in this profile, their handling is a local implementation issue (e.g. the unknown contents MAY be discarded if they cannot be presented to the recipient). Conversely, if an implementation receives a non-VPIM message (i.e., without a mulitpart/voice-message content type) with any of the contents defined in 4.3 & 4.4, it SHOULD deliver those contents, but the full message handling is a local issue (e.g. the unknown contents _or_ the entire message MAY be discarded). Implementations MUST issue negative delivery status notifications to the originator when any form of non-delivery to the recipient occurs.
符合此配置文件的实现可以在VPIM消息中发送附加内容，但只能在多部分/语音消息之外发送。本节中描述的内容类型已标识，可用于此配置文件。未经事先明确的每个目标配置，不得使用此配置文件中未定义的其他内容。如果实现接收到包含此配置文件中未指定的内容类型的VPIM消息，则其处理属于本地实现问题（例如，如果无法向收件人显示未知内容，则可能会丢弃这些内容）。相反，如果一个实现接收到包含4.3和4.4中定义的任何内容的非VPIM消息（即，没有多部分/语音消息内容类型），它应该交付这些内容，但完整的消息处理是一个局部问题（例如，未知内容或整个消息可能被丢弃）。当发生任何形式的未送达收件人时，实施必须向发起人发出负面送达状态通知。
The multipart contents defined below MAY be sent as the top level of a VPIM message (with other noted contents below them as required.) As well, the multipart/mixed content SHOULD be used as the top level of a VPIM message to form a more complex structure (e.g., with additional content types). When multiple contents are present, they SHOULD be presented to the user in the order that they appear in the message. Several examples are given in Appendix B.
下面定义的多部分内容可以作为VPIM消息的顶层发送（根据需要在其下方添加其他注释内容）。此外，多部分/混合内容也应该用作VPIM消息的顶层，以形成更复杂的结构（例如，具有附加内容类型）。当存在多个内容时，应按照它们在消息中出现的顺序向用户显示这些内容。附录B中给出了几个示例。
MIME provides the facilities for enclosing several body parts in a single message. Multipart/Mixed SHOULD only be used for sending complex voice or multimedia messages. That is, as the top level Content-Type when sending one of the following contents (in addition to the VPIM voice message) in a VPIM message. Compliant systems MUST accept multipart/mixed body parts. From [MIME2]
MIME提供了在单个消息中封装多个正文部分的功能。Multipart/Mixed只能用于发送复杂的语音或彩信。也就是说，在VPIM消息中发送以下内容之一（除VPIM语音消息外）时，作为顶级内容类型。兼容系统必须接受多部件/混合车身部件。从[MIME2]
MIME requires support of the basic Text/Plain content type. This content type has limited applicability within the voice messaging environment. However, because VPIM is a MIME profile, MIME requirements should be met. Compliant VPIM implementations SHOULD NOT send the Text/Plain content-type. Compliant implementations MUST accept Text/Plain messages, however, specific handling is left as an implementation decision. From [MIME2]
MIME需要支持基本文本/普通内容类型。此内容类型在语音消息环境中的适用性有限。但是，由于VPIM是一个MIME配置文件，因此应该满足MIME要求。兼容的VPIM实现不应发送文本/普通内容类型。兼容的实现必须接受文本/普通消息，但是，具体的处理由实现决定。从[MIME2]
There are several mechanisms that can be used to support text (once accepted) on voice messaging systems including text-to-speech and text-to-fax conversions. If no rendering of the text is possible (i.e., it is not possible for the recipient to determine if the text is a critical part of the message), the entire message MUST be returned to the sender with a negative delivery status notification and a media-unsupported status code.
有几种机制可用于支持语音消息系统上的文本（一旦接受），包括文本到语音和文本到传真的转换。如果无法呈现文本（即，收件人无法确定文本是否为邮件的关键部分），则必须将整个邮件返回给发件人，并附带负面的传递状态通知和媒体不支持的状态代码。
The Multipart/Report is used for enclosing human-readable and machine parsable notification (e.g. Message/delivery-status) body parts and any returned message content. The multipart/report content-type is used to deliver both delivery status reports indicating transport success or failure and message disposition notifications to indicate post-delivery events such as receipt notification. Compliant implementations MUST use the Multipart/Report construct. Compliant implementations MUST recognize and decode the Multipart/Report content type and its components in order to present the report to the user. From [REPORT]
多部分/报告用于封装人类可读和机器可解析的通知（例如消息/传递状态）正文部分和任何返回的消息内容。多部分/报告内容类型用于传递指示传输成功或失败的传递状态报告和指示传递后事件（如接收通知）的消息处置通知。兼容的实现必须使用多部分/报表构造。兼容的实现必须识别和解码多部分/报告内容类型及其组件，以便向用户呈现报告。来自[报告]
Multipart/Report messages from VPIM implementations SHOULD include the human-readable description of the error as a spoken audio/* content (this speech SHOULD also be made available to the notification recipient). As well, VPIM implementations MUST be able to handle (and MAY generate) Multipart/Report messages that encode the human-readable description of the error as text. Note that per [DSN] the human-readable part MUST always be present.
来自VPIM实现的多部分/报告消息应包括可读的错误描述，作为语音/*内容（此语音也应提供给通知接收者）。此外，VPIM实现必须能够处理（并可能生成）多部分/报告消息，这些消息将人类可读的错误描述编码为文本。请注意，根据[DSN]，人类可读部分必须始终存在。
This MIME body part is used for sending machine-parsable delivery status notifications. Compliant implementations MUST use the Message/delivery-status construct when returning messages or sending warnings. Compliant implementations MUST recognize and decode the Message/delivery-status content type and present the reason for failure to the sender of the message. From [DSN]
此MIME正文部分用于发送机器可解析的传递状态通知。在返回消息或发送警告时，兼容实现必须使用消息/传递状态构造。符合要求的实施必须识别和解码邮件/传递状态内容类型，并向邮件发件人说明失败原因。来自[DSN]
This MIME body part is used for sending machine-parsable receipt notification message disposition notifications. Conforming implementations SHOULD use the Message/Disposition-notification construct when sending post-delivery message status notifications. These MDNs, however, MUST only be sent in response to the presence of the Disposition-notification-to header in 4.2.16. Conforming implementations should recognize and decode the Message/Disposition-notification content type and present the notification to the user. From [MDN]
此MIME正文部分用于发送机器可解析接收通知消息处置通知。一致性实现在发送交付后消息状态通知时应使用消息/处置通知结构。但是，这些MDN必须仅在4.2.16中出现处置通知时发送给标头。一致性实施应识别和解码消息/处置通知内容类型，并向用户呈现通知。来自[MDN]
VPIM version 2 explicitly supports the forwarding of voice and fax content with voice or fax annotation. However, only the two constructs described below are acceptable in a VPIM message. Since only the first (i.e. message/rfc822) can be recognized as a forwarded message (or even multiple forwarded messages), it is RECOMMENDED that this construct be used whenever possible.
VPIM版本2明确支持通过语音或传真批注转发语音和传真内容。但是，在VPIM消息中，只有下面描述的两种构造是可接受的。由于只有第一条（即消息/rfc822）可以被识别为转发消息（甚至多条转发消息），因此建议尽可能使用此结构。
Forwarded VPIM messages SHOULD be sent as a multipart/voice-message
with the entire original message enclosed in a message/rfc822 content
type and the annotation as a separate Audio/* or image/* body part.
If the RFC822 header fields are not available for the forwarded
content, simulated header fields with available information SHOULD be
constructed to indicate the original sending timestamp, and the
original sender as indicated in the "From" line. However, note that
at least one of "From", "Subject", or "Date" MUST be present. As
well, the message/rfc822 content MUST include at least the "MIME-
Version", and "Content-Type" header fields. From [MIME2]
Forwarded VPIM messages SHOULD be sent as a multipart/voice-message
with the entire original message enclosed in a message/rfc822 content
type and the annotation as a separate Audio/* or image/* body part.
If the RFC822 header fields are not available for the forwarded
content, simulated header fields with available information SHOULD be
constructed to indicate the original sending timestamp, and the
original sender as indicated in the "From" line. However, note that
at least one of "From", "Subject", or "Date" MUST be present. As
well, the message/rfc822 content MUST include at least the "MIME-
Version", and "Content-Type" header fields. From [MIME2]
In the event that forwarding information is lost through
concatenation of the original message and the forwarding annotation,
such as must be done in a gateway between VPIM and the AMIS voice
messaging protocol, the entire audio content MAY be sent as a single
Audio/* segment without including any forwarding semantics.
In the event that forwarding information is lost through
concatenation of the original message and the forwarding annotation,
such as must be done in a gateway between VPIM and the AMIS voice
messaging protocol, the entire audio content MAY be sent as a single
Audio/* segment without including any forwarding semantics.
Replies to VPIM messages (and Internet mail messages) are addressed to the address noted in the reply-to header (see 4.2.8) if it is present, else the From address (see 4.2.1) is used. The vCard EMAIL attribute, if present, SHOULD be the same as the reply-to address and may be the same as the From address. While the vCard is the senders preferred address it SHOULD NOT be used to generate a reply. Also, the Return-path address should not be used for replies.
VPIM消息（和Internet邮件消息）的回复地址为回复标题（见4.2.8）中注明的地址（如有），否则使用发件人地址（见4.2.1）。vCard电子邮件属性（如果存在）应与回复地址相同，也可能与发件人地址相同。虽然vCard是发件人的首选地址，但不应将其用于生成回复。此外，返回路径地址不应用于回复。
Support of multiple originator header fields is often not possible on voice messaging systems, so it may be necessary to choose only one when gatewaying a VPIM message to another voice message system. However, implementers should note that this may make it impossible to send error messages and replies to their proper destinations.
语音消息系统通常不支持多个发起者报头字段，因此在将VPIM消息网关化到另一个语音消息系统时，可能需要只选择一个。但是，实现者应该注意，这可能会导致无法向正确的目的地发送错误消息和回复。
In some cases, a reply message is not possible, such as with a message created by telephone answering (i.e. classic voice mail). In this case, the From field MUST contain the special address non-mail-user@domain (see 4.1.2). A null ESMTP MAIL FROM address SHOULD also be used in this case (see 5.1.2). A receiving VPIM system SHOULD NOT offer the user the option to reply to this kind of message.
在某些情况下，无法发送回复消息，例如通过电话应答创建的消息（即经典语音邮件）。在这种情况下，“发件人”字段必须包含非邮件的特殊地址-user@domain（见4.1.2）。在这种情况下，还应使用空ESMTP邮件发件人地址（见5.1.2）。接收VPIM系统不应向用户提供回复此类消息的选项。
VPIM delivery status notification messages (4.4.4) MUST be sent to the originator of the message when any form of non-delivery of the subject message or its components occurs. These error messages must be sent to the return path (4.2.6) if present, otherwise, the From (4.2.1) address may be used.
当主题消息或其组件出现任何形式的未交付时，必须将VPIM交付状态通知消息（4.4.4）发送给消息的发起人。这些错误消息必须发送到返回路径（4.2.6）（如果存在），否则，可以使用From（4.2.1）地址。
VPIM Receipt Notification messages (4.4.5) should be sent to the sender specified in the Disposition-Notification-To header field (4.2.16), only after the message has been presented to the recipient or if the message has somehow been disposed of without being presented to the recipient (e.g. if it were deleted before playing it).
VPIM接收通知消息（4.4.5）应仅在消息已呈现给收件人后，或消息已以某种方式被处置而未呈现给收件人（例如，如果在播放之前已将其删除），才发送给处置通知标题字段（4.2.16）中指定的发件人。
VPIM Notification messages may be positive or negative, and can indicate delivery at the server or receipt by the client. However, the notification MUST be contained in a multipart/report container (4.4.3) and SHOULD contain a spoken error message.
VPIM通知消息可以是肯定的，也可以是否定的，可以表示在服务器上的传递或客户端的接收。但是，通知必须包含在多部分/报告容器（4.4.3）中，并应包含语音错误消息。
If a VPIM system receives a message with contents that are not understood (see 4.3 & 4.4), its handling is a local matter. A delivery status notification SHOULD be generated if the message could not be delivered because of unknown contents (e.g., on traditional voice processing systems). In some cases, the message may be delivered (with a positive DSN sent) to a mailbox before the determination of rendering can be made.
如果VPIM系统接收到内容不可理解的消息（见4.3和4.4），则其处理属于本地事务。如果由于未知内容（例如，在传统语音处理系统上）而无法传递邮件，则应生成传递状态通知。在某些情况下，在确定呈现之前，可能会将消息传递（发送肯定的DSN）到邮箱。
Messages are transported between voice mail machines using the Internet Extended Simple Mail Transfer Protocol (ESMTP). All information required for proper delivery of the message is included in the ESMTP dialog. This information, including the sender and recipient addresses, is commonly referred to as the message
消息使用Internet扩展简单邮件传输协议（ESMTP）在语音邮件机之间传输。正确传递消息所需的所有信息都包含在ESMTP对话框中。此信息，包括发件人和收件人地址，通常称为邮件
"envelope". This information is equivalent to the message control block in many analog voice messaging protocols.
“信封”。此信息相当于许多模拟语音消息协议中的消息控制块。
ESMTP is a general-purpose messaging protocol, designed both to send mail and to allow terminal console messaging. Simple Mail Transport Protocol (SMTP) was originally created for the exchange of US-ASCII 7-bit text messages. Binary and 8-bit text messages have traditionally been transported by encoding the messages into a 7-bit text-like form. [ESMTP] formalized an extension mechanism for SMTP, and subsequent RFCs have defined 8-bit text networking, command streaming, binary networking, and extensions to permit the declaration of message size for the efficient transmission of large messages such as multi-minute voice mail.
ESMTP是一种通用消息传递协议，设计用于发送邮件和允许终端控制台消息传递。简单邮件传输协议（SMTP）最初是为交换US-ASCII 7位文本消息而创建的。二进制和8位文本消息传统上是通过将消息编码为7位文本形式来传输的。[ESMTP]正式定义了SMTP的扩展机制，随后的RFC定义了8位文本网络、命令流、二进制网络和扩展，以允许声明消息大小，以便高效传输大型消息，如多分钟语音邮件。
The following sections list ESMTP commands, keywords, and parameters that are required and those that are optional for conformance to this profile.
以下各节列出了符合此配置文件所需的ESMTP命令、关键字和参数，以及可选的ESMTP命令、关键字和参数。
Base SMTP greeting and identification of sender. This command is not to be sent by compliant systems unless the more-capable EHLO command is not accepted. It is included for compatibility with general SMTP implementations. Compliant servers MUST implement the HELO command for backward compatibility but clients SHOULD NOT send it unless EHLO is not supported. From [SMTP]
基本SMTP问候语和发件人标识。除非不接受能力更强的EHLO命令，否则该命令不得由兼容系统发送。包括它是为了与一般SMTP实现兼容。兼容服务器必须实现HELO命令以实现向后兼容性，但除非不支持EHLO，否则客户端不应发送该命令。从[SMTP]
Originating mailbox. This address contains the mailbox to which errors should be sent. VPIM implementations SHOULD use the same address in the MAIL FROM command as is used in the From header field. This address is not necessarily the same as the message Sender listed in the message header fields if the message was received from a gateway or sent to an Internet-style mailing list. From [SMTP, ESMTP]
发起邮箱。此地址包含应向其发送错误的邮箱。VPIM实现应在邮件发件人命令中使用与发件人标头字段中使用的地址相同的地址。如果邮件是从网关接收或发送到Internet邮件列表，则此地址不一定与邮件标题字段中列出的邮件发件人相同。从[SMTP，ESMTP]
The MAIL FROM address SHOULD be stored in the local message store for the purposes of generating a delivery status notification to the originator. The address indicated in the MAIL FROM command SHOULD be passed as a local system parameter or placed in a Return-Path: line inserted at the beginning of a VPIM message. From [HOSTREQ]
邮件发件人地址应存储在本地邮件存储中，以便向发端人生成传递状态通知。MAIL FROM命令中指示的地址应作为本地系统参数传递，或放置在VPIM消息开头插入的返回路径：行中。从[主机请求]
Since delivery status notifications MUST be sent to the MAIL FROM address, the use of the null address ("<>") is often used to prevent looping of messages. This null address MAY be used to note that a particular message has no return path (e.g. a telephone answer
由于传递状态通知必须发送到邮件发件人地址，因此通常使用空地址（“<>”）来防止邮件循环。此空地址可用于说明特定消息没有返回路径（例如电话应答
message). From [SMTP]
信息）。从[SMTP]
Recipient's mailbox. The parameter to this command contains only the address to which the message should be delivered for this transaction. It is the set of addresses in one or more RCPT TO commands that are used for mail routing. From [SMTP, ESMTP]
收件人的邮箱。此命令的参数仅包含此事务的消息应传递到的地址。它是一个或多个RCPT TO命令中用于邮件路由的地址集。从[SMTP，ESMTP]
Note: In the event that multiple transport connections to multiple destination machines are required for the same message, the set of addresses in a given transport connection may not match the list of recipients in the message header fields.
注意：如果同一邮件需要到多个目标计算机的多个传输连接，则给定传输连接中的地址集可能与邮件标题字段中的收件人列表不匹配。
Initiates the transfer of message data. Support for this command is required. Compliant implementations MUST implement the SMTP DATA command for backwards compatibility. From [SMTP]
启动消息数据的传输。需要对该命令的支持。兼容的实现必须实现SMTP数据命令以实现向后兼容性。从[SMTP]
Requests a change-of-roles, that is, the client that opened the connection offers to assume the role of server for any mail the remote machine may wish to send. Because SMTP is not an authenticated protocol, the TURN command presents an opportunity to improperly fetch mail queued for another destination. Compliant implementations SHOULD NOT implement the TURN command. From [SMTP]
请求角色的更改，即打开连接的客户端为远程计算机可能希望发送的任何邮件提供服务器角色。由于SMTP不是经过身份验证的协议，TURN命令提供了一个不正确获取排队等待另一个目标的邮件的机会。兼容的实现不应实现TURN命令。从[SMTP]
Requests that the connection be closed. If accepted, the remote machine will reset and close the connection. Compliant implementations MUST implement the QUIT command. From [SMTP]
请求关闭连接。如果接受，远程机器将重置并关闭连接。兼容的实现必须实现QUIT命令。从[SMTP]
Resets the connection to its initial state. Compliant implementations MUST implement the RSET command. From [SMTP]
将连接重置为其初始状态。兼容的实现必须实现RSET命令。从[SMTP]
Requests verification that this node can reach the listed recipient. While this functionality is also included in the RCPT TO command, VRFY allows the query without beginning a mail transfer transaction. This command is useful for debugging and tracing problems. Compliant implementations MAY implement the VRFY command. From [SMTP] (Note that the implementation of VRFY may simplify the guessing of a
请求验证此节点是否可以到达列出的收件人。虽然此功能也包含在RCPT TO命令中，但VRFY允许在不开始邮件传输事务的情况下进行查询。此命令对于调试和跟踪问题非常有用。兼容的实现可以实现VRFY命令。来自[SMTP]（请注意，VRFY的实现可能简化对
recipient's mailbox or automated sweeps for valid mailbox addresses, resulting in a possible reduction in privacy. Various implementation techniques may be used to reduce the threat, such as limiting the number of queries per session.) From [SMTP]
收件人的邮箱或自动扫描有效邮箱地址，可能会降低隐私。可以使用各种实现技术来减少威胁，例如限制来自[SMTP]的每个会话的查询数
The enhanced mail greeting that enables a server to announce support for extended messaging options. The extended messaging modes are discussed in subsequent sections of this document. Compliant implementations MUST implement the ESMTP command and return the capabilities indicated later in this memo. From [ESMTP]
增强的邮件问候语，使服务器能够宣布对扩展邮件选项的支持。扩展消息传递模式将在本文档的后续章节中讨论。符合要求的实施必须执行ESMTP命令，并返回本备忘录后面所述的功能。来自[ESMTP]
The BDAT command provides a higher efficiency alternative to the earlier DATA command, especially for voice. The BDAT command provides for native binary transport of messages. Compliant implementations SHOULD support binary transport using the BDAT command [BINARY].
BDAT命令提供了比早期数据命令更高效的替代方案，尤其是对于语音。BDAT命令提供消息的本机二进制传输。兼容的实现应该使用BDAT命令[binary]支持二进制传输。
The following ESMTP keywords indicate extended features useful for voice messaging.
以下ESMTP关键字表示对语音消息有用的扩展功能。
The "PIPELINING" keyword indicates ability of the receiving server to accept new commands before issuing a response to the previous command. Pipelining commands dramatically improves performance by reducing the number of round-trip packet exchanges and makes it possible to validate all recipient addresses in one operation. Compliant implementations SHOULD support the command pipelining indicated by this keyword. From [PIPE]
“Pipeline”关键字表示接收服务器在对前一个命令发出响应之前接受新命令的能力。通过减少往返数据包交换的数量，流水线命令显著提高了性能，并使在一次操作中验证所有收件人地址成为可能。兼容的实现应该支持此关键字指示的命令管道。来自[管道]
The "SIZE" keyword provides a mechanism by which the SMTP server can indicate the maximum size message supported. Compliant servers MUST provide size extension to indicate the maximum size message that can be accepted. Clients SHOULD NOT send messages larger than the size indicated by the server. Clients SHOULD advertise SIZE= when sending messages to servers that indicate support for the SIZE extension. From [SIZE]
“SIZE”关键字提供了一种机制，SMTP服务器可以通过该机制指示支持的最大邮件大小。兼容服务器必须提供大小扩展，以指示可接受的最大消息大小。客户端发送的邮件不应大于服务器指示的大小。当向服务器发送指示支持大小扩展的消息时，客户端应公布SIZE=。从[大小]
The "CHUNKING" keyword indicates that the receiver will support the high-performance binary transport mode. Note that CHUNKING can be used with any message format and does not imply support for binary encoded messages. Compliant implementations MAY support binary transport indicated by this capability. From [BINARY]
“CHUNKING”关键字表示接收器将支持高性能二进制传输模式。请注意，分块可以用于任何消息格式，并不意味着支持二进制编码的消息。兼容的实现可能支持此功能指示的二进制传输。来自[二进制]
The "BINARYMIME" keyword indicates that the SMTP server can accept binary encoded MIME messages. Compliant implementations MAY support binary transport indicated by this capability. Note that support for this feature requires support of CHUNKING. From [BINARY]
“BINARYMIME”关键字表示SMTP服务器可以接受二进制编码的MIME消息。兼容的实现可能支持此功能指示的二进制传输。请注意，支持此功能需要支持分块。来自[二进制]
The "DSN" keyword indicates that the SMTP server will accept explicit delivery status notification requests. Compliant implementations MUST support the delivery notification extensions in [DRPT].
“DSN”关键字表示SMTP服务器将接受显式传递状态通知请求。兼容的实现必须支持[DRPT]中的传递通知扩展。
The "ENHANCEDSTATUSCODES" keyword indicates that an SMTP server augments its responses with the enhanced mail system status codes [CODES]. These codes can then be used to provide more informative explanations of error conditions, especially in the context of the delivery status notifications format defined in [DSN]. Compliant implementations SHOULD support this capability. From [STATUS]
“ENHANCEDSTATUSCODES”关键字表示SMTP服务器使用增强的邮件系统状态代码[代码]增强其响应。然后，这些代码可用于提供错误条件的更多信息解释，特别是在[DSN]中定义的交付状态通知格式的上下文中。兼容的实现应该支持此功能。来自[状态]
The current message is a binary encoded MIME messages. Compliant implementations SHOULD support binary transport indicated by this parameter. From [BINARY]
当前消息是二进制编码的MIME消息。兼容的实现应支持此参数指示的二进制传输。来自[二进制]
The RET parameter indicates whether the content of the message should be returned. Compliant systems SHOULD honor a request for returned content. From [DRPT]
RET参数指示是否应返回消息的内容。合规系统应满足返回内容的请求。来自[DRPT]
The ENVID keyword of the SMTP MAIL command is used to specify an "envelope identifier" to be transmitted along with the message and included in any DSNs issued for any of the recipients named in this SMTP transaction. The purpose of the envelope identifier is to allow the sender of a message to identify the transaction for which the DSN was issued. Compliant implementations MAY use this parameter. From [DRPT]
SMTP邮件命令的ENVID关键字用于指定要随邮件一起传输的“信封标识符”，并包含在为此SMTP事务中指定的任何收件人发出的任何DSN中。信封标识符的用途是允许消息发送方识别为其发出DSN的交易。兼容的实现可能会使用此参数。来自[DRPT]
The NOTIFY parameter indicates the conditions under which a delivery report should be sent. Compliant implementations MUST honor this request. From [DRPT]
NOTIFY参数指示应在何种条件下发送交货报告。兼容的实现必须满足此请求。来自[DRPT]
The ORCPT keyword of the RCPT command is used to specify an "original" recipient address that corresponds to the actual recipient to which the message is to be delivered. If the ORCPT esmtp-keyword is used, it MUST have an associated esmtp-value, which consists of the original recipient address, encoded according to the rules below. Compliant implementations MAY use this parameter. From [DRPT]
RCPT命令的ORCPT关键字用于指定一个“原始”收件人地址，该地址对应于邮件要传递到的实际收件人。如果使用ORCPT esmtp关键字，则必须具有关联的esmtp值，该值由原始收件人地址组成，并根据以下规则进行编码。兼容的实现可能会使用此参数。来自[DRPT]
The ESMTP extensions suggested or required for conformance to VPIM fall into two categories. The first category includes features which increase the efficiency of the transport system such as SIZE, BINARYMIME, and PIPELINING. In the event of a downgrade to a less functional transport system, these features can be dropped with no functional change to the sender or recipient.
建议或要求符合VPIM的ESMTP扩展分为两类。第一类包括提高传输系统效率的功能，如大小、二进制MIME和管道。在降级到功能较差的传输系统的情况下，可以在不改变发送方或接收方功能的情况下删除这些功能。
The second category of features are transport extensions in support of new functions. DSN and EnhancedStatusCodes provide essential improvements in the handling of delivery status notifications to bring email to the level of reliability expected of Voice Mail. To ensure a consistent level of service across an intranet or the global Internet, it is essential that VPIM compliant ESMTP support the ESMTP DSN extension at all hops between a VPIM originating system and the recipient system. In the situation where a `downgrade' is unavoidable a relay hop may be forced (by the next hop) to forward a VPIM message without the ESMTP request for positive delivery status notification. It is RECOMMENDED that the downgrading system should continue to attempt to deliver the message, but MUST send an appropriate delivery
第二类功能是支持新功能的传输扩展。DSN和EnhancedStatusCodes在传递状态通知的处理方面提供了必要的改进，使电子邮件达到语音邮件预期的可靠性水平。为了确保跨intranet或全球Internet的一致服务级别，符合VPIM的ESMTP必须在VPIM发起系统和接收方系统之间的所有跃点支持ESMTP DSN扩展。在“降级”不可避免的情况下，中继跳可能会（由下一跳）被强制转发VPIM消息，而无需ESMTP请求积极传递状态通知。建议降级系统继续尝试传递邮件，但必须发送适当的传递
notification to the originator, e.g. the message left an ESMTP host and was sent (unreliably) via SMTP.
通知发端人，例如，邮件离开ESMTP主机，通过SMTP发送（不可靠）。
It is the responsibility of a VPIM system to provide the fully-qualified domain name (FQDN) of the recipient based on the address entered by the user (if the entered address is not already a FQDN). This would typically be an issue on systems that offered only a telephone user interface. The mapping of the dialed target number to a routeable FQDN address allowing delivery to the destination system can be accomplished through implementation-specific means.
VPIM系统负责根据用户输入的地址（如果输入的地址还不是FQDN）提供收件人的完全限定域名（FQDN）。对于只提供电话用户界面的系统来说，这通常是一个问题。拨号目标号码到可路由FQDN地址的映射，允许传送到目标系统，可以通过特定于实现的方式实现。
To facilitate a local dial-by-name cache, an implementation may wish to populate local directories with the first and last names, as well as the address information extracted from received messages. It is mandated that only address information from vCard attachments to VPIM messages be used to populate such a directory when the vCard is available. Addresses or names parsed from the header fields of VPIM messages SHOULD NOT be used to populate directories as it only provides partial data. Alternatively, bilateral agreements could be made to allow the bulk transfer of vCards between systems.
为了便于本地按名称拨号缓存，实现可能希望用名字和姓氏以及从接收到的消息中提取的地址信息填充本地目录。当vCard可用时，只能使用vCard附件至VPIM消息的地址信息来填充此类目录。从VPIM消息头字段解析的地址或名称不应用于填充目录，因为它只提供部分数据。或者，可以签订双边协议，允许在系统之间批量转让vCard。
The use of client/server desktop mailbox protocols like IMAP or POP to retrieve VPIM messages from a IMAP or POP message store is possible without any special modifications to this VPIM specification. Email clients (and web browsers) typically have a table for mapping from MIME type to displaying application. The audio/*, image/tiff and text/directory contents can be configured so that they invoke the correct player/recorder for rendering. In addition with IMAP clients, the first multipart/mixed content (if present) will not appear since it is a generic part. The user instead will be presented with a message that has (for example) audio and image contents.
可以使用客户端/服务器桌面邮箱协议（如IMAP或POP）从IMAP或POP邮件存储中检索VPIM邮件，而无需对此VPIM规范进行任何特殊修改。电子邮件客户端（和web浏览器）通常有一个表，用于从MIME类型映射到显示应用程序。可以配置音频/*、图像/tiff和文本/目录内容，以便调用正确的播放器/录音机进行渲染。除IMAP客户端外，第一个多部分/混合内容（如果存在）将不会出现，因为它是通用部分。相反，用户将看到一条包含（例如）音频和图像内容的消息。
The Internet protocols provide a mechanism for the management of messaging systems, from the management of the physical network through the management of the message queues. SNMP should be supported on a compliant message machine.
Internet协议为消息传递系统的管理提供了一种机制，从物理网络的管理到消息队列的管理。应在兼容的消息计算机上支持SNMP。
The digital interface to the VM and the TCP/IP protocols MAY be managed. MIB II MAY be implemented to provide basic statistics and reporting of TCP and IP protocol performance [MIB II].
可以管理到VM和TCP/IP协议的数字接口。MIB II可用于提供TCP和IP协议性能的基本统计和报告[MIB II]。
VPIM is a messaging application which must be supported in several environments and be supported on differing devices. These environments include traditional voice processing systems, desktop voice messaging systems, store and forward relays, and protocol translation gateways.
VPIM是一种消息传递应用程序，必须在多个环境中受支持，并且在不同的设备上受支持。这些环境包括传统的语音处理系统、桌面语音消息系统、存储转发中继和协议转换网关。
In order to accommodate all environments, this document defines two areas of conformance: transport and content.
为了适应所有环境，本文档定义了两个一致性领域：传输和内容。
Transport conformant systems will pass VPIM messages in a store and forward manner with assured delivery notifications and without the loss of information. It is expected that most store and forward Internet mail based messaging systems will be VPIM transport compliant.
符合传输要求的系统将以存储转发的方式传递VPIM消息，并确保发送通知，且不会丢失信息。预计大多数基于存储和转发Internet邮件的消息传递系统将与VPIM传输兼容。
Content conformant systems will generate and interpret VPIM messages. Conformance in the generation of VPIM messages indicates that the restrictions of this profile are honored. Only contents specified in this profile or extensions agreed to by bilateral agreement may be sent. Conformance in the interpretation of VPIM messages indicates that all VPIM content types and constructs can be received; that all mandatory VPIM content types can be decoded and presented to the recipient in an appropriate manner; and that any unrenderable contents result in the appropriate notification.
符合内容的系统将生成和解释VPIM消息。生成VPIM消息的一致性表明遵守此配置文件的限制。只能发送本简介中规定的内容或经双边协议同意的扩展内容。VPIM消息解释的一致性表明可以接收所有VPIM内容类型和结构；所有强制性VPIM内容类型都可以以适当的方式解码并呈现给收件人；任何不可交代的内容将导致适当的通知。
A summary of the compliance requirements is contained in Appendix A.
合规性要求的摘要包含在附录A中。
VPIM end systems are expected to be both transport and content conformant. They should generate conforming content, reliably send it to the next hop system, receive a message, decode the message and present it to the user. Voice messaging systems and protocol conversion gateways are considered end systems.
VPIM终端系统应同时符合传输和内容要求。他们应该生成一致的内容，可靠地将其发送到下一跳系统，接收消息，解码消息并将其呈现给用户。语音消息系统和协议转换网关被视为终端系统。
Relay systems are expected to be transport compliant in order to receive and send conforming messages. However, they must also create VPIM conforming delivery status notifications in the event of delivery problems.
中继系统应符合传输要求，以便接收和发送符合要求的信息。但是，如果出现交付问题，他们还必须创建符合VPIM的交付状态通知。
Desktop Email clients that support VPIM and are expected to be content conformant. Desktop email clients use various protocols and API's for exchanging messages with the local message store and message transport system. While these clients may benefit from VPIM transport capabilities, specific client-server requirements are out-of-scope for this document.
支持VPIM且符合内容要求的桌面电子邮件客户端。桌面电子邮件客户端使用各种协议和API与本地消息存储和消息传输系统交换消息。虽然这些客户机可能受益于VPIM传输功能，但特定的客户机服务器要求不在本文档的范围内。
This document is a profile of existing Internet mail protocols. To maintain interoperability with Internet mail, any security to be provided should be part of the of the Internet security infrastructure, rather than a new mechanism or some other mechanism outside of the Internet infrastructure.
本文档是现有Internet邮件协议的概要。为了保持与Internet邮件的互操作性，所提供的任何安全性都应该是Internet安全基础架构的一部分，而不是Internet基础架构之外的新机制或其他机制。
Both Internet mail and voice messaging have their own set of threats and countermeasures. As such, this specification does not create any security issues not already existing in the profiled Internet mail and voice mail protocols themselves. This section attends only to the set of additional threats which ensue from integrating the two services.
互联网邮件和语音信息都有自己的威胁和对策。因此，本规范不会产生任何已分析的Internet邮件和语音邮件协议本身不存在的安全问题。本节仅讨论集成这两个服务所带来的一系列附加威胁。
The actual sender of the voice message might not be the same as that specified in the Sender or From header fields of the message content header fields or the MAIL FROM address from the SMTP envelope. In a tightly constrained environment, sufficient physical and software controls may be able to ensure prevention of this problem. In addition, the recognition of the senders voice may provide confidence of the sender's identity irrespective of that specified in Sender or From. It should be recognized that SMTP implementations do not provide inherent authentication of the senders of messages, nor are sites under obligation to provide such authentication.
语音邮件的实际发件人可能与邮件内容标头字段的发件人或发件人标头字段或SMTP信封中的邮件发件人地址中指定的发件人不同。在严格约束的环境中，充分的物理和软件控制可能能够确保防止此问题。此外，对发送者声音的识别可以提供发送者身份的信心，而不考虑发送者中或从中指定的身份。应该认识到，SMTP实现不提供邮件发件人的固有身份验证，站点也没有义务提供此类身份验证。
Assigning an Internet mail address to a voice mailbox opens the possibility of receiving unsolicited messages (either text or voice mail). Traditionally voice mail systems operated in closed environments and were not susceptible to unknown senders. Voice mail users have a higher expectation of mailbox privacy and may consider such messages as a security breach. Many Internet mail systems are choosing to block all messages from unknown sources in an attempt to
将Internet邮件地址分配给语音邮箱可以接收未经请求的邮件（文本邮件或语音邮件）。传统上，语音邮件系统在封闭的环境中运行，不易受到未知发件人的影响。语音邮件用户对邮箱隐私有更高的期望，并且可以将这些消息视为安全漏洞。许多Internet邮件系统都选择阻止来自未知来源的所有邮件，以试图
curb this problem.
遏制这个问题。
Users of voice messaging systems have an expectation of a level of message privacy which is higher than the level provided by Internet mail without security enhancements. This expectation of privacy by users SHOULD be preserved as much as possible.
语音消息系统的用户期望的消息隐私级别高于没有安全增强的Internet邮件提供的级别。应尽可能保留用户对隐私的这种期望。
Sufficient physical and software control may be acceptable in constrained environments. Further, the profile specified in this document does not in any way preclude the use of any Internet object or channel security protocol to encrypt, authenticate, or non-repudiate the messages.
在受限环境中，可以接受充分的物理和软件控制。此外，本文档中指定的配置文件不以任何方式排除使用任何Internet对象或通道安全协议来加密、验证或不可否认消息。
[8BIT] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker, "SMTP Service Extension for 8bit-MIMEtransport", RFC 1426, February 1993.
[8BIT]Klensin，J.，Freed，N.，Rose，M.，Stefferud，E.，和D.Crocker，“8BIT MIMEtransport的SMTP服务扩展”，RFC 1426，1993年2月。
[ADPCM] Vaudreuil, G., and G. Parsons, "Toll Quality Voice - 32 kbit/s ADPCM: MIME Sub-type Registration", RFC 2422, September 1998.
[ADPCM]Vaudreuil，G.和G.Parsons，“收费质量语音-32 kbit/s ADPCM:MIME子类型注册”，RFC 2422，1998年9月。
[AMIS-A] Audio Messaging Interchange Specifications (AMIS) - Analog Protocol Version 1, Issue 2, February 1992.
[AMIS-A]音频消息交换规范（AMIS）-模拟协议第1版，第2期，1992年2月。
[AMIS-D] Audio Messaging Interchange Specifications (AMIS) - Digital Protocol Version 1, Issue 3 August 1993.
[AMIS-D]音频消息交换规范（AMIS）-数字协议第1版，1993年8月3日发行。
[BINARY] Vaudreuil, G., "SMTP Service Extensions for Transmission of Large and Binary MIME Messages", RFC 1830, October 1995.
[BINARY]Vaudreuil，G.“用于传输大型和二进制MIME消息的SMTP服务扩展”，RFC 1830，1995年10月。
[CODES] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, January 1996.
[CODES]Vaudreuil，G.，“增强邮件系统状态代码”，RFC 1893，1996年1月。
[MIMEDIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-Type for Directory Information", RFC 2425, September 1998.
[MIMEDIR]Howes，T.，Smith，M.，和F.Dawson，“目录信息的MIME内容类型”，RFC 24251998年9月。
[DISP] Troost, R., and S. Dorner, "Communicating Presentation Information in Internet Messages: The Content-Disposition Header", RFC 2183, August 1997.
[DISP]Troost，R.和S.Dorner，“在Internet消息中传递表示信息：内容处置头”，RFC 2183，1997年8月。
[DNS1] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[DNS1]Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 1035，1987年11月。
[DNS2] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, November 1987.
[DNS2]Mockapetris，P.，“域名-概念和设施”，STD 13，RFC 1034，1987年11月。
[DRPT] Moore, K., "SMTP Service Extensions for Delivery Status Notifications", RFC 1891, January 1996.
[DRPT]Moore，K.，“传递状态通知的SMTP服务扩展”，RFC 18911996年1月。
[DSN] Moore, K., and G. Vaudreuil, "An Extensible Message Format for Delivery Status Notifications", RFC 1894, January 1996.
[DSN]Moore，K.和G.Vaudreuil，“传递状态通知的可扩展消息格式”，RFC 1894，1996年1月。
[DUR] Vaudreuil, G., and G. Parsons, "Content Duration MIME Header Definition", RFC 2424, September 1998.
[DUR]Vaudreuil，G.和G.Parsons，“内容持续时间MIME头定义”，RFC 24241998年9月。
[E164] CCITT Recommendation E.164 (1991), Telephone Network and ISDN Operation, Numbering, Routing and Mobile Service - Numbering Plan for the ISDN Era.
[E164]CCITT建议E.164（1991），电话网络和ISDN操作，编号，路由和移动服务-ISDN时代的编号计划。
[ESMTP] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker, "SMTP Service Extensions", RFC 1869, November 1995.
[ESMTP]Klensin，J.，Freed，N.，Rose，M.，Stefferud，E.，和D.Crocker，“SMTP服务扩展”，RFC 18691995年11月。
[G726] CCITT Recommendation G.726 (1990), General Aspects of Digital Transmission Systems, Terminal Equipment - 40, 32, 24,16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM).
[G726]CCITT建议G.726（1990），数字传输系统的一般方面，终端设备-40,32,24,16 kbit/s自适应差分脉冲编码调制（ADPCM）。
[HOSTREQ] Braden, R., "Requirements for Internet Hosts -- Application and Support", STD 3, RFC 1123, October 1989.
[HOSTREQ]Braden，R.，“互联网主机的要求——应用和支持”，STD 3，RFC 1123，1989年10月。
[LANG] Alvestrand, H., "Tags for the Identification of Languages", RFC 1766, March 1995.
[LANG]Alvestrand，H.，“语言识别标签”，RFC17661995年3月。
[MDN] Fajman, R., "An Extensible Message Format for Message Disposition Notifications", RFC 2298, March 1998.
[MDN]Fajman，R.，“用于消息处置通知的可扩展消息格式”，RFC22981998年3月。
[MIB II] Rose, M., "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", RFC 1158, May 1990.
[MIB II]Rose，M.，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，RFC 1158，1990年5月。
[MIME1] Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[MIME1]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[MIME2] Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[MIME2]Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第二部分：媒体类型”，RFC 20461996年11月。
[MIME3] Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, November 1996.
[MIME3]Moore，K.，“多用途互联网邮件扩展（MIME）第三部分：非ASCII文本的消息头扩展”，RFC 2047，1996年11月。
[MIME4] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", RFC 2048, November 1996.
[MIME4]Freed，N.，Klensin，J.，和J.Postel，“多用途互联网邮件扩展（MIME）第四部分：注册程序”，RFC 20481996年11月。
[MIME5] Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, November 1996.
[MIME5]Freed，N.和N.Borenstein，“多用途Internet邮件扩展（MIME）第五部分：一致性标准和示例”，RFC 2049，1996年11月。
[PIPE] Freed, N., and A. Cargille, "SMTP Service Extension for Command Pipelining", RFC 1854, October 1995.
[PIPE]Freed，N.和A.Cargille，“用于命令管道的SMTP服务扩展”，RFC 18541995年10月。
[REPORT] Vaudreuil, G., "The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages", RFC 1892, January 1996.
[报告]Vaudreuil，G.“邮件系统管理消息报告的多部分/报告内容类型”，RFC 1892，1996年1月。
[REQ] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[REQ]Bradner，S.，“在RFC中用于指示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC822] Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822, August 1982.
[RFC822]Crocker，D.，“ARPA互联网文本信息格式标准”，STD 11，RFC 822，1982年8月。
[SIZE] Klensin, J., Freed, N., and K. Moore, "SMTP Service Extensions for Message Size Declaration", RFC 1870, November 1995.
[SIZE]Klensin，J.，Freed，N.，和K.Moore，“邮件大小声明的SMTP服务扩展”，RFC 1870，1995年11月。
[SMTP] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821, August 1982.
[SMTP]Postel，J.，“简单邮件传输协议”，STD 10，RFC 8211982年8月。
[STATUS] Freed, N., "SMTP Service Extension for Returning Enhanced Error Codes", RFC 2034, October 1996.
[STATUS]Freed，N.，“用于返回增强错误代码的SMTP服务扩展”，RFC 2034，1996年10月。
[TIFF-F] Parsons, G., and J. Rafferty, "Tag Image File Format: Application F", RFC 2306, March 1998.
[TIFF-F]Parsons，G.和J.Rafferty，“标签图像文件格式：应用程序F”，RFC 2306，1998年3月。
[TIFFREG] Parsons, G., Rafferty, J., and S. Zilles, "Tag Image File Format: image/tiff - MIME sub-type registraion", RFC 2302, March 1998.
[TIFFREG]Parsons，G.，Rafferty，J.，和S.Zilles，“标签图像文件格式：图像/tiff-MIME子类型注册”，RFC 2302，1998年3月。
[V-MSG] Vaudreuil, G., and G. Parsons, "VPIM Voice Message: MIME Sub-type Registration", RFC 2423, September 1998.
[V-MSG]Vaudreuil，G.和G.Parsons，“VPIM语音信息：MIME子类型注册”，RFC 24231998年9月。
[VCARD] Dawson, F., and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998.
[VCARD]Dawson，F.和T.Howes，“VCARD MIME目录配置文件”，RFC24261998年9月。
[VPIM1] Vaudreuil, G., "Voice Profile for Internet Mail", RFC 1911, February 1996.
[VPIM1]Vaudreuil，G.，“互联网邮件的语音模式”，RFC 19111996年2月。
[X.400] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", RFC 1327, May 1992.
[X.400]Hardcastle Kille，S.，“X.400（1988）/ISO 10021和RFC 822之间的映射”，RFC 1327，1992年5月。
The authors would like to offer a special thanks to the Electronic Messaging Association (EMA), especially the members of the Voice Messaging Committee and the VPIM Work Group, for their support of the VPIM specification and the efforts they have made to ensure its success.
作者要特别感谢电子信息协会（EMA），特别是语音信息委员会和VPIM工作组的成员，感谢他们对VPIM规范的支持以及为确保其成功所做的努力。
The EMA hosts the VPIM web page at http://www.ema.org/vpim.
EMA在以下位置托管VPIM网页：http://www.ema.org/vpim.
Glenn W. Parsons Northern Telecom P.O. Box 3511, Station C Ottawa, ON K1Y 4H7 Canada
加拿大K1Y 4H7渥太华C站Glenn W.Parsons Northern Telecom邮政信箱3511
Phone: +1-613-763-7582
Fax: +1-613-763-4461
EMail: Glenn.Parsons@Nortel.ca
Phone: +1-613-763-7582
Fax: +1-613-763-4461
EMail: Glenn.Parsons@Nortel.ca
Gregory M. Vaudreuil Lucent Technologies, Octel Messaging Division 17080 Dallas Parkway Dallas, TX 75248-1905 United States
Gregory M.Vaudreuil-Lucent Technologies，美国德克萨斯州达拉斯市达拉斯大道17080号八进制信息部，邮编75248-1905
Phone/Fax: +1-972-733-2722
EMail: GregV@Lucent.Com
Phone/Fax: +1-972-733-2722
EMail: GregV@Lucent.Com
The following table summarizes the profile of VPIM version 2 detailed in this document. Since in many cases it is not possible to simplify the qualifications for supporting each feature this appendix is informative. The reader is recommended to read the complete explanation of each feature in the referenced section. The text in the previous sections shall be deemed authoritative if any item in this table is ambiguous.
下表总结了本文档中详细介绍的VPIM版本2的配置文件。由于在许多情况下，不可能简化支持每个功能的资格，因此本附录提供了信息。建议读者阅读参考章节中每个功能的完整说明。如果本表中的任何项目不明确，则前几节中的文本应视为权威。
The conformance table is separated into various columns:
一致性表分为不同的列：
Feature - name of protocol feature (note that the indenting indicates a hierarchy of conformance, i.e. the conformance of a lower feature is only relevant if there is conformance to the higher feature)
功能-协议功能的名称（注意，缩进表示一致性的层次结构，即，只有在与较高功能一致时，较低功能的一致性才相关）
Section - reference section in main text of this document
章节-本文件正文中的参考章节
Area - conformance area to which each feature applies: C - content T - transport
区域-每个功能适用的一致性区域：C-内容T-传输
Status - whether the feature is mandatory, optional, or prohibited. The key words used in this table are to be interpreted as described in [REQ], though the following list gives a quick overview of the different degrees of feature conformance: Must - mandatory Should - required in the absence of a compelling need to omit. May - optional Should not - prohibited in the absence of a compelling need. Must not - prohibited
状态-功能是强制的、可选的还是禁止的。本表中使用的关键词应按照[REQ]中所述进行解释，尽管以下列表简要概述了不同程度的功能一致性：必须-必须-必须-需要，在没有迫切需要省略的情况下。在没有迫切需要的情况下，可以-可选-不应该-禁止。不得-禁止
Footnote - special comment about conformance for a particular feature
脚注-关于特定特征一致性的特别注释
VPIM version 2 Conformance
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
| | | | | | | |
Message Addressing Formats: | | | | | | | |
Use DNS host names |4.1 |C|x| | | | |
Use only numbers in mailbox IDs |4.1.1 |C| |x| | | |
Use alpha-numeric mailbox IDs |4.1.1 |C| | |x| | |
Support of postmaster@domain |4.1.2 |C|x| | | | |
Support of non-mail-user@domain |4.1.2 |C| |x| | | |
Support of distribution lists |4.1.3 |C| |x| | | |
| | | | | | | |
Message Header Fields: | | | | | | | |
Encoding outbound messages | | | | | | | |
From |4.2.1 |C|x| | | | |
Addition of text name |4.2.1 |C| |x| | | |
To |4.2.2 |C|x| | | | |1
cc |4.2.3 |C| |x| | | |1
Date |4.2.4 |C|x| | | | |
Sender |4.2.5 |C| | |x| | |
Return-Path |4.2.6 |C| | |x| | |
Message-id |4.2.7 |C|x| | | | |
Reply-To |4.2.8 |C| | | |x| |
Received |4.2.9 |C|x| | | | |
MIME Version: 1.0 (Voice 2.0) |4.2.10 |C| |x| | | |
Content-Type |4.2.11 |C|x| | | | |
Content-Transfer-Encoding |4.2.12 |C|x| | | | |
Sensitivity |4.2.13 |C| | |x| | |
Importance |4.2.14 |C| | |x| | |
Subject |4.2.15 |C| |x| | | |
Disposition-notification-to |4.2.16 |C| | |x| | |
Disposition-notification-options |4.2.17 |C| | |x| | |
Other Headers |4.2 |C| | |x| | |
| | | | | | | |
VPIM version 2 Conformance
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
| | | | | | | |
Message Addressing Formats: | | | | | | | |
Use DNS host names |4.1 |C|x| | | | |
Use only numbers in mailbox IDs |4.1.1 |C| |x| | | |
Use alpha-numeric mailbox IDs |4.1.1 |C| | |x| | |
Support of postmaster@domain |4.1.2 |C|x| | | | |
Support of non-mail-user@domain |4.1.2 |C| |x| | | |
Support of distribution lists |4.1.3 |C| |x| | | |
| | | | | | | |
Message Header Fields: | | | | | | | |
Encoding outbound messages | | | | | | | |
From |4.2.1 |C|x| | | | |
Addition of text name |4.2.1 |C| |x| | | |
To |4.2.2 |C|x| | | | |1
cc |4.2.3 |C| |x| | | |1
Date |4.2.4 |C|x| | | | |
Sender |4.2.5 |C| | |x| | |
Return-Path |4.2.6 |C| | |x| | |
Message-id |4.2.7 |C|x| | | | |
Reply-To |4.2.8 |C| | | |x| |
Received |4.2.9 |C|x| | | | |
MIME Version: 1.0 (Voice 2.0) |4.2.10 |C| |x| | | |
Content-Type |4.2.11 |C|x| | | | |
Content-Transfer-Encoding |4.2.12 |C|x| | | | |
Sensitivity |4.2.13 |C| | |x| | |
Importance |4.2.14 |C| | |x| | |
Subject |4.2.15 |C| |x| | | |
Disposition-notification-to |4.2.16 |C| | |x| | |
Disposition-notification-options |4.2.17 |C| | |x| | |
Other Headers |4.2 |C| | |x| | |
| | | | | | | |
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
Detection & Decoding inbound messages | | | | | | | |
From |4.2.1 |C|x| | | | |
Present text personal name |4.2.1 |C| | |x| | |
To |4.2.2 |C|x| | | | |
cc |4.2.3 |C| | |x| | |
Date |4.2.4 |C|x| | | | |
Conversion of Date to local time |4.2.4 |C| |x| | | |
Sender |4.2.5 |C| | |x| | |
Return-Path |4.2.6 |C| | |x| | |
Message ID |4.2.7 |C|x| | | | |
Reply-To |4.2.8 |C| |x| | | |
Received |4.2.9 |C| | |x| | |
MIME Version: 1.0 (Voice 2.0) |4.2.10 |C| |x| | | |
Content Type |4.2.11 |C|x| | | | |
Content-Transfer-Encoding |4.2.12 |C|x| | | | |
Sensitivity |4.2.13 |C|x| | | | |2
Importance |4.2.14 |C| | |x| | |
Subject |4.2.15 |C| | |x| | |
Disposition-notification-to |4.2.16 |C| | |x| | |
Disposition-notification-options |4.2.17 |C| | |x| | |
Other Headers |4.2 |C|x| | | | |3
| | | | | | | |
Message Content Encoding: | | | | | | | |
Encoding outbound audio/fax contents | | | | | | | |
7BIT |4.3 |C| | | | |x|
8BIT |4.3 |C| | | | |x|
Quoted Printable |4.3 |C| | | | |x|
Base64 |4.3 |C|x| | | | |4
Binary |4.3 |C| |x| | | |5
Detection & decoding inbound messages | | | | | | | |
7BIT |4.3 |C|x| | | | |
8BIT |4.3 |C|x| | | | |
Quoted Printable |4.3 |C|x| | | | |
Base64 |4.3 |C|x| | | | |
Binary |4.3 |C|x| | | | |5
| | | | | | | |
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
Detection & Decoding inbound messages | | | | | | | |
From |4.2.1 |C|x| | | | |
Present text personal name |4.2.1 |C| | |x| | |
To |4.2.2 |C|x| | | | |
cc |4.2.3 |C| | |x| | |
Date |4.2.4 |C|x| | | | |
Conversion of Date to local time |4.2.4 |C| |x| | | |
Sender |4.2.5 |C| | |x| | |
Return-Path |4.2.6 |C| | |x| | |
Message ID |4.2.7 |C|x| | | | |
Reply-To |4.2.8 |C| |x| | | |
Received |4.2.9 |C| | |x| | |
MIME Version: 1.0 (Voice 2.0) |4.2.10 |C| |x| | | |
Content Type |4.2.11 |C|x| | | | |
Content-Transfer-Encoding |4.2.12 |C|x| | | | |
Sensitivity |4.2.13 |C|x| | | | |2
Importance |4.2.14 |C| | |x| | |
Subject |4.2.15 |C| | |x| | |
Disposition-notification-to |4.2.16 |C| | |x| | |
Disposition-notification-options |4.2.17 |C| | |x| | |
Other Headers |4.2 |C|x| | | | |3
| | | | | | | |
Message Content Encoding: | | | | | | | |
Encoding outbound audio/fax contents | | | | | | | |
7BIT |4.3 |C| | | | |x|
8BIT |4.3 |C| | | | |x|
Quoted Printable |4.3 |C| | | | |x|
Base64 |4.3 |C|x| | | | |4
Binary |4.3 |C| |x| | | |5
Detection & decoding inbound messages | | | | | | | |
7BIT |4.3 |C|x| | | | |
8BIT |4.3 |C|x| | | | |
Quoted Printable |4.3 |C|x| | | | |
Base64 |4.3 |C|x| | | | |
Binary |4.3 |C|x| | | | |5
| | | | | | | |
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
Message Content Types: | | | | | | | |
Inclusion in outbound messages | | | | | | | |
Multipart/Voice-Message |4.3.1 |C|x| | | | |
Message/RFC822 |4.3.2 |C| | |x| | |
Text/Directory |4.3.3 |C| |x| | | |
include TEL, EMAIL, VERSION |4.3.3 |C|x| | | | |
include ROLE, SOUND, N, REV |4.3.3 |C| |x| | | |
only one voice type per level |4.3.3 |C|x| | | | |
Audio/32KADPCM |4.3.4 |C|x| | | | |
Content-Description |4.3.4.1 |C| | |x| | |
Content-Disposition |4.3.4.2 |C|x| | | | |
Content-Duration |4.3.4.3 |C| | |x| | |
Content-Langauge |4.3.4.4 |C| | |x| | |
Image/tiff; application=faxbw |4.3.5 |C| | |x| | |
Audio/* or Image/* (other encodings) |4.3.6 |C| | |x| | |
Multipart/Mixed |4.4.1 |C| | |x| | |
Text/plain |4.4.2 |C| | | |x| |
Multipart/Report |4.4.3 |C|x| | | | |
human-readable part is voice |4.4.3 |C| |x| | | |
human-readable part is text |4.4.3 |C| | |x| | |
Message/delivery-status |4.4.4 |C|x| | | | |
Message/disposition-notification |4.4.5 |C| |x| | | |
Other contents |4.4 |C| | | |x| |6
| | | | | | | |
Detection & decoding in inbound messages | | | | | | | |
Multipart/Voice-Message |4.3.1 |C|x| | | | |
Message/RFC822 |4.3.2 |C|x| | | | |
Text/Directory |4.3.3 |C| |x| | | |
recognize TEL, EMAIL, VERSION |4.3.3 |C|x| | | | |
recognize ROLE, SOUND, N, REV |4.3.3 |C| |x| | | |
Audio/32KADPCM |4.3.4 |C|x| | | | |
Content-Description |4.3.4.1 |C| | |x| | |
Content-Disposition |4.3.4.2 |C| |x| | | |
Content-Duration |4.3.4.3 |C| | |x| | |
Content-Langauge |4.3.4.4 |C| | |x| | |
Image/tiff; application=faxbw |4.3.5 |C| |x| | | |
send NDN if unable to render |4.3.5 |C|x| | | | |7
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
Message Content Types: | | | | | | | |
Inclusion in outbound messages | | | | | | | |
Multipart/Voice-Message |4.3.1 |C|x| | | | |
Message/RFC822 |4.3.2 |C| | |x| | |
Text/Directory |4.3.3 |C| |x| | | |
include TEL, EMAIL, VERSION |4.3.3 |C|x| | | | |
include ROLE, SOUND, N, REV |4.3.3 |C| |x| | | |
only one voice type per level |4.3.3 |C|x| | | | |
Audio/32KADPCM |4.3.4 |C|x| | | | |
Content-Description |4.3.4.1 |C| | |x| | |
Content-Disposition |4.3.4.2 |C|x| | | | |
Content-Duration |4.3.4.3 |C| | |x| | |
Content-Langauge |4.3.4.4 |C| | |x| | |
Image/tiff; application=faxbw |4.3.5 |C| | |x| | |
Audio/* or Image/* (other encodings) |4.3.6 |C| | |x| | |
Multipart/Mixed |4.4.1 |C| | |x| | |
Text/plain |4.4.2 |C| | | |x| |
Multipart/Report |4.4.3 |C|x| | | | |
human-readable part is voice |4.4.3 |C| |x| | | |
human-readable part is text |4.4.3 |C| | |x| | |
Message/delivery-status |4.4.4 |C|x| | | | |
Message/disposition-notification |4.4.5 |C| |x| | | |
Other contents |4.4 |C| | | |x| |6
| | | | | | | |
Detection & decoding in inbound messages | | | | | | | |
Multipart/Voice-Message |4.3.1 |C|x| | | | |
Message/RFC822 |4.3.2 |C|x| | | | |
Text/Directory |4.3.3 |C| |x| | | |
recognize TEL, EMAIL, VERSION |4.3.3 |C|x| | | | |
recognize ROLE, SOUND, N, REV |4.3.3 |C| |x| | | |
Audio/32KADPCM |4.3.4 |C|x| | | | |
Content-Description |4.3.4.1 |C| | |x| | |
Content-Disposition |4.3.4.2 |C| |x| | | |
Content-Duration |4.3.4.3 |C| | |x| | |
Content-Langauge |4.3.4.4 |C| | |x| | |
Image/tiff; application=faxbw |4.3.5 |C| |x| | | |
send NDN if unable to render |4.3.5 |C|x| | | | |7
Audio/* or Image/* (other encodings) |4.3.6 |C| | |x| | |
Multipart/Mixed |4.4.1 |C|x| | | | |
Text/plain |4.4.2 |C|x| | | | |
send NDN if unable to render |4.4.2 |C|x| | | | |
Audio/* or Image/* (other encodings) |4.3.6 |C| | |x| | |
Multipart/Mixed |4.4.1 |C|x| | | | |
Text/plain |4.4.2 |C|x| | | | |
send NDN if unable to render |4.4.2 |C|x| | | | |
| | | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
------------------------------------------|-----------|-|-|-|-|-|-|-
| | | | | | | |
Multipart/Report |4.4.3 |C|x| | | | |
human-readable part is voice |4.4.3 |C| |x| | | |
human-readable part is text |4.4.3 |C|x| | | | |
Message/delivery-status |4.4.4 |C|x| | | | |
Message/disposition-notification |4.4.5 |C| |x| | | |
Other contents |4.4 |C| | | |x| |6
send NDN if unable to render |4.4 |C| |x| | | |
| | | | | | | |
Forwarded Messages | | | | | | | |
use Message/RFC822 construct |4.5 |C| |x| | | |
simulate headers if none available |4.5 |C| |x| | | |
| | | | | | | |
Reply Messages | | | | | | | |
send to Reply-to, else From address |4.6 |C|x| | | | |
do not send to non-mail-user |4.6 |C|x| | | | |
| | | | | | | |
Notifications | | | | | | | |
use multipart/report format |4.7 |C|x| | | | |
always send error on non-delivery |4.7 |C| |x| | | |
| | | | | | | |
Message Transport Protocol: | | | | | | | |
ESMTP Commands | | | | | | | |
HELO |5.1.1 |T|x| | | | |
MAIL FROM |5.1.2 |T|x| | | | |
support null address |5.1.2 |T|x| | | | |
RCPT TO |5.1.3 |T|x| | | | |
DATA |5.1.4 |T|x| | | | |
TURN |5.1.5 |T| | | | |x|
QUIT |5.1.6 |T|x| | | | |
RSET |5.1.7 |T|x| | | | |
VRFY |5.1.8 |T| | |x| | |
EHLO |5.1.9 |T|x| | | | |
BDAT |5.1.10 |T| | |x| | |5
| | | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
------------------------------------------|-----------|-|-|-|-|-|-|-
| | | | | | | |
Multipart/Report |4.4.3 |C|x| | | | |
human-readable part is voice |4.4.3 |C| |x| | | |
human-readable part is text |4.4.3 |C|x| | | | |
Message/delivery-status |4.4.4 |C|x| | | | |
Message/disposition-notification |4.4.5 |C| |x| | | |
Other contents |4.4 |C| | | |x| |6
send NDN if unable to render |4.4 |C| |x| | | |
| | | | | | | |
Forwarded Messages | | | | | | | |
use Message/RFC822 construct |4.5 |C| |x| | | |
simulate headers if none available |4.5 |C| |x| | | |
| | | | | | | |
Reply Messages | | | | | | | |
send to Reply-to, else From address |4.6 |C|x| | | | |
do not send to non-mail-user |4.6 |C|x| | | | |
| | | | | | | |
Notifications | | | | | | | |
use multipart/report format |4.7 |C|x| | | | |
always send error on non-delivery |4.7 |C| |x| | | |
| | | | | | | |
Message Transport Protocol: | | | | | | | |
ESMTP Commands | | | | | | | |
HELO |5.1.1 |T|x| | | | |
MAIL FROM |5.1.2 |T|x| | | | |
support null address |5.1.2 |T|x| | | | |
RCPT TO |5.1.3 |T|x| | | | |
DATA |5.1.4 |T|x| | | | |
TURN |5.1.5 |T| | | | |x|
QUIT |5.1.6 |T|x| | | | |
RSET |5.1.7 |T|x| | | | |
VRFY |5.1.8 |T| | |x| | |
EHLO |5.1.9 |T|x| | | | |
BDAT |5.1.10 |T| | |x| | |5
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
| | | | | | | |
ESMTP Keywords & Parameters | | | | | | | |
PIPELINING |5.2.1 |T| |x| | | |
SIZE |5.2.2 |T|x| | | | |
CHUNKING |5.2.3 |T| | |x| | |
BINARYMIME |5.2.4,5.3.1|T| | |x| | |
DSN |5.2.5 |T|x| | | | |
ENHANCEDSTATUSCODES |5.2.6 |T| |x| | | |
RET |5.3.2 |T| |x| | | |
ENVID |5.3.3 |T| | |x| | |
NOTIFY |5.4.1 |T|x| | | | |
ORCPT |5.4.2 |T| | |x| | |
| | | | | | | |
ESMTP-SMTP Downgrading | | | | | | | |
send delivery report upon downgrade |
| | | | | | | |
Directory Address Resolution | | | | | | | |
provide facility to resolve addresses |6 |C| |x| | | |
use vCards to populate local directory |6 |C| |x| | | |8
use headers to populate local directory |6 |C| | | |x| |
| | | | | | | |
Management Protocols: | | | | | | | |
Network management |8.1 |T| ||x| | |
-------------------------------------------|----------|-|-|-|-|-|-|-
| | | | |S| |
| | | | | |H| |F
| | | | | |O|M|o
| | | |S| |U|U|o
| | | |H| |L|S|t
| |A|M|O| |D|T|n
| |R|U|U|M| | |o
| |E|S|L|A|N|N|t
| |A|T|D|Y|O|O|t
FEATURE |SECTION | | | | |T|T|e
-------------------------------------------|----------|-|-|-|-|-|-|-
| | | | | | | |
ESMTP Keywords & Parameters | | | | | | | |
PIPELINING |5.2.1 |T| |x| | | |
SIZE |5.2.2 |T|x| | | | |
CHUNKING |5.2.3 |T| | |x| | |
BINARYMIME |5.2.4,5.3.1|T| | |x| | |
DSN |5.2.5 |T|x| | | | |
ENHANCEDSTATUSCODES |5.2.6 |T| |x| | | |
RET |5.3.2 |T| |x| | | |
ENVID |5.3.3 |T| | |x| | |
NOTIFY |5.4.1 |T|x| | | | |
ORCPT |5.4.2 |T| | |x| | |
| | | | | | | |
ESMTP-SMTP Downgrading | | | | | | | |
send delivery report upon downgrade |
| | | | | | | |
Directory Address Resolution | | | | | | | |
provide facility to resolve addresses |6 |C| |x| | | |
use vCards to populate local directory |6 |C| |x| | | |8
use headers to populate local directory |6 |C| | | |x| |
| | | | | | | |
Management Protocols: | | | | | | | |
Network management |8.1 |T| ||x| | |
-------------------------------------------|----------|-|-|-|-|-|-|-
Footnotes:
脚注：
1. MUST NOT include if all recipients are not known or resolvable. 2. If a sensitive message is received by a system that does not support sensitivity, then it MUST be returned to the originator with an appropriate error notification. Also, a received sensitive message MUST NOT be forwarded to anyone. 3. If the addtional header fields are not understood they MAY be ignored 4. When binary transport is not available 5. When binary transport is available
1. 如果所有收件人都未知或无法解决，则不得包括。2.如果不支持敏感度的系统接收到敏感消息，则必须将其返回给发起人，并发出相应的错误通知。此外，收到的敏感信息不得转发给任何人。3.如果不理解附加标题字段，则可以忽略它们4。当二进制传输不可用时5。当二进制传输可用时
6. Other un-profiled contents must only be sent by bilateral agreement. 7. If the content cannot be presented in some form, the entire message MUST be returned with a negative delivery status notification. 8. When the vCard is present in a message
6. 其他非概要内容只能通过双边协议发送。7.如果无法以某种形式呈现内容，则必须返回整个邮件，并发出负面传递状态通知。8.当vCard出现在消息中时
The following message is a full-featured message addressed to two recipients. The message includes the sender's spoken name and a short speech segment. The message is marked as important and private.
以下消息是一条功能齐全的消息，发送给两位收件人。该消息包括发送者的口头姓名和简短的语音片段。该消息被标记为重要和私有。
To: +19725551212@vm1.mycompany.com
To: +16135551234@VM1.mycompany.com
From: "Parsons, Glenn" <12145551234@VM2.mycompany.com>
Date: Mon, 26 Aug 93 10:20:20 -0700 (CDT)
MIME-Version: 1.0 (Voice 2.0)
Content-type: Multipart/Voice-Message; Version=2.0;
Boundary="MessageBoundary"
Content-Transfer-Encoding: 7bit
Message-ID: 123456789@VM2.mycompany.com
Sensitivity: Private
Importance: High
To: +19725551212@vm1.mycompany.com
To: +16135551234@VM1.mycompany.com
From: "Parsons, Glenn" <12145551234@VM2.mycompany.com>
Date: Mon, 26 Aug 93 10:20:20 -0700 (CDT)
MIME-Version: 1.0 (Voice 2.0)
Content-type: Multipart/Voice-Message; Version=2.0;
Boundary="MessageBoundary"
Content-Transfer-Encoding: 7bit
Message-ID: 123456789@VM2.mycompany.com
Sensitivity: Private
Importance: High
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Disposition: inline; voice=Originator-Spoken-Name
Content-Language: en-US
Content-ID: part1@VM2-4321
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Disposition: inline; voice=Originator-Spoken-Name
Content-Language: en-US
Content-ID: part1@VM2-4321
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadasssdasddasdasd (This is a sample of the base-64 Spoken Name data) fgdhgddlkgpokpeowrit09==
GLSLFDSLSERTIFLKTPFPGKTPORTPKTPFGTPOITPDADASSDADSDASD（这是base-64语音名称数据的示例）FGDHGDDLKGPOOKPEOWRIT09==
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Description: Brand X Voice Message
Content-Disposition: inline; voice=Voice-Message; filename=msg1.726
Content-Duration: 25
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Description: Brand X Voice Message
Content-Disposition: inline; voice=Voice-Message; filename=msg1.726
Content-Duration: 25
iIiIiIjMzN3czdze3s7d7fwfHhcvESJVe/4yEhLz8/FOQjVFRERCESL/zqrq
(This is a sample of the base64 message data) zb8tFdLTQt1PXj
u7wjOyRhws+krdns7Rju0t4tLF7cE0K0MxOTOnRW/Pn30c8uHi9==
iIiIiIjMzN3czdze3s7d7fwfHhcvESJVe/4yEhLz8/FOQjVFRERCESL/zqrq
(This is a sample of the base64 message data) zb8tFdLTQt1PXj
u7wjOyRhws+krdns7Rju0t4tLF7cE0K0MxOTOnRW/Pn30c8uHi9==
--MessageBoundary
Content-type: text/directory; charset=us-ascii; profile=vCard
Content-Transfer-Encoding: 7bit
--MessageBoundary
Content-type: text/directory; charset=us-ascii; profile=vCard
Content-Transfer-Encoding: 7bit
BEGIN:VCARD
N:Parsons;Glenn;;Mr.;
EMAIL;TYPE=INTERNET:+12145551234@VM2.mycompany.com
TEL:+1-217-555-1234
BEGIN:VCARD
N:Parsons;Glenn;;Mr.;
EMAIL;TYPE=INTERNET:+12145551234@VM2.mycompany.com
TEL:+1-217-555-1234
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part1@VM2-4321>
REV:19951031T222710Z
VERSION: 3.0
END:VCARD
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part1@VM2-4321>
REV:19951031T222710Z
VERSION: 3.0
END:VCARD
--MessageBoundary_
--消息边界_
The following message is a forwarded single segment voice. Both the forwarded message and the forwarding message contain VCARDs with spoken names.
以下消息是转发的单段语音。转发消息和转发消息都包含带有语音名称的vCard。
To: +12145551212@vm1.mycompany.com
From: "Vaudreuil, Greg" <+19725552345@VM2.mycompany.com>
Date: Mon, 26 Aug 93 10:20:20 -0700 (CDT)
MIME-Version: 1.0 (Voice 2.0)
Content-type: Multipart/Voice-Message; Version=2.0;
Boundary="MessageBoundary"
Content-Transfer-Encoding: 7bit
Message-ID: ABCD-123456789@VM2.mycompany.com
To: +12145551212@vm1.mycompany.com
From: "Vaudreuil, Greg" <+19725552345@VM2.mycompany.com>
Date: Mon, 26 Aug 93 10:20:20 -0700 (CDT)
MIME-Version: 1.0 (Voice 2.0)
Content-type: Multipart/Voice-Message; Version=2.0;
Boundary="MessageBoundary"
Content-Transfer-Encoding: 7bit
Message-ID: ABCD-123456789@VM2.mycompany.com
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Disposition: inline; voice=Originator-Spoken-Name
Content-Language: en-US
Content-ID: part3@VM2-4321
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Disposition: inline; voice=Originator-Spoken-Name
Content-Language: en-US
Content-ID: part3@VM2-4321
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadasssdasddasdasd (This is a sample of the base-64 Spoken Name data) fgdhgd dlkgpokpeowrit09==
GLSLFDSLSERTIFLKTFPGTPGKTPORTPKTPFGTPOITPDADASSDASD（这是base-64语音名称数据的示例）fgdhgd DLKGPOOKPEOWRIT09==
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Description: Forwarded Message Annotation
Content-Disposition: inline; voice=Voice-Message
Content-Transfer-Encoding: Base64
--MessageBoundary
Content-type: Audio/32KADPCM
Content-Description: Forwarded Message Annotation
Content-Disposition: inline; voice=Voice-Message
Content-Transfer-Encoding: Base64
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadasssdasddasdasd (This is the voiced introductory remarks encoded in base64) jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gQ5tkjpokfgW dlkgpokpeowrit09==
GLSLFDSLSERTIFLKTFPGKTPORTPKTPFGTPOITPDADASSDASD（这是以base64编码的有声介绍性评论）jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gQ5tkjpokfgW DLKGPOPKPEOWRIT09==
--MessageBoundary Content-type: Message/RFC822 Content-Transfer-Encoding: 7bit
--MessageBoundary内容类型：Message/RFC822内容传输编码：7bit
To: +19725552345@VM2.mycompany.com
To: +19725552345@VM2.mycompany.com
From: "Parsons, Glenn, W." <+16135551234@VM1.mycompany.com>
Date: Mon, 26 Aug 93 8:23:10 -0500 (EST)
Content-type: Multipart/Voice-Message; Version=2.0;
Boundary="MessageBoundary2"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Voice 2.0)
From: "Parsons, Glenn, W." <+16135551234@VM1.mycompany.com>
Date: Mon, 26 Aug 93 8:23:10 -0500 (EST)
Content-type: Multipart/Voice-Message; Version=2.0;
Boundary="MessageBoundary2"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Voice 2.0)
--MessageBoundary2
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Disposition: inline; voice=Originator-Spoken-Name
Content-Language: en-US
Content-ID: part6@VM2-4321
--MessageBoundary2
Content-type: Audio/32KADPCM
Content-Transfer-Encoding: Base64
Content-Disposition: inline; voice=Originator-Spoken-Name
Content-Language: en-US
Content-ID: part6@VM2-4321
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadasssdasddasdasd (This is a sample of the base-64 Spoken Name data) fgdhgd dlkgpokpeowrit09==
GLSLFDSLSERTIFLKTFPGTPGKTPORTPKTPFGTPOITPDADASSDASD（这是base-64语音名称数据的示例）fgdhgd DLKGPOOKPEOWRIT09==
--MessageBoundary2
Content-type: Audio/32KADPCM
Content-Disposition: inline; voice=Voice-Message
Content-Transfer-Encoding: Base64
--MessageBoundary2
Content-type: Audio/32KADPCM
Content-Disposition: inline; voice=Voice-Message
Content-Transfer-Encoding: Base64
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadasssdasddasdasd (This is the original message audio data) fgwersdfmniwrjj jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gQ5tkjpokfgW dlkgpokpeowrit09==
GLSLFDSLSERTIFLKTFPGKTPORTPKTPFGTPOITPDADASSDADSDASD（这是原始消息音频数据）FGWERSDFMNIWRJJRGOIJ3O45ITJ09FIUVDKJGWLAKGQ93IJKPOKFPGOKQ90GQ5TKJPOKFGW dlkgpokpeowrit09==
--MessageBoundary2
Content-type: text/directory; charset=us-ascii
Content-Transfer-Encoding: 7bit
--MessageBoundary2
Content-type: text/directory; charset=us-ascii
Content-Transfer-Encoding: 7bit
BEGIN:VCARD
N:Parsons;Glenn;W;Mr.;
EMAIL;TYPE=INTERNET:+16135551234@VM2.mycompany.com
TEL:+1-613-555-1234
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part6@VM2-4321>
REV:19951031T222710Z
END:VCARD
BEGIN:VCARD
N:Parsons;Glenn;W;Mr.;
EMAIL;TYPE=INTERNET:+16135551234@VM2.mycompany.com
TEL:+1-613-555-1234
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part6@VM2-4321>
REV:19951031T222710Z
END:VCARD
--MessageBoundary2--
--消息边界2--
--MessageBoundary
Content-type: text/directory; charset=us-ascii
Content-Transfer-Encoding: 7bit
--MessageBoundary
Content-type: text/directory; charset=us-ascii
Content-Transfer-Encoding: 7bit
BEGIN:VCARD
N:Vaudreuil;Greg;;Mr.;
BEGIN:VCARD
N:Vaudreuil;Greg;;Mr.;
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part3@VM2-4321>
EMAIL;TYPE=INTERNET,VPIM:+19725552345@VM2.mycompany.com
TEL:+1-972-555-2345
REV:19951031T222710Z
VERSION: 3.0
END:VCARD
SOUND;TYPE=32KADPCM;ENCODING=URI: CID:<part3@VM2-4321>
EMAIL;TYPE=INTERNET,VPIM:+19725552345@VM2.mycompany.com
TEL:+1-972-555-2345
REV:19951031T222710Z
VERSION: 3.0
END:VCARD
--MessageBoundary--
--消息边界--
The following example is for a message returned to the sender by a VPIM gateway at VM1.company.com for a mailbox which does not exist.
以下示例适用于VM1.company.com上的VPIM网关为不存在的邮箱返回给发件人的邮件。
Date: Thu, 7 Jul 1994 17:16:05 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@vm.company.com>
Message-Id: <199407072116.RAA14128@vm1.company.com>
Subject: Returned voice message
To: 2175552345@VM2.mycompany.com
MIME-Version: 1.0 (Voice 2.0)
Content-Type: multipart/report; report-type=delivery-status;
boundary="RAA14128.773615765/VM1.COMPANY.COM"
Date: Thu, 7 Jul 1994 17:16:05 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@vm.company.com>
Message-Id: <199407072116.RAA14128@vm1.company.com>
Subject: Returned voice message
To: 2175552345@VM2.mycompany.com
MIME-Version: 1.0 (Voice 2.0)
Content-Type: multipart/report; report-type=delivery-status;
boundary="RAA14128.773615765/VM1.COMPANY.COM"
--RAA14128.773615765/VM1.COMPANY.COM
Content-type: Audio/32KADPCM
Content-Description: Spoken Delivery Status Notification
Content-Disposition: inline; voice= Voice-Message-Notification
Content-Transfer-Encoding: Base64
--RAA14128.773615765/VM1.COMPANY.COM
Content-type: Audio/32KADPCM
Content-Description: Spoken Delivery Status Notification
Content-Disposition: inline; voice= Voice-Message-Notification
Content-Transfer-Encoding: Base64
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadadffsssddasdasd (This is a voiced description of the error in base64) jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gdffkjpokfgW dlkgpokpeowrit09==
GLSLFDSLSERTIFLKTFPGKTPORTPKTPFGTPOITPDADFFSSSDADSDASSD（这是base64中错误的语音描述）jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gdffkjpokfgW DLKGPOOKPEWRIT09==
--RAA14128.773615765/VM1.COMPANY.COM Content-type: message/delivery-status
--RAA14128.773615765/VM1.COMPANY.COM内容类型：消息/传递状态
Reporting-MTA: dns; vm1.company.com
报告MTA:dns；vm1.company.com
Original-Recipient: rfc822; 2145551234@VM1.mycompany.com
Final-Recipient: rfc822; 2145551234@VM1.mycompany.com
Action: failed
Status: 5.1.1 (User does not exist)
Diagnostic-Code: smtp; 550 Mailbox not found
Last-Attempt-Date: Thu, 7 Jul 1994 17:15:49 -0400
Original-Recipient: rfc822; 2145551234@VM1.mycompany.com
Final-Recipient: rfc822; 2145551234@VM1.mycompany.com
Action: failed
Status: 5.1.1 (User does not exist)
Diagnostic-Code: smtp; 550 Mailbox not found
Last-Attempt-Date: Thu, 7 Jul 1994 17:15:49 -0400
--RAA14128.773615765/VM1.COMPANY.COM content-type: message/rfc822
--RAA14128.773615765/VM1.COMPANY.COM内容类型：message/rfc822
[original VPIM message goes here]
[此处显示原始VPIM消息]
--RAA14128.773615765/VM1.COMPANY.COM--
--RAA14128.773615765/VM1.COMPANY.COM--
The following example is for a receipt notification sent to the original sender for a message which has been played. This delivered VPIM message was received by a corporate gateway and relayed to a unified mailbox.
以下示例适用于发送给原始发件人的已播放邮件的接收通知。此已传递的VPIM消息由公司网关接收并转发到统一邮箱。
Date: Thu, 7 Jul 1994 17:16:05 -0400
From: "Greg Vaudreuil" <22722@vm.company.com>
Message-Id: <199407072116.RAA14128@exchange.company.com>
Subject: Voice message played
To: 2175552345@VM2.mycompany.com
MIME-Version: 1.0 (Voice 2.0)
Content-Type: multipart/report;
Report-type=disposition-notification;
Boundary="RAA14128.773615765/EXCHANGE.COMPANY.COM"
Date: Thu, 7 Jul 1994 17:16:05 -0400
From: "Greg Vaudreuil" <22722@vm.company.com>
Message-Id: <199407072116.RAA14128@exchange.company.com>
Subject: Voice message played
To: 2175552345@VM2.mycompany.com
MIME-Version: 1.0 (Voice 2.0)
Content-Type: multipart/report;
Report-type=disposition-notification;
Boundary="RAA14128.773615765/EXCHANGE.COMPANY.COM"
--RAA14128.773615765/EXCHANGE.COMPANY.COM
Content-type: Audio/32KADPCM
Content-Description: Spoken Disposition Notification
Content-Disposition: inline; voice= Voice-Message-Notification
Content-Transfer-Encoding: Base64
--RAA14128.773615765/EXCHANGE.COMPANY.COM
Content-type: Audio/32KADPCM
Content-Description: Spoken Disposition Notification
Content-Disposition: inline; voice= Voice-Message-Notification
Content-Transfer-Encoding: Base64
glslfdslsertiflkTfpgkTportrpkTpfgTpoiTpdadadffsssddasdasd (Voiced description of the disposition action in base64) jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gdffkjpokfgW dlkgpokpeowrit09==
GLSLFDSLSERTIFLKTFPGKT端口RPKTPFGTPOITPDADFFSSSDADSDASSD（base64中处置行动的语音描述）jrgoij3o45itj09fiuvdkjgWlakgQ93ijkpokfpgokQ90gdffkjpokfgW DLKGPOPOKPEO09==
--RAA14128.773615765/EXCHANGE.COMPANY.COM Content-type: message/disposition-notification
--RAA14128.773615765/EXCHANGE.COMPANY.COM内容类型：消息/处置通知
Reporting-UA: gregs-laptop.dallas.company.com (Unified FooMail 3.0)
报告UA:gregs-laptop.dallas.company.com（Unified FooMail 3.0）
Original-Recipient: rfc822;22722@vm.company.com
Final-Recipient: rfc822;Greg.Vaudreuil@foomail.company.com
Original-Message-ID: <199509192301.12345@vm2.mycompany.com >
Disposition: manual-action/MDN-sent-automatically; displayed
Original-Recipient: rfc822;22722@vm.company.com
Final-Recipient: rfc822;Greg.Vaudreuil@foomail.company.com
Original-Message-ID: <199509192301.12345@vm2.mycompany.com >
Disposition: manual-action/MDN-sent-automatically; displayed
--RAA14128.773615765/EXCHANGE.COMPANY.COM Content-type: message/rfc822
--RAA14128.773615765/EXCHANGE.COMPANY.COM内容类型：message/rfc822
[original VPIM message goes here]
[此处显示原始VPIM消息]
--RAA14128.773615765/EXCHANGE.COMPANY.COM--
--RAA14128.773615765/EXCHANGE.COMPANY.COM--
The following common voice processing errors and their corresponding status codes are given as examples. Text after the error codes are intended only for reference to describe the error code. Implementations should provide implementation specific informative comments after the error code rather than the text below.
下面给出了以下常见的语音处理错误及其相应的状态代码作为示例。错误代码后的文本仅用于描述错误代码的参考。实现应该在错误代码之后提供特定于实现的信息性注释，而不是下面的文本。
Error condition RFC 1893 Error codes
----------------------------- --------------------------------
Error condition RFC 1893 Error codes
----------------------------- --------------------------------
Analog delivery failed 4.4.0 Persistent connection error because remote system is busy - other
模拟传输失败4.4.0永久连接错误，因为远程系统忙-其他
Analog delivery failed 4.4.1 Persistent protocol error because remote system is - no answer from host ring-no-answer
模拟传输失败4.4.1永久协议错误，因为远程系统为-主机无应答无应答
Remote system did not answer 5.5.5 Permanent protocol error AMIS-Analog handshake ("D" in - wrong version response to "C" at connect time)
远程系统未回答5.5.5永久性协议错误AMIS模拟握手（“D”在-连接时对“C”的错误版本响应）
Mailbox does not exist 5.1.1 Permanent mailbox error - does not exist
邮箱不存在5.1.1永久邮箱错误-不存在
Mailbox full or over quota 4.2.2 Persistent mailbox error - full
邮箱已满或超过配额4.2.2永久邮箱错误-已满
Disk full 4.3.1 Persistent system error - full
磁盘已满4.3.1永久性系统错误-已满
Command out of sequence 5.5.1 Permanent protocol error - invalid command
命令顺序错误5.5.1永久协议错误-命令无效
Frame Error 5.5.2 Permanent protocol error - syntax error
帧错误5.5.2永久协议错误-语法错误
Mailbox does not support FAX 5.6.1 Permanent media error - not supported
邮箱不支持传真5.6.1永久介质错误-不支持
Mailbox does not support TEXT 5.6.1 Permanent media error - not supported
邮箱不支持文本5.6.1永久性媒体错误-不支持
Sender is not authorized 5.7.1 Permanent security error - sender not authorized
发件人未授权5.7.1永久性安全错误-发件人未授权
Message marked private, but 5.3.3 Permanent system error system is not private capable - not feature capable
消息标记为专用，但5.3.3永久系统错误系统不支持专用-不支持功能
The following common voice processing disposition conditions and their corresponding MDN Disposition (which contains the disposition mode, type and modifier, if applicable) are given as examples. Implementers should refer to [MDN] for a full description of the format of message disposition notifications.
下面给出了常见的语音处理配置条件及其相应的MDN配置（包含配置模式、类型和修改器，如果适用）作为示例。实现者应参考[MDN]了解消息处置通知格式的完整描述。
Notification event MDN Disposition mode, type & modifier
------------------------------ -------------------------------------
Notification event MDN Disposition mode, type & modifier
------------------------------ -------------------------------------
Message played by recipient, manual-action/MDN-sent-automatically; receipt automatically returned displayed
收件人播放的消息，手动操作/MDN自动发送；显示自动返回的收据
Message deleted from mailbox manual-action/MDN-sent-automatically; by user without listening deleted
自动发送从邮箱手动操作删除的邮件/MDN；按用户删除而不侦听
Message cleared when mailbox manual-action/MDN-sent-automatically; deleted by admin deleted/mailbox-terminated
邮箱手动操作/MDN自动发送时清除消息；已被管理员删除/邮箱已终止
Message automatically deleted automatic-action/ when older than administrator MDN-sent-automatically; deleted/ set threshold expired
消息自动删除自动操作/早于管理员时自动发送MDN；已删除/设置阈值已过期
Message processed, however manual-action/MDN-sent-automatically;
audio encoding unknown - processed/error
unable to play to user Error: unknown audio encoding
Message processed, however manual-action/MDN-sent-automatically;
audio encoding unknown - processed/error
unable to play to user Error: unknown audio encoding
To: ietf-mime-directory@imc.org
致：ietf mime-directory@imc.org
Subject: Registration of new parameter for text/directory MIME type EMAIL
主题：为文本/目录MIME类型电子邮件注册新参数
Type name: EMAIL
类型名称：电子邮件
Type purpose: To specify the electronic mail address for communication with the object the vCard represents (defined in [VCARD]).
类型用途：指定与vCard表示的对象通信的电子邮件地址（在[vCard]中定义）。
Type encoding: 8bit
类型编码：8位
Type value: A single text value.
类型值：单个文本值。
Type special notes: The type may include the type parameter "TYPE" to specify the format or preference of the electronic mail address. The TYPE parameter values previously defined include: "internet" to indicate an Internet addressing type, "x400" to indicate a X.400 addressing type and "pref" to indicate a preferred-use email address when more than one is specified. The value of "vpim" is defined to indicate that the address specified supports VPIM messages. Other IANA registered address type may also be specified. The default email type is "internet". A non-standard value may also be specified.
类型特殊说明：该类型可能包括类型参数“Type”，以指定电子邮件地址的格式或首选项。先前定义的类型参数值包括：“internet”表示internet寻址类型，“x400”表示X.400寻址类型，“pref”表示指定多个电子邮件地址时的首选使用电子邮件地址。“vpim”的值定义为指示指定的地址支持vpim消息。还可以指定其他IANA注册地址类型。默认电子邮件类型为“internet”。也可以指定非标准值。
Type example:
EMAIL;TYPE=internet,vpim:jqpublic@xyz.dom1.com
Type example:
EMAIL;TYPE=internet,vpim:jqpublic@xyz.dom1.com
To: IANA@IANA.ORG
致：IANA@IANA.ORG
Subject: Registration of new Content-Disposition parameter
主题：注册新内容处置参数
Content-Disposition parameter name: voice
内容配置参数名称：语音
Allowable values for this parameter:
此参数的允许值：
Voice-Message - the primary voice message, Voice-Message-Notification - a spoken delivery notification or spoken disposition notification, Originator-Spoken-Name - the spoken name of the originator,
语音信息-主要语音信息，语音信息通知-语音发送通知或语音处置通知，发起者语音名称-发起者的语音名称，
Recipient-Spoken-Name - the spoken name of the recipient if available to the originator and present if there is ONLY one recipient, Spoken-Subject- the spoken subject of the message, typically spoken by the originator
收件人口头姓名-收件人的口头姓名（如果发端人可用），如果只有一个收件人，则为收件人的口头姓名，口头主题-邮件的口头主题，通常由发端人说
Description:
说明：
In order to distinguish between the various types of audio contents in a VPIM voice message a new disposition parameter "voice" is defined with the preceding values to be used as appropriate. Note that there SHOULD only be one instance of each of these types of audio contents per message level. Additional instances of a given type (i.e., parameter value) may occur within an attached forwarded voice message.
为了区分VPIM语音消息中的各种类型的音频内容，定义了一个新的配置参数“voice”，并根据需要使用前面的值。请注意，对于每种类型的音频内容，每个消息级别应该只有一个实例。附加的转发语音消息中可能会出现给定类型（即参数值）的其他实例。
The updated profile in this document is based on the experience of a proof of concept demonstration of VPIM at EMA'96 in April 1996 and a subsequent demonstration of products at EMA'97 in April 1997. This version of the profile is significantly different from the previous described in [VPIM1]. The changes are categorized as general, content, transport and compliance. They are detailed below:
本文件中的更新配置文件基于1996年4月在EMA'96上进行的VPIM概念验证演示以及随后在1997年4月在EMA'97上进行的产品演示的经验。此版本的配置文件与[VPIM1]中之前描述的版本有很大不同。更改分为常规更改、内容更改、传输更改和法规遵从性更改。详情如下:
1. General
1. 全体的
- All definitions are now contained in separate documents that are referenced by this profile. The new documents include:
- 所有定义现在都包含在此配置文件引用的单独文档中。新文件包括：
- a refined multipart/voice-message definition
- 完善的多部分/语音消息定义
- a refined (i.e., added nibble order) audio/32KADPCM definition
- 完善的音频/32KADPCM定义（即增加了半字节顺序）
- the definitions of TIFF-F and image/tiff for fax images
- 传真图像的TIFF-F和图像/TIFF的定义
- the Content-Duration definition
- 内容持续时间定义
- Changed the Voice version to 2.0
- 将语音版本更改为2.0
- Added Table of Contents and more examples
- 添加了目录和更多示例
- Various editorial updates to improve readability
- 各种编辑更新以提高可读性
- Added more security considerations
- 增加了更多的安全注意事项
2. Content
2. 所容纳之物
- Modified multipart/voice-message content type by dropping the positional dependence of contents while restricting its contents to voice message specific content types
- 通过删除内容的位置相关性，同时将其内容限制为特定于语音消息的内容类型，修改了多部分/语音消息内容类型
- Explicitly indicated other contents that may be present ina multipart/mixed content type
- 明确指出了多部分/混合内容类型中可能存在的其他内容
- Explicitly defined the forwarding model using message/RFC822
- 使用message/RFC822显式定义转发模型
- Explained the use of reply-to and from header fields for addressing message replies
- 解释了如何使用“回复到”和“来自”标题字段来寻址邮件回复
- Deprecated the special "loopback" address because of security concerns and its use only for testing
- 不推荐使用特殊的“环回”地址，因为存在安全问题，并且该地址仅用于测试
- Defined the non-mail-user reserved address to support the case in which replies to the originator are not possible
- 定义了非邮件用户保留地址，以支持无法回复发起人的情况
- Eliminated the text name in the "To" and "CC" header fields. Deprecated ordering of text names in the "From" header.
- 删除了“收件人”和“抄送”标题字段中的文本名称。“发件人”标题中文本名称的顺序已弃用。
- Added support for facsimile using TIFF-F in an image/tiff; application=faxbw content type
- 增加了对在图像/TIFF中使用TIFF-F的传真的支持；应用程序=传真BW内容类型
- Profiled vCard in the text/directory body part for transport of directory information about the originator
- 文本/目录正文部分中的配置文件vCard，用于传输有关发起者的目录信息
- Loosened text restriction
- 放宽文本限制
- Added additional details on delivery and receipt notifications
- 添加了有关交货和收货通知的其他详细信息
- Added support for message disposition notifications, also known as receipt notifications.
- 增加了对消息处置通知（也称为接收通知）的支持。
- Added suggested addressing formats
- 添加了建议的寻址格式
- Described handling of private messages
- 描述了私有消息的处理
- Described the handling of non-profiled contents in VPIM messages
- 描述了VPIM消息中非概要内容的处理
- Described the use of Content-Disposition to semantically identify audio contents
- 描述了如何使用内容配置从语义上标识音频内容
3. Transport
3. 运输
- Moved binary support to optional
- 将二进制支持移动到可选
- Added optional ESMTP keywords for return of content, enhanced status codes, original recipient, and envelope ID
- 添加了用于返回内容、增强状态代码、原始收件人和信封ID的可选ESMTP关键字
- Described use of null MAIL FROM address
- 描述了空邮件发件人地址的使用
4. Compliance
4. 顺从
- Added an explicit section on conformance specifying conformance to content or transport
- 添加了关于一致性的明确部分，指定内容或传输的一致性
- Improved conformance table in Appendix A
- 附录A中改进的一致性表
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。