RFC 8460: SMTP TLS Reporting
In plain English — editorial summary, not part of the RFC
A number of protocols exist for establishing encrypted channels between SMTP Mail Transfer Agents (MTAs), including STARTTLS, DNS- Based Authentication of Named Entities (DANE) TLSA, and MTA Strict Transport Security (MTA-STS). These protocols can fail due to misconfiguration or active attack, leading to undelivered messages or delivery over unencrypted or unauthenticated channels. This document describes a reporting mechanism and format by which sending systems can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations.
Document record
- Document ID
- RFC8460
- Published
- September 2018
- Authors
- D. Margolis; A. Brotman; B. Ramakrishnan; J. Jones; M. Risher
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8314Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and AccessUpdated
January 2018
- RFC 7672SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)Current
October 2015
- RFC 7671The DNS-Based Authentication of Named Entities (DANE) Protocol: Updates and Operational GuidanceCurrent
October 2015
- RFC 7250Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Current
June 2014
- RFC 7218Adding Acronyms to Simplify Conversations about DNS-Based Authentication of Named Entities (DANE)Current
April 2014
- RFC 8461SMTP MTA Strict Transport Security (MTA-STS)Current
September 2018
- RFC 8449Record Size Limit Extension for TLSCurrent
August 2018
- RFC 8471The Token Binding Protocol Version 1.0Current
October 2018
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?