RFC 2449: POP3 Extension Mechanism
In plain English — editorial summary, not part of the RFC
This memo updates RFC 1939 to define a mechanism to announce support for optional commands, extensions, and unconditional server behavior. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2449
- Published
- November 1998
- Authors
- R. Gellens; C. Newman; L. Lundblade
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 19
- 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 2349TFTP Timeout Interval and Transfer Size OptionsCurrent
May 1998
- RFC 2348TFTP Blocksize OptionCurrent
May 1998
- RFC 2347TFTP Option ExtensionCurrent
May 1998
- RFC 2391Load Sharing using IP Network Address Translation (LSNAT)Current
August 1998
- RFC 2384POP URL SchemeCurrent
August 1998
- RFC 2318The text/css Media TypeCurrent
March 1998
- RFC 2595Using TLS with IMAP, POP3 and ACAPUpdated
June 1999
- RFC 2646The Text/Plain Format ParameterObsoleted
August 1999
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?