RFC 2061: IMAP4 Compatibility with IMAP2bis
In plain English — editorial summary, not part of the RFC
This document is intended to be read along with RFC 1176 and the most recent IMAP4 specification (RFC 2060) to assist implementors in creating an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2061
- Published
- December 1996
- Authors
- M. Crispin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 3
- Also known as
- —
- Obsoletes:
- RFC 1730
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Read the full history of Internet Message Access Protocol (IMAP) - Version 4rev2 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
- RFC 2095IMAP/POP AUTHorize Extension for Simple Challenge/ResponseObsoleted
January 1997
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2193IMAP4 Mailbox ReferralsCurrent
September 1997
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?