Network Working Group G. Klyne
Request for Comments: 4021 University of Oxford
Category: Standards Track J. Palme
Stockholm University/KT
March 2005
Network Working Group G. Klyne
Request for Comments: 4021 University of Oxford
Category: Standards Track J. Palme
Stockholm University/KT
March 2005
Registration of Mail and MIME Header Fields
邮件和MIME头字段的注册
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 (2005).
版权所有（C）互联网协会（2005年）。
Abstract
摘要
This document defines the initial IANA registration for permanent mail and MIME message header fields, per RFC 3864.
本文档根据RFC 3864定义了永久邮件和MIME邮件头字段的初始IANA注册。
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Structure of This Document . . . . . . . . . . . . . . . 3
1.2. Document Terminology and Conventions . . . . . . . . . . 4
2. Registration Templates . . . . . . . . . . . . . . . . . . . . 4
2.1. Permanent Mail Header Field Registrations . . . . . . . 4
2.1.1. Header Field: Date . . . . . . . . . . . . . . . 6
2.1.2. Header Field: From . . . . . . . . . . . . . . . 7
2.1.3. Header Field: Sender . . . . . . . . . . . . . . 7
2.1.4. Header Field: Reply-To . . . . . . . . . . . . . 8
2.1.5. Header Field: To . . . . . . . . . . . . . . . . 8
2.1.6. Header Field: Cc . . . . . . . . . . . . . . . . 9
2.1.7. Header Field: Bcc . . . . . . . . . . . . . . . 9
2.1.8. Header Field: Message-ID . . . . . . . . . . . . 10
2.1.9. Header Field: In-Reply-To . . . . . . . . . . . 10
2.1.10. Header Field: References . . . . . . . . . . . . 11
2.1.11. Header Field: Subject . . . . . . . . . . . . . 11
2.1.12. Header Field: Comments . . . . . . . . . . . . . 12
2.1.13. Header Field: Keywords . . . . . . . . . . . . . 12
2.1.14. Header Field: Resent-Date . . . . . . . . . . . 13
2.1.15. Header Field: Resent-From . . . . . . . . . . . 13
2.1.16. Header Field: Resent-Sender . . . . . . . . . . 14
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Structure of This Document . . . . . . . . . . . . . . . 3
1.2. Document Terminology and Conventions . . . . . . . . . . 4
2. Registration Templates . . . . . . . . . . . . . . . . . . . . 4
2.1. Permanent Mail Header Field Registrations . . . . . . . 4
2.1.1. Header Field: Date . . . . . . . . . . . . . . . 6
2.1.2. Header Field: From . . . . . . . . . . . . . . . 7
2.1.3. Header Field: Sender . . . . . . . . . . . . . . 7
2.1.4. Header Field: Reply-To . . . . . . . . . . . . . 8
2.1.5. Header Field: To . . . . . . . . . . . . . . . . 8
2.1.6. Header Field: Cc . . . . . . . . . . . . . . . . 9
2.1.7. Header Field: Bcc . . . . . . . . . . . . . . . 9
2.1.8. Header Field: Message-ID . . . . . . . . . . . . 10
2.1.9. Header Field: In-Reply-To . . . . . . . . . . . 10
2.1.10. Header Field: References . . . . . . . . . . . . 11
2.1.11. Header Field: Subject . . . . . . . . . . . . . 11
2.1.12. Header Field: Comments . . . . . . . . . . . . . 12
2.1.13. Header Field: Keywords . . . . . . . . . . . . . 12
2.1.14. Header Field: Resent-Date . . . . . . . . . . . 13
2.1.15. Header Field: Resent-From . . . . . . . . . . . 13
2.1.16. Header Field: Resent-Sender . . . . . . . . . . 14
2.1.17. Header Field: Resent-To . . . . . . . . . . . . 14
2.1.18. Header Field: Resent-Cc . . . . . . . . . . . . 15
2.1.19. Header Field: Resent-Bcc . . . . . . . . . . . . 15
2.1.20. Header Field: Resent-Reply-To . . . . . . . . . 16
2.1.21. Header Field: Resent-Message-ID . . . . . . . . 16
2.1.22. Header Field: Return-Path . . . . . . . . . . . 17
2.1.23. Header Field: Received . . . . . . . . . . . . . 17
2.1.24. Header Field: Encrypted . . . . . . . . . . . . 18
2.1.25. Header Field: Disposition-Notification-To . . . 18
2.1.26. Header Field: Disposition-Notification-Options . 19
2.1.27. Header Field: Accept-Language . . . . . . . . . 19
2.1.28. Header Field: Original-Message-ID . . . . . . . 20
2.1.29. Header Field: PICS-Label . . . . . . . . . . . . 20
2.1.30. Header Field: Encoding . . . . . . . . . . . . . 21
2.1.31. Header Field: List-Archive . . . . . . . . . . . 21
2.1.32. Header Field: List-Help . . . . . . . . . . . . 22
2.1.33. Header Field: List-ID . . . . . . . . . . . . . 22
2.1.34. Header Field: List-Owner . . . . . . . . . . . . 23
2.1.35. Header Field: List-Post . . . . . . . . . . . . 23
2.1.36. Header Field: List-Subscribe . . . . . . . . . . 24
2.1.37. Header Field: List-Unsubscribe . . . . . . . . . 24
2.1.38. Header Field: Message-Context . . . . . . . . . 25
2.1.39. Header Field: DL-Expansion-History . . . . . . . 25
2.1.40. Header Field: Alternate-Recipient . . . . . . . 26
2.1.41. Header Field: Original-Encoded-Information-Types 26
2.1.42. Header Field: Content-Return . . . . . . . . . . 27
2.1.43. Header Field: Generate-Delivery-Report . . . . . 27
2.1.44. Header Field: Prevent-NonDelivery-Report . . . . 28
2.1.45. Header Field: Obsoletes . . . . . . . . . . . . 28
2.1.46. Header Field: Supersedes . . . . . . . . . . . . 29
2.1.47. Header Field: Content-Identifier . . . . . . . . 29
2.1.48. Header Field: Delivery-Date . . . . . . . . . . 30
2.1.49. Header Field: Expiry-Date . . . . . . . . . . . 30
2.1.50. Header Field: Expires . . . . . . . . . . . . . 31
2.1.51. Header Field: Reply-By . . . . . . . . . . . . . 31
2.1.52. Header Field: Importance . . . . . . . . . . . . 32
2.1.53. Header Field: Incomplete-Copy . . . . . . . . . 32
2.1.54. Header Field: Priority . . . . . . . . . . . . . 33
2.1.55. Header Field: Sensitivity . . . . . . . . . . . 33
2.1.56. Header Field: Language . . . . . . . . . . . . . 34
2.1.57. Header Field: Conversion . . . . . . . . . . . . 34
2.1.58. Header Field: Conversion-With-Loss . . . . . . . 35
2.1.59. Header Field: Message-Type . . . . . . . . . . . 35
2.1.60. Header Field: Autosubmitted . . . . . . . . . . 36
2.1.61. Header Field: Autoforwarded . . . . . . . . . . 36
2.1.62. Header Field: Discarded-X400-IPMS-Extensions . . 37
2.1.63. Header Field: Discarded-X400-MTS-Extensions . . 37
2.1.64. Header Field: Disclose-Recipients . . . . . . . 38
2.1.17. Header Field: Resent-To . . . . . . . . . . . . 14
2.1.18. Header Field: Resent-Cc . . . . . . . . . . . . 15
2.1.19. Header Field: Resent-Bcc . . . . . . . . . . . . 15
2.1.20. Header Field: Resent-Reply-To . . . . . . . . . 16
2.1.21. Header Field: Resent-Message-ID . . . . . . . . 16
2.1.22. Header Field: Return-Path . . . . . . . . . . . 17
2.1.23. Header Field: Received . . . . . . . . . . . . . 17
2.1.24. Header Field: Encrypted . . . . . . . . . . . . 18
2.1.25. Header Field: Disposition-Notification-To . . . 18
2.1.26. Header Field: Disposition-Notification-Options . 19
2.1.27. Header Field: Accept-Language . . . . . . . . . 19
2.1.28. Header Field: Original-Message-ID . . . . . . . 20
2.1.29. Header Field: PICS-Label . . . . . . . . . . . . 20
2.1.30. Header Field: Encoding . . . . . . . . . . . . . 21
2.1.31. Header Field: List-Archive . . . . . . . . . . . 21
2.1.32. Header Field: List-Help . . . . . . . . . . . . 22
2.1.33. Header Field: List-ID . . . . . . . . . . . . . 22
2.1.34. Header Field: List-Owner . . . . . . . . . . . . 23
2.1.35. Header Field: List-Post . . . . . . . . . . . . 23
2.1.36. Header Field: List-Subscribe . . . . . . . . . . 24
2.1.37. Header Field: List-Unsubscribe . . . . . . . . . 24
2.1.38. Header Field: Message-Context . . . . . . . . . 25
2.1.39. Header Field: DL-Expansion-History . . . . . . . 25
2.1.40. Header Field: Alternate-Recipient . . . . . . . 26
2.1.41. Header Field: Original-Encoded-Information-Types 26
2.1.42. Header Field: Content-Return . . . . . . . . . . 27
2.1.43. Header Field: Generate-Delivery-Report . . . . . 27
2.1.44. Header Field: Prevent-NonDelivery-Report . . . . 28
2.1.45. Header Field: Obsoletes . . . . . . . . . . . . 28
2.1.46. Header Field: Supersedes . . . . . . . . . . . . 29
2.1.47. Header Field: Content-Identifier . . . . . . . . 29
2.1.48. Header Field: Delivery-Date . . . . . . . . . . 30
2.1.49. Header Field: Expiry-Date . . . . . . . . . . . 30
2.1.50. Header Field: Expires . . . . . . . . . . . . . 31
2.1.51. Header Field: Reply-By . . . . . . . . . . . . . 31
2.1.52. Header Field: Importance . . . . . . . . . . . . 32
2.1.53. Header Field: Incomplete-Copy . . . . . . . . . 32
2.1.54. Header Field: Priority . . . . . . . . . . . . . 33
2.1.55. Header Field: Sensitivity . . . . . . . . . . . 33
2.1.56. Header Field: Language . . . . . . . . . . . . . 34
2.1.57. Header Field: Conversion . . . . . . . . . . . . 34
2.1.58. Header Field: Conversion-With-Loss . . . . . . . 35
2.1.59. Header Field: Message-Type . . . . . . . . . . . 35
2.1.60. Header Field: Autosubmitted . . . . . . . . . . 36
2.1.61. Header Field: Autoforwarded . . . . . . . . . . 36
2.1.62. Header Field: Discarded-X400-IPMS-Extensions . . 37
2.1.63. Header Field: Discarded-X400-MTS-Extensions . . 37
2.1.64. Header Field: Disclose-Recipients . . . . . . . 38
2.1.65. Header Field: Deferred-Delivery . . . . . . . . 38
2.1.66. Header Field: Latest-Delivery-Time . . . . . . . 39
2.1.67. Header Field: Originator-Return-Address . . . . 39
2.1.68. Header Field: X400-Content-Identifier . . . . . 40
2.1.69. Header Field: X400-Content-Return . . . . . . . 40
2.1.70. Header Field: X400-Content-Type . . . . . . . . 41
2.1.71. Header Field: X400-MTS-Identifier . . . . . . . 41
2.1.72. Header Field: X400-Originator . . . . . . . . . 42
2.1.73. Header Field: X400-Received . . . . . . . . . . 42
2.1.74. Header Field: X400-Recipients . . . . . . . . . 43
2.1.75. Header Field: X400-Trace . . . . . . . . . . . . 43
2.2. Permanent MIME Header Field Registrations . . . . . . . 44
2.2.1. Header Field: MIME-Version . . . . . . . . . . . 44
2.2.2. Header Field: Content-ID . . . . . . . . . . . . 45
2.2.3. Header Field: Content-Description . . . . . . . 45
2.2.4. Header Field: Content-Transfer-Encoding . . . . 46
2.2.5. Header Field: Content-Type . . . . . . . . . . . 46
2.2.6. Header Field: Content-Base . . . . . . . . . . . 47
2.2.7. Header Field: Content-Location . . . . . . . . . 47
2.2.8. Header Field: Content-features . . . . . . . . . 48
2.2.9. Header Field: Content-Disposition . . . . . . . 48
2.2.10. Header Field: Content-Language . . . . . . . . . 49
2.2.11. Header Field: Content-Alternative . . . . . . . 49
2.2.12. Header Field: Content-MD5 . . . . . . . . . . . 50
2.2.13. Header Field: Content-Duration . . . . . . . . . 50
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
4. Security Considerations . . . . . . . . . . . . . . . . . . . 51
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 51
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1. Normative References . . . . . . . . . . . . . . . . . . 51
6.2. Informative References . . . . . . . . . . . . . . . . . 53
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 53
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 54
2.1.65. Header Field: Deferred-Delivery . . . . . . . . 38
2.1.66. Header Field: Latest-Delivery-Time . . . . . . . 39
2.1.67. Header Field: Originator-Return-Address . . . . 39
2.1.68. Header Field: X400-Content-Identifier . . . . . 40
2.1.69. Header Field: X400-Content-Return . . . . . . . 40
2.1.70. Header Field: X400-Content-Type . . . . . . . . 41
2.1.71. Header Field: X400-MTS-Identifier . . . . . . . 41
2.1.72. Header Field: X400-Originator . . . . . . . . . 42
2.1.73. Header Field: X400-Received . . . . . . . . . . 42
2.1.74. Header Field: X400-Recipients . . . . . . . . . 43
2.1.75. Header Field: X400-Trace . . . . . . . . . . . . 43
2.2. Permanent MIME Header Field Registrations . . . . . . . 44
2.2.1. Header Field: MIME-Version . . . . . . . . . . . 44
2.2.2. Header Field: Content-ID . . . . . . . . . . . . 45
2.2.3. Header Field: Content-Description . . . . . . . 45
2.2.4. Header Field: Content-Transfer-Encoding . . . . 46
2.2.5. Header Field: Content-Type . . . . . . . . . . . 46
2.2.6. Header Field: Content-Base . . . . . . . . . . . 47
2.2.7. Header Field: Content-Location . . . . . . . . . 47
2.2.8. Header Field: Content-features . . . . . . . . . 48
2.2.9. Header Field: Content-Disposition . . . . . . . 48
2.2.10. Header Field: Content-Language . . . . . . . . . 49
2.2.11. Header Field: Content-Alternative . . . . . . . 49
2.2.12. Header Field: Content-MD5 . . . . . . . . . . . 50
2.2.13. Header Field: Content-Duration . . . . . . . . . 50
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
4. Security Considerations . . . . . . . . . . . . . . . . . . . 51
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 51
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1. Normative References . . . . . . . . . . . . . . . . . . 51
6.2. Informative References . . . . . . . . . . . . . . . . . 53
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 53
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 54
This document defines IANA registration for a number of mail message and MIME header fields, per registration procedures for message header fields [1].
本文档根据消息头字段的注册过程定义了许多邮件消息和MIME头字段的IANA注册[1]。
The main body of this document is automatically generated from RDF/N3 data. Some experimental HTML registry pages have been prepared from the same data and can be found at [27].
本文档的主体由RDF/N3数据自动生成。一些实验性HTML注册表页是根据相同的数据准备的，可以在[27]中找到。
Section 2.1 contains the templates for initial registration of mail message header fields.
第2.1节包含邮件消息头字段的初始注册模板。
Section 2.2 contains templates for initial registration of MIME header fields.
第2.2节包含MIME头字段的初始注册模板。
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 BCP 14, RFC 2119 [9].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[9]中的描述进行解释。
Header field registry entries are summarized in tabular form for convenience of reference and presented in full in the following sections.
标题字段注册表项以表格形式汇总，以便于参考，并在以下各节中完整介绍。
Header name Protocol
----------- --------
Date Mail Message date and time
From Mail Mailbox of message author
Sender Mail Mailbox of message sender
Reply-To Mail Mailbox for replies to message
To Mail Primary recipient mailbox
Cc Mail Carbon-copy recipient mailbox
Bcc Mail Blind-carbon-copy recipient
mailbox
Message-ID Mail Message identifier
In-Reply-To Mail Identify replied-to message(s)
References Mail Related message identifier(s)
Subject Mail Topic of message
Comments Mail Additional comments about the
message
Keywords Mail Message key words and/or phrases
Resent-Date Mail Date and time message is resent
Resent-From Mail Mailbox of person for whom message
is resent
Resent-Sender Mail Mailbox of person who actually
resends the message
Resent-To Mail Mailbox to which message is resent
Resent-Cc Mail Mailbox(es) to which message is
cc'ed on resend
Resent-Bcc Mail Mailbox(es) to which message is
bcc'ed on resend
Resent-Reply-To Mail Resent reply-to
Resent-Message-ID Mail Message identifier for resent
message
Header name Protocol
----------- --------
Date Mail Message date and time
From Mail Mailbox of message author
Sender Mail Mailbox of message sender
Reply-To Mail Mailbox for replies to message
To Mail Primary recipient mailbox
Cc Mail Carbon-copy recipient mailbox
Bcc Mail Blind-carbon-copy recipient
mailbox
Message-ID Mail Message identifier
In-Reply-To Mail Identify replied-to message(s)
References Mail Related message identifier(s)
Subject Mail Topic of message
Comments Mail Additional comments about the
message
Keywords Mail Message key words and/or phrases
Resent-Date Mail Date and time message is resent
Resent-From Mail Mailbox of person for whom message
is resent
Resent-Sender Mail Mailbox of person who actually
resends the message
Resent-To Mail Mailbox to which message is resent
Resent-Cc Mail Mailbox(es) to which message is
cc'ed on resend
Resent-Bcc Mail Mailbox(es) to which message is
bcc'ed on resend
Resent-Reply-To Mail Resent reply-to
Resent-Message-ID Mail Message identifier for resent
message
Return-Path Mail Message return path Received Mail Mail transfer trace information Encrypted Mail Message encryption information Disposition-Notification-To Mail Mailbox for sending disposition notification Disposition-Notification-Options Mail Disposition notification options Accept-Language Mail Language(s) for auto-responses Original-Message-ID Mail Original message identifier PICS-Label Mail PICS rating label Encoding Mail Message encoding and other information List-Archive Mail URL of mailing list archive List-Help Mail URL for mailing list information List-ID Mail Mailing list identifier List-Owner Mail URL for mailing list owner's mailbox List-Post Mail URL for mailing list posting List-Subscribe Mail URL for mailing list subscription List-Unsubscribe Mail URL for mailing list unsubscription Message-Context Mail Type or context of message DL-Expansion-History Mail Trace of distribution lists passed Alternate-Recipient Mail Controls forwarding to alternate recipients Original-Encoded-Information-Types Mail Body part types in message Content-Return Mail Return content on non-delivery? Generate-Delivery-Report Mail Request delivery report generation Prevent-NonDelivery-Report Mail Non-delivery report required? Obsoletes Mail Reference message to be replaced Supersedes Mail Reference message to be replaced Content-Identifier Mail Message content identifier Delivery-Date Mail Message delivery time Expiry-Date Mail Message expiry time Expires Mail Message expiry time Reply-By Mail Time by which a reply is requested Importance Mail Message importance Incomplete-Copy Mail Body parts are missing Priority Mail Message priority Sensitivity Mail Message content sensitivity Language Mail X.400 message content language Conversion Mail Conversion allowed?
返回路径邮件返回路径收到的邮件传输跟踪信息加密邮件加密信息处置通知发送到邮箱处置通知处置通知选项邮件处置通知选项接受语言邮件语言对于自动响应，原始邮件ID邮件原始邮件标识符PICS标签邮件PICS分级标签编码邮件编码和其他信息列表存档邮件URL邮件列表存档列表帮助邮件URL邮件列表信息列表ID邮件列表标识符列表所有者邮件URL邮件列表所有者邮箱列表邮寄邮件URL用于邮寄列表邮寄列表订阅邮件URL用于邮寄列表订阅列表取消订阅邮件URL用于邮寄列表取消订阅邮件上下文邮件类型或邮件上下文DL扩展历史通讯组列表的邮件跟踪传递给备用收件人邮件控件转发给备用收件人原始编码信息类型邮件正文部分类型邮件内容返回邮件未送达时返回内容？生成交货报告邮件请求交货报告生成阻止不交货报告邮件不交货报告是否需要？废弃要替换的邮件引用邮件取代要替换的邮件引用邮件内容标识符邮件内容标识符送达日期邮件送达时间到期日期邮件到期时间到期邮件到期时间按邮件回复请求回复的时间重要性邮件重要性不完整的副本邮件正文部分缺少优先级邮件优先级敏感度邮件内容敏感度语言邮件X.400邮件内容语言转换允许邮件转换吗？
Conversion-With-Loss Mail Lossy conversion allowed? Message-Type Mail Message type: delivery report? Autosubmitted Mail Automatically submitted indicator Autoforwarded Mail Automatically forwarded indicator Discarded-X400-IPMS-Extensions Mail X.400 IPM extensions discarded Discarded-X400-MTS-Extensions Mail X.400 MTS extensions discarded Disclose-Recipients Mail Disclose names of other recipients? Deferred-Delivery Mail Deferred delivery information Latest-Delivery-Time Mail Latest delivery time requested Originator-Return-Address Mail Originator return address X400-Content-Identifier Mail Message content identifier X400-Content-Return Mail Return content on non-delivery? X400-Content-Type Mail X400 content type X400-MTS-Identifier Mail X400 MTS-Identifier X400-Originator Mail X400 Originator X400-Received Mail X400 Received X400-Recipients Mail X400 Recipients X400-Trace Mail X400 Trace
是否允许使用丢失邮件有损转换？邮件类型邮件类型：传递报告？自动转发邮件自动提交指示符自动转发邮件自动转发指示符丢弃-X400-IPMS-Extensions邮件X.400 IPM Extensions丢弃-X400-MTS-Extensions邮件X.400 MTS Extensions丢弃披露收件人邮件披露其他收件人的姓名？延迟投递邮件延迟投递信息最新投递时间邮件最新投递时间请求的发起者返回地址邮件发起者返回地址X400内容标识符邮件内容标识符X400内容返回邮件未送达时返回内容？X400内容类型邮件X400内容类型X400 MTS标识符邮件X400 MTS标识符邮件X400发起人邮件X400发起人邮件X400接收邮件X400接收邮件X400收件人邮件X400收件人X400跟踪邮件X400跟踪
Description: Message date and time
描述：消息日期和时间
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.1)
规范文件：RFC 2822[18]（第3.6.1节）
Related information: Specifies the date and time at which the creator of the message indicated that the message was complete and ready to enter the mail delivery system. Defined as standard by RFC 822.
相关信息：指定消息创建者指示消息已完成并准备好进入邮件传递系统的日期和时间。由RFC 822定义为标准。
Description: Mailbox of message author
Description:邮件作者的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.2)
规范文件：RFC 2822[18]（第3.6.2节）
Related information: Specifies the author(s) of the message; that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. Defined as standard by RFC 822.
相关信息：指定消息的作者；即，负责编写邮件的人员或系统的邮箱。由RFC 822定义为标准。
Description: Mailbox of message sender
Description:邮件发件人的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.2)
规范文件：RFC 2822[18]（第3.6.2节）
Related information: Specifies the mailbox of the agent responsible for the actual transmission of the message. Defined as standard by RFC 822.
相关信息：指定负责实际传输邮件的代理的邮箱。由RFC 822定义为标准。
Description: Mailbox for replies to message
描述：用于回复邮件的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller:
IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
Author/change controller:
IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
Specification document(s): RFC 2822 [18] (section 3.6.2)
规范文件：RFC 2822[18]（第3.6.2节）
Related information: When the "Reply-To:" field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent. Defined as standard by RFC 822.
相关信息：“回复：”字段存在时，表示邮件作者建议向其发送回复的邮箱。由RFC 822定义为标准。
Description: Primary recipient mailbox
说明：主收件人邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.3)
规范文件：RFC 2822[18]（第3.6.3节）
Related information: Contains the address(es) of the primary recipient(s) of the message. Defined as standard by RFC 822.
相关信息：包含邮件主要收件人的地址。由RFC 822定义为标准。
Description: Carbon-copy recipient mailbox
说明：抄送收件人邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.3)
规范文件：RFC 2822[18]（第3.6.3节）
Related information: Contains the addresses of others who are to receive the message, though the content of the message may not be directed at them. Defined as standard by RFC 822.
相关信息：包含将接收邮件的其他人的地址，尽管邮件内容可能不是针对他们的。由RFC 822定义为标准。
Description: Blind-carbon-copy recipient mailbox
描述：盲拷贝收件人邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.3)
规范文件：RFC 2822[18]（第3.6.3节）
Related information: Contains addresses of recipients of the message whose addresses are not to be revealed to other recipients of the message. Defined as standard by RFC 822.
相关信息：包含不向其他邮件收件人显示其地址的邮件收件人的地址。由RFC 822定义为标准。
Description: Message identifier
描述：消息标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.4)
规范文件：RFC 2822[18]（第3.6.4节）
Related information: Contains a single unique message identifier that refers to a particular version of a particular message. If the message is resent without changes, the original Message-ID is retained. Defined as standard by RFC 822.
相关信息：包含一个唯一的消息标识符，该标识符表示特定消息的特定版本。如果重新发送邮件时未做任何更改，则保留原始邮件ID。由RFC 822定义为标准。
Description: Identify replied-to message(s)
描述：识别已回复的邮件
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.4)
规范文件：RFC 2822[18]（第3.6.4节）
Related information: The message identifier(s) of the original message(s) to which the current message is a reply. Defined as standard by RFC 822.
相关信息：当前消息作为回复的原始消息的消息标识符。由RFC 822定义为标准。
Description: Related message identifier(s)
描述：相关消息标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.4)
规范文件：RFC 2822[18]（第3.6.4节）
Related information: The message identifier(s) of other message(s) to which the current message may be related. In RFC 2822, the definition was changed to say that this header field contains a list of all Message-IDs of messages in the preceding reply chain. Defined as standard by RFC 822.
相关信息：当前消息可能与之相关的其他消息的消息标识符。在RFC 2822中，定义被更改为表示此标头字段包含前面回复链中消息的所有消息ID的列表。由RFC 822定义为标准。
Description: Topic of message
描述：信息主题
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.5)
规范文件：RFC 2822[18]（第3.6.5节）
Related information: Contains a short string identifying the topic of the message. Defined as standard by RFC 822.
相关信息：包含标识消息主题的短字符串。由RFC 822定义为标准。
Description: Additional comments about the message
描述：有关消息的其他注释
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.5)
规范文件：RFC 2822[18]（第3.6.5节）
Related information: Contains any additional comments on the text of the body of the message. Warning: Some mailers will not show this field to recipients. Defined as standard by RFC 822.
相关信息：包含对邮件正文文本的任何附加注释。警告：某些邮件不会向收件人显示此字段。由RFC 822定义为标准。
Description: Message key words and/or phrases
描述：消息关键字和/或短语
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.5)
规范文件：RFC 2822[18]（第3.6.5节）
Related information: Contains a comma-separated list of important words and phrases that might be useful for the recipient. Defined as standard by RFC 822.
相关信息：包含可能对收件人有用的重要单词和短语的逗号分隔列表。由RFC 822定义为标准。
Description: Date and time message is resent
描述：重新发送日期和时间消息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains the date and time that a message is reintroduced into the message transfer system. Defined as standard by RFC 822.
相关信息：包含将消息重新引入消息传输系统的日期和时间。由RFC 822定义为标准。
Description: Mailbox of person for whom message is resent
描述：为其重新发送邮件的人的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains the mailbox of the agent who has reintroduced the message into the message transfer system, or on whose behalf the message has been resent. Defined as standard by RFC 822.
相关信息：包含已将邮件重新引入邮件传输系统或已代表其重新发送邮件的代理的邮箱。由RFC 822定义为标准。
Description: Mailbox of person who actually resends the message
描述：实际重新发送邮件的人的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains the mailbox of the agent who has reintroduced the message into the message transfer system, if this is different from the Resent-From value. Defined as standard by RFC 822.
相关信息：包含已将邮件重新引入邮件传输系统的代理的邮箱（如果该邮箱与“重新发送自”值不同）。由RFC 822定义为标准。
Description: Mailbox to which message is resent
描述：邮件重新发送到的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains the mailbox(es) to which the message has been resent. Defined as standard by RFC 822.
相关信息：包含邮件重新发送到的邮箱。由RFC 822定义为标准。
Description: Mailbox(es) to which message is cc'ed on resend
描述：邮件在重新发送时抄送到的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains the mailbox(es) to which message is cc'ed on resend. Defined as standard by RFC 822.
相关信息：包含邮件在重新发送时抄送到的邮箱。由RFC 822定义为标准。
Description: Mailbox(es) to which message is bcc'ed on resend
描述：邮件在重新发送时以密件传给的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains the mailbox(es) to which message is bcc'ed on resend. Defined as standard by RFC 822.
相关信息：包含邮件在重新发送时以密件传给的邮箱。由RFC 822定义为标准。
Description: Resent reply-to
描述：重新回复
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: obsolete
现状：过时
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18]
规范文件：RFC 2822[18]
Related information: Resent Reply-to. Defined by RFC 822, obsoleted by RFC 2822.
相关信息：重新回复。由RFC 822定义，由RFC 2822淘汰。
Description: Message identifier for resent message
描述：重新发送消息的消息标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.6)
规范文件：RFC 2822[18]（第3.6.6节）
Related information: Contains a message identifier for a resent message. Defined as standard by RFC 822.
相关信息：包含重新发送消息的消息标识符。由RFC 822定义为标准。
Description: Message return path
描述：消息返回路径
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.7)
规范文件：RFC 2822[18]（第3.6.7节）
Related information: Return path for message response diagnostics. See also RFC 2821 [17]. Defined as standard by RFC 822.
相关信息：消息响应诊断的返回路径。另见RFC 2821[17]。由RFC 822定义为标准。
Description: Mail transfer trace information
描述：邮件传输跟踪信息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2822 [18] (section 3.6.7)
规范文件：RFC 2822[18]（第3.6.7节）
Related information: Contains information about receipt of the current message by a mail transfer agent on the transfer path. See also RFC 2821 [17]. Defined as standard by RFC 822.
相关信息：包含有关邮件传输代理在传输路径上接收当前邮件的信息。另见RFC 2821[17]。由RFC 822定义为标准。
Description: Message encryption information
描述：消息加密信息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: obsolete
现状：过时
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 822 [2]
规范文件：RFC 822[2]
Related information: Defined by RFC 822, but was found to be inadequately specified, was not widely implemented, and was removed in RFC 2822. Current practice is to use separate encryption, such as S/MIME or OpenPGP, possibly in conjunction with RFC 1847 MIME security multiparts.
相关信息：由RFC 822定义，但被发现未充分规定，未广泛实施，并在RFC 2822中删除。目前的做法是使用单独的加密，如S/MIME或OpenPGP，可能与RFC1847 MIME安全多部分结合使用。
Description: Mailbox for sending disposition notification
描述：用于发送处置通知的邮箱
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2298 [12]
规范文件：RFC 2298[12]
Related information: Indicates that the sender wants a disposition notification when this message is received (read, processed, etc.) by its recipients.
相关信息：表示当收件人收到（读取、处理等）此邮件时，发件人希望收到处置通知。
Description: Disposition notification options
描述：处置通知选项
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2298 [12]
规范文件：RFC 2298[12]
Related information: For optional modifiers on disposition notification requests.
相关信息：有关处置通知请求的可选修饰符。
Description: Language(s) for auto-responses
描述：用于自动响应的语言
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 3282 [21]
规范文件：RFC 3282[21]
Related information: Indicates a language that the message sender requests to be used for responses. Accept-language was not designed for email but has been considered useful as input to the generation of automatic replies. Some problems have been noted concerning its use with email, including but not limited to determination of the email address to which it refers; cost and lack of effective internationalization of email responses; interpretation of language subtags; and determining what character set encoding should be used.
相关信息：表示消息发送者请求用于响应的语言。Accept语言不是为电子邮件设计的，但被认为是生成自动回复的有用输入。已注意到与电子邮件使用有关的一些问题，包括但不限于确定其所指的电子邮件地址；电子邮件回复的成本和缺乏有效的国际化；语言子标签的解释；以及确定应该使用什么字符集编码。
Description: Original message identifier
描述：原始消息标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 3297 [22]
规范文件：RFC 3297[22]
Related information: Original message identifier used with resend of message with alternative content format; identifies the original message data to which it corresponds.
相关信息：用于重新发送具有替代内容格式的消息的原始消息标识符；标识其对应的原始消息数据。
Description: PICS rating label
描述：PICS评级标签
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standard
状态：标准
Author/change controller: W3C (mailto:web-human@w3.org) World Wide Web Consortium
作者/变更控制者：W3C（邮箱：web）-human@w3.org)万维网联盟
Specification document(s): PICS-labels [24]
规范文件：PICS标签[24]
Related information: Ratings label to control selection (filtering) of messages according to the PICS protocol. Specified for general use with RFC 822 message format, with HTTP-specific extensions.
相关信息：根据PICS协议控制消息选择（过滤）的评级标签。指定用于RFC 822消息格式的通用，带有HTTP特定扩展名。
Description: Message encoding and other information
描述：消息编码和其他信息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: experimental
现状：实验性
Author/change controller: Albert K. Costanzo (mailto:AL@AKC.COM) AKC Consulting Inc.
作者/变更控制员：阿尔伯特K.科斯坦佐（邮寄：AL@AKC.COM)AKC咨询公司。
Specification document(s): RFC 1505 [4]
规范文件：RFC 1505[4]
Related information: Used in several different ways by different mail systems. Some use it for a kind of content-type information, some for encoding and length information, some for a kind of boundary information, and some in other ways.
相关信息：由不同的邮件系统以几种不同的方式使用。有些用于内容类型信息，有些用于编码和长度信息，有些用于边界信息，还有一些用于其他方式。
Description: URL of mailing list archive
描述：邮件列表存档的URL
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2369 [13]
规范文件：RFC 2369[13]
Related information: Contains the URL to use to browse the archives of the mailing list from which this message was relayed.
相关信息：包含用于浏览转发此邮件的邮件列表存档的URL。
Description: URL for mailing list information
描述：邮件列表信息的URL
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2369 [13]
规范文件：RFC 2369[13]
Related information: Contains the URL to use to get information about the mailing list from which this message was relayed.
相关信息：包含用于获取转发此邮件的邮件列表信息的URL。
Description: Mailing list identifier
描述：邮件列表标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2919 [20]
规范文件：RFC 2919[20]
Related information: Stores an identification of the mailing list through which this message was distributed.
相关信息：存储用于分发此邮件的邮件列表的标识。
Description: URL for mailing list owner's mailbox
描述：邮件列表所有者邮箱的URL
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2369 [13]
规范文件：RFC 2369[13]
Related information: Contains the URL to send e-mail to the owner of the mailing list from which this message was relayed.
相关信息：包含向转发此邮件的邮件列表的所有者发送电子邮件的URL。
Description: URL for mailing list posting
描述：邮件列表发布的URL
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2369 [13]
规范文件：RFC 2369[13]
Related information: Contains the URL to use to send contributions to the mailing list from which this message was relayed.
相关信息：包含用于向转发此邮件的邮件列表发送贡献的URL。
Description: URL for mailing list subscription
描述：邮件列表订阅的URL
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2369 [13]
规范文件：RFC 2369[13]
Related information: Contains the URL to use to get a subscription to the mailing list from which this message was relayed.
相关信息：包含用于获取转发此邮件的邮件列表订阅的URL。
Description: URL for mailing list unsubscription
描述：用于取消订阅邮件列表的URL
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2369 [13]
规范文件：RFC 2369[13]
Related information: Contains the URL to use to unsubscribe the mailing list from which this message was relayed.
相关信息：包含用于取消订阅转发此邮件的邮件列表的URL。
Description: Type or context of message
描述：消息的类型或上下文
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 3458 [23]
规范文件：RFC 3458[23]
Related information: Provides information about the context and presentation characteristics of a message. Can have the values 'voice-message', 'fax-message', 'pager-message', 'multimedia-message', 'text-message', or 'none'.
相关信息：提供有关消息的上下文和表示特征的信息。可以具有值“语音消息”、“传真消息”、“寻呼机消息”、“彩信”、“文本消息”或“无”。
Description: Trace of distribution lists passed
描述：传递的通讯组列表的跟踪
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Trace of distribution lists passed. (MIXER X.400 mapping; not for general use.)
相关信息：传递的通讯组列表的跟踪。（混合器X.400映射；不用于一般用途。）
Description: Controls forwarding to alternate recipients
描述：控制转发到备用收件人
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Controls whether this message may be forwarded to an alternate recipient, such as a postmaster, if delivery to the intended recipient is not possible. Default: Allowed. RFC 2156 (MIXER), not for general use.
相关信息：控制如果无法将此邮件发送给预期收件人，是否可以将此邮件转发给其他收件人，如邮政局长。默认值：允许。RFC 2156（混合器），非通用型。
Description: Body part types in message
描述：消息中的正文部分类型
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Which body part types occur in this message. RFC 2156 (MIXER); not for general use.
相关信息：此消息中出现了哪些车身零件类型。RFC2156（混合器）；不适用于一般用途。
Description: Return content on non-delivery?
描述：未交付时返回内容？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: obsolete
现状：过时
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 1327 [3]
规范文件：RFC 1327[3]
Related information: Indicates whether the content of a message is to be returned with non-delivery notifications. Introduced by RFC 1327 and subsequently changed by RFC 2156 to avoid confusion with MIME defined fields.
相关信息：指示是否返回邮件内容和未送达通知。由RFC 1327引入，随后由RFC 2156更改，以避免与MIME定义的字段混淆。
Description: Request delivery report generation
描述：请求传递报告生成
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Indicates whether a delivery report is wanted at successful delivery. Default is not to generate such a report. RFC 2156 (MIXER); not for general use.
相关信息：表示成功交付时是否需要交付报告。默认情况下，不生成这样的报告。RFC2156（混合器）；不适用于一般用途。
Description: Non-delivery report required?
说明：是否需要未交付报告？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Indicates whether a non-delivery report is wanted on delivery error. Default is to generate such a report. RFC 2156 (MIXER); not for general use.
相关信息：指示是否需要交付错误的未交付报告。默认情况下，生成这样的报告。RFC2156（混合器）；不适用于一般用途。
Description: Reference message to be replaced
描述：要替换的参考消息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: obsolete
现状：过时
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 1327 [3]
规范文件：RFC 1327[3]
Related information: Reference to a previous message being corrected and replaced. Compare to 'Supersedes:',f used in Usenet News. Introduced by RFC 1327 and subsequently renamed by RFC 2156 to 'Supersedes'.
相关信息：引用正在更正和替换的上一条消息。与Usenet新闻中使用的“取代：”，f进行比较。由RFC 1327引入，随后由RFC 2156更名为“取代”。
Description: Reference message to be replaced
描述：要替换的参考消息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Reference to a previous message being corrected and replaced. Renamed version of obsolete 'Obsoletes' header field. RFC 2156 (MIXER); not for general use.
相关信息：引用正在更正和替换的上一条消息。已重命名的过时“过时”标题字段的版本。RFC2156（混合器）；不适用于一般用途。
Description: Message content identifier
描述：消息内容标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: obsolete
现状：过时
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 1327 [3]
规范文件：RFC 1327[3]
Related information: A text string that identifies the content of a message. Introduced by RFC 1327 and subsequently changed by RFC 2156 to avoid confusion with MIME defined fields. Gateways that reverse map may support the old field.
相关信息：标识消息内容的文本字符串。由RFC 1327引入，随后由RFC 2156更改，以避免与MIME定义的字段混淆。反向映射的网关可能支持旧字段。
Description: Message delivery time
描述：邮件传递时间
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: The time when a message was delivered to its recipient. RFC 2156 (MIXER); not for general use.
相关信息：邮件传递给收件人的时间。RFC2156（混合器）；不适用于一般用途。
Description: Message expiry time
描述：邮件到期时间
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: obsolete
现状：过时
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 1327 [3]
规范文件：RFC 1327[3]
Related information: Time at which a message loses its validity. Introduced by RFC 1327 and subsequently changed by RFC 2156 to 'Expires:'.
相关信息：消息失去有效性的时间。由RFC 1327引入，随后由RFC 2156更改为“Expires:”。
Description: Message expiry time
描述：邮件到期时间
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Time at which a message loses its validity. Renamed version of obsolete Expiry-Date header field. RFC 2156 (MIXER), not for general use.
相关信息：消息失去有效性的时间。已重命名的过时到期日期标题字段的版本。RFC 2156（混合器），非通用型。
Description: Time by which a reply is requested
描述：请求回复的时间
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Latest time by which a reply is requested (not demanded). RFC 2156 (MIXER); not for general use.
相关信息：要求回复（非要求回复）的最新时间。RFC2156（混合器）；不适用于一般用途。
Description: Message importance
描述：消息重要性
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: A hint from the originator to the recipients about how important a message is. Values: High, normal, or low. Not used to control transmission speed. Proposed for use with RFC 2156 (MIXER) [10] and RFC 3801 (VPIM) [14].
相关信息：发起者向收件人提示消息的重要性。值：高、正常或低。不用于控制变速箱速度。建议与RFC 2156（混合器）[10]和RFC 3801（VPIM）[14]一起使用。
Description: Body parts are missing
描述：身体部位缺失
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Body parts are missing. RFC 2156 (MIXER); not for general use.
相关信息：身体部位缺失。RFC2156（混合器）；不适用于一般用途。
Description: Message priority
描述：消息优先级
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Can be 'normal', 'urgent', or 'non-urgent' and can influence transmission speed and delivery. RFC 2156 (MIXER); not for general use.
相关信息：可以是“正常”、“紧急”或“非紧急”，并可能影响传输速度和传输。RFC2156（混合器）；不适用于一般用途。
Description: Message content sensitivity
描述：消息内容敏感度
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: How sensitive it is to disclose this message to people other than the specified recipients. Values: Personal, private, and company confidential. The absence of this header field in messages gatewayed from X.400 indicates that the message is not sensitive. Proposed for use with RFC 2156 (MIXER) [10] and RFC 3801 (VPIM) [14].
相关信息：向指定收件人以外的人透露此邮件的敏感程度。价值观：个人、私人和公司机密。从X.400网关发送的消息中缺少此标头字段表示该消息不敏感。建议与RFC 2156（混合器）[10]和RFC 3801（VPIM）[14]一起使用。
Description: X.400 message content language
说明：X.400消息内容语言
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Can include a code for the natural language used in a message; e.g., 'en' for English. See also 'Content-Language'. RFC 2156 (MIXER); not for general use.
相关信息：可以包括消息中使用的自然语言代码；e、 “en”代表英语。另请参见“内容语言”。RFC2156（混合器）；不适用于一般用途。
Description: Conversion allowed?
描述：允许转换吗？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: The body of this message may not be converted from one character set to another. Values: prohibited and allowed. RFC 2156 (MIXER); not for general use.
相关信息：此邮件的正文不能从一个字符集转换为另一个字符集。值：禁止和允许。RFC2156（混合器）；不适用于一般用途。
Description: Lossy conversion allowed?
描述：允许有损转换吗？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: The body of this message may not be converted from one character set to another if information will be lost. Values: prohibited and allowed. RFC 2156 (MIXER); not for general use.
相关信息：如果信息丢失，此消息的正文可能无法从一个字符集转换为另一个字符集。值：禁止和允许。RFC2156（混合器）；不适用于一般用途。
Description: Message type: delivery report?
描述：邮件类型：传递报告？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Only used with the value 'Delivery Report' to indicate that this is a delivery report gatewayed from X.400. RFC 2156 (MIXER); not for general use.
相关信息：仅与值“Delivery Report”（交付报告）一起使用，表示这是从X.400网关传送的交付报告。RFC2156（混合器）；不适用于一般用途。
Description: Automatically submitted indicator
说明：自动提交的指标
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Has been automatically submitted. RFC 2156 (MIXER); not for general use.
相关信息：已自动提交。RFC2156（混合器）；不适用于一般用途。
Description: Automatically forwarded indicator
描述：自动转发指示器
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Has been automatically forwarded. RFC 2156 (MIXER), not for general use.
相关信息：已自动转发。RFC 2156（混合器），非通用型。
Description: X.400 IPM extensions discarded
描述：丢弃X.400 IPM扩展
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Can be used in Internet mail to indicate X.400 IPM extensions that could not be mapped to Internet mail format. RFC 2156 (MIXER); not for general use.
相关信息：可在Internet邮件中使用，表示无法映射到Internet邮件格式的X.400 IPM扩展。RFC2156（混合器）；不适用于一般用途。
Description: X.400 MTS extensions discarded
说明：放弃X.400 MTS扩展
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Can be used in Internet mail to indicate X.400 MTS extensions that could not be mapped to Internet mail format. RFC 2156 (MIXER); not for general use.
相关信息：可在Internet邮件中使用，表示无法映射到Internet邮件格式的X.400 MTS扩展。RFC2156（混合器）；不适用于一般用途。
Description: Disclose names of other recipients?
说明：是否披露其他收件人的姓名？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Tells whether recipients are to be told the names of other recipients of the same message. This is primarily an X.400 facility. In X.400, this is an envelope attribute and refers to disclosure of the envelope recipient list. Disclosure of other recipients is done in Internet mail via the To:, cc:, and bcc: header fields. Not for general use.
相关信息：告知收件人是否要告知同一邮件的其他收件人的姓名。这主要是一个X.400设施。在X.400中，这是信封属性，指的是信封收件人列表的披露。通过收件人：、抄送：、密件抄送：标题字段在Internet邮件中公开其他收件人。不适用于一般用途。
Description: Deferred delivery information
说明：延迟交货信息
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Provides information about deferred delivery service to the recipient. RFC 2156 (MIXER); not for general use.
相关信息：向收件人提供有关延迟交付服务的信息。RFC2156（混合器）；不适用于一般用途。
Description: Latest delivery time requested
描述：要求的最新交货时间
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Provides the recipient with information about requested delivery but will not be acted on by the SMTP infrastructure. RFC 2156 (MIXER); not for general use.
相关信息：向收件人提供有关请求传递的信息，但SMTP基础结构不会对其采取行动。RFC2156（混合器）；不适用于一般用途。
Description: Originator return address
描述：发起者返回地址
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Originator return address. RFC 2156 (MIXER); not for general use.
相关信息：发起者返回地址。RFC2156（混合器）；不适用于一般用途。
Description: Message content identifier
描述：消息内容标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: A text string that identifies the content of a message. Renamed version of obsolete Content-Identifier field. RFC 2156 (MIXER); not for general use.
相关信息：标识消息内容的文本字符串。已重命名过时内容标识符字段的版本。RFC2156（混合器）；不适用于一般用途。
Description: Return content on non-delivery?
描述：未交付时返回内容？
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: Indicates whether the content of a message is to be returned with non-delivery notifications. Renamed version of obsolete Content-Return field. RFC 2156 (MIXER); not for general use.
相关信息：指示是否返回邮件内容和未送达通知。已重命名过时内容返回字段的版本。RFC2156（混合器）；不适用于一般用途。
Description: X400 content type
说明：X400内容类型
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: X400 content type. RFC 2156 (MIXER); not for general use.
相关信息：X400内容类型。RFC2156（混合器）；不适用于一般用途。
Description: X400 MTS-Identifier
描述：X400 MTS标识符
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: X400 MTS-Identifier. RFC 2156 (MIXER); not for general use.
相关信息：X400 MTS标识符。RFC2156（混合器）；不适用于一般用途。
Description: X400 Originator
描述：X400发起人
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: X400 Originator. RFC 2156 (MIXER); not for general use.
相关信息：X400发起人。RFC2156（混合器）；不适用于一般用途。
Description: X400 Received
说明：收到X400
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: X400 Received. RFC 2156 (MIXER); not for general use.
相关信息：已收到X400。RFC2156（混合器）；不适用于一般用途。
Description: X400 Recipients
说明：X400收件人
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: X400 Recipients. RFC 2156 (MIXER); not for general use.
相关信息：X400收件人。RFC2156（混合器）；不适用于一般用途。
Description: X400 Trace
描述：X400跟踪
Applicable protocol: Mail [18]
适用协议：邮件[18]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2156 [10]
规范文件：RFC 2156[10]
Related information: X400 Trace. RFC 2156 (MIXER), not for general use.
相关信息：X400跟踪。RFC 2156（混合器），非通用型。
Header name Protocol
----------- --------
MIME-Version MIME MIME version number
Content-ID MIME Identify content body part
Content-Description MIME Description of message body part
Content-Transfer-Encoding
MIME Content transfer encoding applied
Content-Type MIME MIME content type
Content-Base MIME Base to be used for resolving
relative URIs within this content
part
Content-Location MIME URI for retrieving a body part
Content-features MIME Indicates content features of a
MIME body part
Content-Disposition MIME Intended content disposition and
file name
Content-Language MIME Language of message content
Content-Alternative MIME Alternative content available
Content-MD5 MIME MD5 checksum of content
Content-Duration MIME Time duration of content
Header name Protocol
----------- --------
MIME-Version MIME MIME version number
Content-ID MIME Identify content body part
Content-Description MIME Description of message body part
Content-Transfer-Encoding
MIME Content transfer encoding applied
Content-Type MIME MIME content type
Content-Base MIME Base to be used for resolving
relative URIs within this content
part
Content-Location MIME URI for retrieving a body part
Content-features MIME Indicates content features of a
MIME body part
Content-Disposition MIME Intended content disposition and
file name
Content-Language MIME Language of message content
Content-Alternative MIME Alternative content available
Content-MD5 MIME MD5 checksum of content
Content-Duration MIME Time duration of content
Description: MIME version number
描述：MIME版本号
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2045 [7] (section 4)
规范文件：RFC 2045[7]（第4节）
Related information: An indicator that this message is formatted according to the MIME standard, and an indication of which version of MIME is used.
相关信息：指示此消息是根据MIME标准格式化的，并指示使用哪个MIME版本。
Description: Identify content body part
描述：标识内容正文部分
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2045 [7] (section 7)
规范文件：RFC 2045[7]（第7节）
Related information: Specifies a Unique ID for one MIME body part of the content of a message.
相关信息：为消息内容的一个MIME正文部分指定唯一ID。
Description: Description of message body part
Description：消息正文部分的说明
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2045 [7] (section 8)
规范文件：RFC 2045[7]（第8节）
Related information: Description of a particular body part of a message; for example, a caption for an image body part.
相关信息：消息的特定正文部分的描述；例如，图像主体部分的标题。
Description: Content transfer encoding applied
描述：已应用内容传输编码
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2045 [7] (section 6)
规范文件：RFC 2045[7]（第6节）
Related information: Coding method used in a MIME message body part.
相关信息：MIME消息正文部分中使用的编码方法。
Description: MIME content type
描述：MIME内容类型
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2045 [7] (section 5)
规范文件：RFC 2045[7]（第5节）
Related information: Format of content (character set, etc.) Note that the values for this header field are defined in different ways in RFC 1049 and in MIME (RFC 2045). The 'MIME-version' header field will show whether Content-Type is to be interpreted according to RFC 1049 or according to MIME. The MIME definition should be used in generating mail. RFC 1049 has 'historic' status. RFC 1766 [5] defines a parameter 'difference' to this header field. Various other Content-Type define various additional parameters. For example, the parameter 'charset' is mandatory for all textual Content-Types. See also RFC 1049, RFC 1123: 5.2.13, and RFC 1766: 4.1.
相关信息：内容格式（字符集等）。请注意，此标题字段的值在RFC 1049和MIME（RFC 2045）中以不同的方式定义。“MIME版本”标题字段将显示是根据RFC 1049还是根据MIME解释内容类型。MIME定义应用于生成邮件。RFC 1049具有“历史”状态。RFC 1766[5]定义了此标头字段的参数“差异”。各种其他内容类型定义各种附加参数。例如，参数“charset”对于所有文本内容类型都是必需的。另见RFC 1049、RFC 1123:5.2.13和RFC 1766:4.1。
Description: Base to be used for resolving relative URIs within this content part.
描述：用于解析此内容部件中的相对URI的基。
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2110 [8]
规范文件：RFC 2110[8]
Related information: Base to be used for resolving relative URIs within this content part. See also Content-Location. This header was included in the first version of MHTML and HTTP 1.1 but removed in the second version (RFC 2557).
相关信息：用于解析此内容部件中的相对URI的基。另请参见内容位置。此标头包含在MHTML和HTTP 1.1的第一个版本中，但在第二个版本（RFC 2557）中被删除。
Description: URI for retrieving a body part
描述：用于检索身体部位的URI
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2557 [16]
规范文件：RFC 2557[16]
Related information: URI using which the content of this body-part part was retrieved, might be retrievable, or which otherwise gives a globally unique identification of the content.
相关信息：用于检索此正文部分内容的URI可能是可检索的，或者以其他方式提供内容的全局唯一标识。
Description: Indicates content features of a MIME body part
描述：指示MIME正文部分的内容特征
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2912 [19] (section 3)
规范文件：RFC 2912[19]（第3节）
Related information: The 'Content-features:' header can be used to annotate a MIME body part with a media feature expression, to indicate features of the body part content. See also RFC 2533, RFC 2506, and RFC 2045.
相关信息：“Content features:”标题可用于使用媒体功能表达式对MIME主体部分进行注释，以指示主体部分内容的功能。另见RFC 2533、RFC 2506和RFC 2045。
Description: Intended content disposition and file name
描述：预期的内容配置和文件名
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2183 [11]
规范文件：RFC 2183[11]
Related information: Indicates whether a MIME body part is to be shown inline or is an attachment; can also indicate a suggested filename for use when saving an attachment to a file.
相关信息：指示MIME主体部分是内联显示还是作为附件显示；还可以指示在将附件保存到文件时使用的建议文件名。
Description: Language of message content
描述：消息内容的语言
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 3282 [21]
规范文件：RFC 3282[21]
Related information: Can include a code for the natural language used in a message; e.g., 'en' for English. Can also contain a list of languages for a message containing more than one language.
相关信息：可以包括消息中使用的自然语言代码；e、 “en”代表英语。还可以包含包含多种语言的邮件的语言列表。
Description: Alternative content available
说明：可供选择的内容
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: work-in-progress
状态：正在进行的工作
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 3297 [22]
规范文件：RFC 3297[22]
Related information: Information about the media features of alternative content formats available for the current message.
相关信息：有关当前邮件可用的替代内容格式的媒体功能的信息。
Description: MD5 checksum of content
描述：内容的MD5校验和
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 1864 [6]
规范文件：RFC 1864[6]
Related information: Checksum of content to ensure that it has not been modified.
相关信息：内容校验和，以确保内容未被修改。
Description: Time duration of content
描述：内容的持续时间
Applicable protocol: MIME [7]
适用协议：MIME[7]
Status: standards-track
状态：标准跟踪
Author/change controller: IETF (mailto:iesg@ietf.org) Internet Engineering Task Force
作者/变更控制员：IETF（邮寄：iesg@ietf.org)互联网工程专责小组
Specification document(s): RFC 2424 [15]
规范文件：RFC 2424[15]
Related information: Time duration of body part content, in seconds (e.g., for audio message).
相关信息：身体部位内容的持续时间，以秒为单位（例如，对于音频消息）。
Section 2 of this specification provides initial registrations of mail and MIME header fields in the "Permanent Message Header Field Registry", defined by registration procedures for message header fields [1].
本规范第2节提供了“永久消息头字段注册表”中邮件和MIME头字段的初始注册，该注册表由消息头字段的注册过程定义[1]。
No security considerations are introduced by this registration document beyond those already inherent in use of the mail message header fields referenced.
除了在使用所引用的邮件消息头字段时已经固有的安全注意事项外，此注册文档不会引入其他安全注意事项。
Most of the information in this document has been derived from Jacob Palme's work in RFC 2076 [25] and subsequent updates [26]. The authors also gratefully acknowledge contributions and constructive input from Mark Nottingham, Bruce Lilly, Keith Moore, and Charles Lindsey (the mention of whom is not intended to imply their unqualified support for material herein).
本文件中的大部分信息来源于Jacob Palme在RFC 2076[25]中的工作以及随后的更新[26]。作者还感谢马克·诺丁汉、布鲁斯·莉莉、基思·摩尔和查尔斯·林赛（提及他们并不意味着他们对本文材料的无保留支持）的贡献和建设性意见。
[1] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, September 2004.
[1] Klyne，G.，Nottingham，M.和J.Mogul，“消息头字段的注册程序”，BCP 90，RFC 3864，2004年9月。
[2] Crocker, D., "Standard for the format of ARPA Internet text messages", STD 11, RFC 822, August 1982.
[2] Crocker，D.，“ARPA互联网文本信息格式标准”，STD 11，RFC 822，1982年8月。
[3] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", RFC 1327, May 1992.
[3] Hardcastle Kille，S.，“X.400（1988）/ISO 10021和RFC 822之间的映射”，RFC 1327，1992年5月。
[4] Costanzo, A., Robinson, D., and R. Ullmann, "Encoding Header Field for Internet Messages", RFC 1505, August 1993.
[4] Costanzo，A.，Robinson，D.，和R.Ullmann，“互联网消息的编码头字段”，RFC 15051993年8月。
[5] Alvestrand, H., "Tags for the Identification of Languages", RFC 1766, March 1995.
[5] Alvestrand，H.，“语言识别标签”，RFC1766，1995年3月。
[6] Myers, J. and M. Rose, "The Content-MD5 Header Field", RFC 1864, October 1995.
[6] Myers，J.和M.Rose，“Content-MD5标题字段”，RFC 18641995年10月。
[7] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[7] Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第一部分：互联网邮件正文格式”，RFC 20451996年11月。
[8] Palme, J. and A. Hopmann, "MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)", RFC 2110, March 1997.
[8] Palme，J.和A.Hopmann，“聚合文档的MIME电子邮件封装，如HTML（MHTML）”，RFC 2110，1997年3月。
[9] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[9] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[10] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME", RFC 2156, January 1998.
[10] Kille，S.，“混音器（Mime互联网X.400增强中继）：X.400和RFC 822/Mime之间的映射”，RFC 2156，1998年1月。
[11] Troost, R., Dorner, S., and K. Moore, "Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field", RFC 2183, August 1997.
[11] Troost，R.，Dorner，S.，和K.Moore，“在互联网消息中传达呈现信息：内容处置标题字段”，RFC 2183，1997年8月。
[12] Hansen, T. and G. Vaudreuil, "Message Disposition Notification", RFC 3798, May 2004.
[12] Hansen，T.和G.Vaudreuil，“消息处置通知”，RFC 3798，2004年5月。
[13] Neufeld, G. and J. Baer, "The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields", RFC 2369, July 1998.
[13] Neufeld，G.和J.Baer，“将URL用作核心邮件列表命令的元语法及其通过消息头字段的传输”，RFC 2369，1998年7月。
[14] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet Mail - version 2 (VPIMv2)", RFC 3801, June 2004.
[14] Vaudreuil，G.和G.Parsons，“互联网邮件语音配置文件-第2版（VPIMv2）”，RFC 3801，2004年6月。
[15] Vaudreuil, G. and G. Parsons, "Content Duration MIME Header Definition", RFC 3803, June 2004.
[15] Vaudreuil，G.和G.Parsons，“内容持续时间MIME头定义”，RFC 3803，2004年6月。
[16] Palme, J., Hopmann, A., and N. Shelness, "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)", RFC 2557, March 1999.
[16] Palme，J.，Hopmann，A.，和N.Shelness，“聚合文档的MIME封装，如HTML（MHTML）”，RFC2557，1999年3月。
[17] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, April 2001.
[17] 《简单邮件传输协议》，RFC 28212001年4月。
[18] Resnick, P., "Internet Message Format", RFC 2822, April 2001.
[18] Resnick，P.，“互联网信息格式”，RFC 2822，2001年4月。
[19] Klyne, G., "Indicating Media Features for MIME Content", RFC 2912, September 2000.
[19] Klyne，G.“为MIME内容指明媒体特征”，RFC 2912，2000年9月。
[20] Chandhok, R. and G. Wenger, "List-Id: A Structured Field and Namespace for the Identification of Mailing Lists", RFC 2919, March 2001.
[20] Chandhok，R.和G.Wenger，“列表Id：用于识别邮件列表的结构化字段和名称空间”，RFC 2919，2001年3月。
[21] Alvestrand, H., "Content Language Headers", RFC 3282, May 2002.
[21] Alvestrand，H.，“内容语言标题”，RFC 3282，2002年5月。
[22] Klyne, G., Iwazaki, R., and D. Crocker, "Content Negotiation for Messaging Services based on Email", RFC 3297, July 2002.
[22] Klyne，G.，Iwazaki，R.，和D.Crocker，“基于电子邮件的消息传递服务的内容协商”，RFC 3297，2002年7月。
[23] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message Context for Internet Mail", RFC 3458, January 2003.
[23] Burger，E.，Candell，E.，Eliot，C.，和G.Klyne，“互联网邮件的消息上下文”，RFC 3458，2003年1月。
[24] Miller, J., Krauskopf, T., Resnick, P. and W. Treese, "PICS Label Distribution Label Syntax and Communication Protocols", W3C Recommendation REC-PICS-labels, October 1996, <http://www.w3.org/TR/REC-PICS-labels>.
[24] Miller，J.，Krauskopf，T.，Resnick，P.和W.Treese，“PICS标签分发标签语法和通信协议”，W3C建议REC PICS标签，1996年10月<http://www.w3.org/TR/REC-PICS-labels>.
[25] Palme, J., "Common Internet Message Headers", RFC 2076, February 1997.
[25] Palme，J.，“通用互联网消息头”，RFC 2076，1997年2月。
[26] Palme, J., "Common Internet Message Header Fields", Work in Progress.
[26] Palme，J.，“通用互联网消息头字段”，正在进行中。
URIs
URI
[27] <http://www.ninebynine.org/IETF/Messaging/HdrRegistry/
Intro.html>
[27] <http://www.ninebynine.org/IETF/Messaging/HdrRegistry/
Intro.html>
Authors' Addresses
作者地址
Graham Klyne Image Bioinformatics Research Group Department of Zoology, University of Oxford South Parks Road, Oxford OX1 3PS, UK
格雷厄姆克林恩图像生物信息学研究组，牛津大学动物学系，牛津南公园路，英国OX1 3PS，美国
Phone: +44-(0)1865-281991
Fax: +44-(0)1865-310447
EMail: GK-IETF@ninebynine.org
Phone: +44-(0)1865-281991
Fax: +44-(0)1865-310447
EMail: GK-IETF@ninebynine.org
Jacob Palme Stockholm University/KTH Forum 100 Kista S-164 40 Sweden
雅各布·帕尔姆斯德哥尔摩大学/KTH论坛100基斯塔S-164 40瑞典
Phone: +46-8-16 16 67
Fax: +46-8-783 08 29
EMail: jpalme@dsv.su.se
Phone: +46-8-16 16 67
Fax: +46-8-783 08 29
EMail: jpalme@dsv.su.se
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。
G. Klyne, et al. Standards Track [Page 54]
G.Klyne等人，《标准轨道》[第54页]