Permanent Message Header Field Names
Registration Procedure(s)
- Expert Review
Expert(s)
- Mark Baker (primary), Murray Kucherawy (backup)
Reference
- RFC 3864: Registration Procedures for Message Header Fields
- RFC-ietf-emailcore-rfc5322bis-12: Internet Message Format
Note
RFC 5504 specified that no new header fields be registered that begin with "Downgraded-". That restriction is now lifted, per RFC 6857.
Note
HTTP field name registrations have been moved to Hypertext Transfer Protocol (HTTP) Field Name Registry per RFC 9110.
Available Formats
| Header Field Name | Template | Protocol | Status | Trace | Reference |
|---|---|---|---|---|---|
| Accept-Language | RFC 4021 | ||||
| Also-Control | netnews | obsoleted | RFC 1849; RFC 5536 | ||
| Alternate-Recipient | RFC 4021 | ||||
| Approved | netnews | standard | RFC 5536 | ||
| ARC-Authentication-Results | experimental | RFC 8617 | |||
| ARC-Message-Signature | experimental | RFC 8617 | |||
| ARC-Seal | experimental | RFC 8617 | |||
| Archive | netnews | standard | RFC 5536 | ||
| Archived-At | standard | RFC 5064 | |||
| Archived-At | netnews | standard | RFC 5064 | ||
| Article-Names | netnews | obsoleted | RFC 1849; RFC 5536 | ||
| Article-Updates | netnews | obsoleted | RFC 1849; RFC 5536 | ||
| Authentication-Results | standard | RFC 8601 | |||
| Auto-Submitted | standard | RFC 3834, Section 5 | |||
| Autoforwarded | RFC 4021 | ||||
| Autosubmitted | RFC 4021 | ||||
| Base | MIME | obsoleted | RFC 1808; RFC 2068, Section 14.11 | ||
| Bcc | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.3 | ||
| Body | none | reserved | RFC 6068 | ||
| Cancel-Key | netnews | standard | RFC 8315 | ||
| Cancel-Lock | netnews | standard | RFC 8315 | ||
| Cc | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.3 | ||
| Comments | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.5 | ||
| Comments | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Content-Alternative | MIME | RFC 4021 | |||
| Content-Base | MIME | obsoleted | RFC 2110; RFC 2557 | ||
| Content-Description | MIME | RFC 4021 | |||
| Content-Disposition | MIME | RFC 4021 | |||
| Content-Duration | MIME | RFC 4021 | |||
| Content-features | MIME | RFC 4021 | |||
| Content-ID | MIME | RFC 4021 | |||
| Content-Identifier | RFC 4021 | ||||
| Content-Language | MIME | RFC 4021 | |||
| Content-Location | MIME | RFC 4021 | |||
| Content-MD5 | MIME | RFC 4021 | |||
| Content-Return | RFC 4021 | ||||
| Content-Transfer-Encoding | MIME | RFC 4021 | |||
| Content-Translation-Type | MIME | standard | RFC 8255 | ||
| Content-Type | MIME | RFC 4021; RFC 9788 | |||
| Control | netnews | standard | RFC 5536 | ||
| Conversion | RFC 4021 | ||||
| Conversion-With-Loss | RFC 4021 | ||||
| DL-Expansion-History | RFC 4021 | ||||
| Date | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.1 | ||
| Date | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Date-Received | netnews | obsoleted | RFC 850; RFC 5536 | ||
| Deferred-Delivery | RFC 4021 | ||||
| Delivery-Date | RFC 4021 | ||||
| Discarded-X400-IPMS-Extensions | RFC 4021 | ||||
| Discarded-X400-MTS-Extensions | RFC 4021 | ||||
| Disclose-Recipients | RFC 4021 | ||||
| Disposition-Notification-Options | RFC 4021 | ||||
| Disposition-Notification-To | RFC 4021 | ||||
| Distribution | netnews | standard | RFC 5536 | ||
| DKIM-Signature | standard | RFC 6376 | |||
| Downgraded-Bcc | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Cc | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Disposition-Notification-To | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Final-Recipient | standard | RFC 6857, Section 3.1.10 | |||
| Downgraded-From | obsoleted | RFC 5504; RFC 6857, Section 3.1.10 | |||
| Downgraded-In-Reply-To | standard | RFC 6857, Section 3.1.10 | |||
| Downgraded-Mail-From | obsoleted | RFC 5504; RFC 6857, Section 3.1.10 | |||
| Downgraded-Message-Id | standard | RFC 6857, Section 3.1.10 | |||
| Downgraded-Original-Recipient | standard | RFC 6857, Section 3.1.10 | |||
| Downgraded-Rcpt-To | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-References | standard | RFC 6857, Section 3.1.10 | |||
| Downgraded-Reply-To | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Resent-Bcc | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Resent-Cc | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Resent-From | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Resent-Reply-To | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Resent-Sender | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Resent-To | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Return-Path | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-Sender | obsoleted | RFC 5504; RFC 6857 | |||
| Downgraded-To | obsoleted | RFC 5504; RFC 6857 | |||
| Encoding | RFC 4021 | ||||
| Encrypted | RFC 4021 | ||||
| Expires | standard | RFC-ietf-mailmaint-expires-06 | |||
| Expires | netnews | standard | RFC 5536 | ||
| Expiry-Date | RFC 4021 | ||||
| Followup-To | netnews | standard | RFC 5536 | ||
| From | standard | no | RFC 6854; RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.2 | ||
| From | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Generate-Delivery-Report | RFC 4021 | ||||
| HP-Outer | standard | RFC 9788, Section 2.2.1 | |||
| Importance | RFC 4021 | ||||
| In-Reply-To | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.4 | ||
| Incomplete-Copy | RFC 4021 | ||||
| Injection-Date | netnews | standard | RFC 5536 | ||
| Injection-Info | netnews | standard | RFC 5536 | ||
| Keywords | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.5 | ||
| Keywords | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Language | RFC 4021 | ||||
| Latest-Delivery-Time | RFC 4021 | ||||
| Lines | netnews | deprecated | RFC 5536; RFC 3977 | ||
| List-Archive | RFC 4021 | ||||
| List-Help | RFC 4021 | ||||
| List-ID | RFC 4021 | ||||
| List-Owner | RFC 4021 | ||||
| List-Post | RFC 4021 | ||||
| List-Subscribe | RFC 4021 | ||||
| List-Unsubscribe | perm/list-unsubscribe | RFC 4021 | |||
| List-Unsubscribe-Post | standard | RFC 8058 | |||
| Message-Context | RFC 4021 | ||||
| Message-ID | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.4 | ||
| Message-ID | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Message-Type | RFC 4021 | ||||
| MIME-Version | MIME | RFC 4021 | |||
| MMHS-Exempted-Address | RFC 6477; ACP123 Appendix A1.1 and Appendix B.105 | ||||
| MMHS-Extended-Authorisation-Info | RFC 6477; ACP123 Appendix A1.2 and Appendix B.106 | ||||
| MMHS-Subject-Indicator-Codes | RFC 6477; ACP123 Appendix A1.3 and Appendix B.107 | ||||
| MMHS-Handling-Instructions | RFC 6477; ACP123 Appendix A1.4 and Appendix B.108 | ||||
| MMHS-Message-Instructions | RFC 6477; ACP123 Appendix A1.5 and Appendix B.109 | ||||
| MMHS-Codress-Message-Indicator | RFC 6477; ACP123 Appendix A1.6 and Appendix B.110 | ||||
| MMHS-Originator-Reference | RFC 6477; ACP123 Appendix A1.7 and Appendix B.111 | ||||
| MMHS-Primary-Precedence | RFC 6477; ACP123 Appendix A1.8 and Appendix B.101 | ||||
| MMHS-Copy-Precedence | RFC 6477; ACP123 Appendix A1.9 and Appendix B.102 | ||||
| MMHS-Message-Type | RFC 6477; ACP123 Appendix A1.10 and Appendix B.103 | ||||
| MMHS-Other-Recipients-Indicator-To | RFC 6477; ACP123 Appendix A1.12 and Appendix B.113 | ||||
| MMHS-Other-Recipients-Indicator-CC | RFC 6477; ACP123 Appendix A1.12 and Appendix B.113 | ||||
| MMHS-Acp127-Message-Identifier | RFC 6477; ACP123 Appendix A1.14 and Appendix B.116 | ||||
| MMHS-Originator-PLAD | RFC 6477; ACP123 Appendix A1.15 and Appendix B.117 | ||||
| MT-Priority | standard | RFC 6758 | |||
| Newsgroups | netnews | standard | RFC 5536 | ||
| NNTP-Posting-Date | netnews | obsoleted | RFC 5536 | ||
| NNTP-Posting-Host | netnews | obsoleted | RFC 2980; RFC 5536 | ||
| Obsoletes | RFC 4021 | ||||
| Organization | informational | RFC 7681 | |||
| Organization | netnews | standard | RFC 5536 | ||
| Original-Encoded-Information-Types | RFC 4021 | ||||
| Original-From | standard | RFC 5703 | |||
| Original-Message-ID | RFC 4021 | ||||
| Original-Recipient | perm/original-recipient | standard | RFC 3798; RFC 5337 | ||
| Original-Sender | netnews | standard | RFC 5537 | ||
| Originator-Return-Address | RFC 4021 | ||||
| Original-Subject | standard | RFC 5703 | |||
| Path | netnews | standard | RFC 5536 | ||
| PICS-Label | RFC 4021 | ||||
| Posting-Version | netnews | obsoleted | RFC 850; RFC 5536 | ||
| Prevent-NonDelivery-Report | RFC 4021 | ||||
| Priority | RFC 4021 | ||||
| Received | standard | yes | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.7; RFC-ietf-emailcore-rfc5321bis-43 | ||
| Received-SPF | standard | RFC 7208 | |||
| References | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.4 | ||
| References | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Relay-Version | netnews | obsoleted | RFC 850; RFC 5536 | ||
| Reply-By | RFC 4021 | ||||
| Reply-To | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.2 | ||
| Reply-To | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Require-Recipient-Valid-Since | standard | RFC 7293 | |||
| Resent-Bcc | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Resent-Cc | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Resent-Date | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Resent-From | standard | no | RFC 6854; RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Resent-Message-ID | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Resent-Reply-To | obsoleted | no | RFC-ietf-emailcore-rfc5322bis-12, Section 4.5.6 | ||
| Resent-Sender | standard | no | RFC 6854; RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Resent-To | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.6 | ||
| Return-Path | standard | yes | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.7; RFC-ietf-emailcore-rfc5321bis-43 | ||
| See-Also | netnews | obsoleted | RFC 1849; RFC 5536 | ||
| Sender | standard | no | RFC 6854; RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.2 | ||
| Sender | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Sensitivity | RFC 4021 | ||||
| Solicitation | RFC 3865 | ||||
| Subject | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.5 | ||
| Subject | netnews | standard | RFC 5536; RFC-ietf-emailcore-rfc5322bis-12 | ||
| Summary | netnews | standard | RFC 5536 | ||
| Supersedes | RFC 4021 | ||||
| Supersedes | netnews | standard | RFC 5536; RFC 2156 | ||
| TLS-Report-Domain | standard | RFC 8460 | |||
| TLS-Report-Submitter | standard | RFC 8460 | |||
| TLS-Required | standard | RFC 8689 | |||
| To | standard | no | RFC-ietf-emailcore-rfc5322bis-12, Section 3.6.3 | ||
| User-Agent | netnews | standard | RFC 5536; RFC 2616 | ||
| VBR-Info | standard | RFC 5518 | |||
| X400-Content-Identifier | RFC 4021 | ||||
| X400-Content-Return | RFC 4021 | ||||
| X400-Content-Type | RFC 4021 | ||||
| X400-MTS-Identifier | RFC 4021 | ||||
| X400-Originator | RFC 4021 | ||||
| X400-Received | RFC 4021 | ||||
| X400-Recipients | RFC 4021 | ||||
| X400-Trace | RFC 4021 | ||||
| Xref | netnews | standard | RFC 5536 |
Provisional Message Header Field Names
Registration Procedure(s)
- Expert Review
Expert(s)
- Mark Baker (primary), Murray Kucherawy (backup)
Reference
- RFC 3864: Registration Procedures for Message Header Fields
- RFC-ietf-emailcore-rfc5322bis-12: Internet Message Format
Note
Registration of a Provisional Message Header Field does not of itself imply any kind of endorsement by the IETF, IANA or any other body.
Note
HTTP field name registrations have been moved to Hypertext Transfer Protocol (HTTP) Field Name Registry per RFC 9110.
Available Formats
| Header Field Name | Template | Protocol | Status | Trace | Reference |
|---|---|---|---|---|---|
| Apparently-To | prov/apparently-to | RFC 2076 | |||
| Author | RFC 9057 | ||||
| CFBL-Address | RFC 9477 | ||||
| CFBL-Feedback-ID | RFC 9477 | ||||
| Delivered-To | RFC 9228 | ||||
| EDIINT-Features | RFC 6017 | ||||
| Eesst-Version | RFC 7681 | ||||
| Errors-To | prov/errors-to | RFC 2076 | |||
| Face | prov/face | https://quimby.gnus.org/circus/face | |||
| Face | prov/face | netnews | https://quimby.gnus.org/circus/face | ||
| Form-Sub | draft-levine-mailbomb-header-00 | ||||
| Jabber-ID | prov/jabber-id | RFC 7259 | |||
| Jabber-ID | prov/jabber-id | netnews | RFC 7259 | ||
| MMHS-Authorizing-Users | RFC 7912 | ||||
| Privicon | draft-koenig-privicons-01 | ||||
| SIO-Label | RFC 7444 | ||||
| SIO-Label-History | RFC 7444 | ||||
| Wrong-Recipient | prov/wrong-recipient | draft-ietf-mailmaint-wrong-recipient-00 | |||
| X-Archived-At | prov/x-archived-at | deprecated | RFC 5064 | ||
| X-Archived-At | prov/x-archived-at | netnews | deprecated | RFC 5064 | |
| X-Face | prov/x-face | https://purl.org/x-face-spec | |||
| X-Face | prov/x-face | netnews | https://purl.org/x-face-spec | ||
| X-Mittente | RFC 6109 | ||||
| X-PGP-Sig | prov/x-pgp-sig | netnews | ftp://ftp.isc.org/pub/pgpcontrol/FORMAT; https://ftp.isc.org/pub/pgpcontrol/FORMAT | ||
| X-Ricevuta | RFC 6109 | ||||
| X-Riferimento-Message-ID | RFC 6109 | ||||
| X-TipoRicevuta | RFC 6109 | ||||
| X-Trasporto | RFC 6109 | ||||
| X-VerificaSicurezza | RFC 6109 |
Content-Translation-Type Header Field Values
Registration Procedure(s)
- Specification Required
Expert(s)
- Nik Tomkinson
Reference
- RFC 8255: Multiple Language Content Type
Available Formats
| Value | Description | Reference |
|---|---|---|
| original | Content in the original language | RFC 8255 |
| human | Content that has been translated by a human translator or a human has checked and corrected an automated translation | RFC 8255 |
| automated | Content that has been translated by an electronic agent without proofreading or subsequent correction | RFC 8255 |