Skip to main content

SMTP Service Extension for Secure SMTP over Transport Layer Security

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3207.
Author Paul E. Hoffman
Last updated 2020-01-21 (Latest revision 2001-11-05)
RFC stream Legacy stream
Intended RFC status Proposed Standard
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3207 (Proposed Standard)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3207

        Title:      SMTP Service Extension for
                    Secure SMTP over Transport Layer Security
        Author(s):  P. Hoffman
        Status:     Standards Track
        Date:       February 2002
        Pages:      9
        Characters: 18679
        Obsoletes:  2487

        I-D Tag:    draft-hoffman-rfc2487bis-06.txt


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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.