End-to-end cryptographic protections for email messages can provide useful security. However, the standards for providing cryptographic protection are extremely flexible. That flexibility can trap users and cause surprising failures. This document offers guidance for Mail User Agent (MUA) implementers to help mitigate those risks and to make end-to-end email simple and secure for the end user. It provides a useful set of vocabulary as well as recommendations to avoid common failures. It also identifies a number of currently unsolved usability and interoperability problems.
IETF · RFCОфициальная английская аннотация
End-to-end cryptographic protections for email messages can provide useful security. However, the standards for providing cryptographic protection are extremely flexible. That flexibility can trap users and cause surprising failures. This document offers guidance for Mail User Agent (MUA) implementers to help mitigate those risks and to make end-to-end email simple and secure for the end user. It provides a useful set of vocabulary as well as recommendations to avoid common failures. It also identifies a number of currently unsolved usability and interoperability problems.
{
"id": "RFC9787",
"number": 9787,
"title_en": "Guidance on End-to-End Email Security",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "End-to-end cryptographic protections for email messages can provide useful security. However, the standards for providing cryptographic protection are extremely flexible. That flexibility can trap users and cause surprising failures. This document offers guidance for Mail User Agent (MUA) implementers to help mitigate those risks and to make end-to-end email simple and secure for the end user. It provides a useful set of vocabulary as well as recommendations to avoid common failures. It also identifies a number of currently unsolved usability and interoperability problems.",
"authors": [
"D. K. Gillmor",
"A. Melnikov",
"B. Hoeneisen"
],
"organizations": [],
"publication_date": "2025-08-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "IETF",
"stream_ru": "IETF",
"area": "sec",
"area_ru": "Безопасность",
"working_group": "lamps",
"source_draft": "draft-ietf-lamps-e2e-mail-guidance-17",
"page_count": 53,
"doi": "10.17487/RFC9787",
"keywords": [
"cryptography",
"encryption",
"signature",
"signing",
"usability",
"MIME",
"confidentiality",
"integrity",
"authenticity"
],
"formats": [
"HTML",
"TXT",
"PDF",
"XML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc9787/",
"html": "https://www.rfc-editor.org/rfc/rfc9787.html",
"txt": "https://www.rfc-editor.org/rfc/rfc9787.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc9787/"
}
}