RFC 3207: SMTP Service Extension for Secure SMTP over Transport Layer Security
In plain English — editorial summary, not part of the RFC
This document describes an extension to the SMTP (Simple Mail Transfer Protocol) service that allows an SMTP server and client to use TLS (Transport Layer Security) to provide private, authenticated communication over the Internet. This gives SMTP agents the ability to protect some or all of their communications from eavesdroppers and attackers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3207
- Published
- February 2002
- Authors
- P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7457Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)Current
February 2015
- RFC 7525Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Obsoleted
May 2015
- RFC 7590Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)Current
June 2015
- RFC 3030SMTP Service Extensions for Transmission of Large and Binary MIME MessagesCurrent
December 2000
- RFC 2852Deliver By SMTP Service ExtensionCurrent
June 2000
- RFC 2476Message SubmissionObsoleted
December 1998
- RFC 3268Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)Obsoleted
July 2002
- RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated
December 2002
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?