RFC 2554: SMTP Service Extension for Authentication
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4954.
Current version: RFC 4954 — SMTP Service Extension for Authentication
In plain English — editorial summary, not part of the RFC
This document defines an SMTP service extension [ESMTP] whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2554
- Published
- March 1999
- Authors
- J. Myers
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 4954
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 2487SMTP Service Extension for Secure SMTP over TLSObsoleted
January 1999
- RFC 2505Anti-Spam Recommendations for SMTP MTAsCurrent
February 1999
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2197SMTP Service Extension for Command PipeliningObsoleted
September 1997
- RFC 2034SMTP Service Extension for Returning Enhanced Error CodesCurrent
October 1996
- RFC 2033Local Mail Transfer ProtocolCurrent
October 1996
- RFC 1985SMTP Service Extension for Remote Message Queue StartingCurrent
August 1996
- RFC 2818HTTP Over TLSObsoleted
May 2000
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?