RFC 2180: IMAP4 Multi-Accessed Mailbox Practice
In plain English — editorial summary, not part of the RFC
The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2180
- Published
- July 1997
- Authors
- M. Gahrns
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2221IMAP4 Login ReferralsCurrent
October 1997
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2195IMAP/POP AUTHorize Extension for Simple Challenge/ResponseCurrent
September 1997
- RFC 2095IMAP/POP AUTHorize Extension for Simple Challenge/ResponseObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
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?