RFC 7912: Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure
In plain English — editorial summary, not part of the RFC
This document describes a procedure for when a Military Message Handling System (MMHS) message is composed by one user and is only released to the mail transfer system when one or more Authorizing Users authorize release of the message by adding the MMHS-Authorizing-Users header field. The resulting message can be optionally signed by the sender and/or reviewer, allowing recipients to verify both the original signature (if any) and the review signatures.
Document record
- Document ID
- RFC7912
- Published
- June 2016
- Authors
- A. Melnikov
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 7681Email Exchange of Secondary School TranscriptsCurrent
October 2015
- RFC 7489Domain-based Message Authentication, Reporting, and Conformance (DMARC)Obsoleted
March 2015
- RFC 7444Security Labels in Internet EmailCurrent
February 2015
- RFC 7281Authentication-Results Registration for S/MIME Signature VerificationCurrent
June 2014
- RFC 7259The Jabber-ID Header FieldCurrent
May 2014
- RFC 8904DNS Whitelist (DNSWL) Email Authentication Method ExtensionCurrent
September 2020
- RFC 9057Email Author Header FieldCurrent
June 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?