RFC 1733: Distributed Electronic Mail Models in IMAP4
In plain English — editorial summary, not part of the RFC
There are three fundamental models of client/server email: offline, online, and disconnected use. IMAP4 can be used in any one of these three models. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1733
- Published
- December 1994
- Authors
- M. Crispin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 3
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1732IMAP4 Compatibility with IMAP2 and IMAP2bisCurrent
December 1994
- RFC 1731IMAP4 Authentication MechanismsCurrent
December 1994
- RFC 5092IMAP URL SchemeUpdated
November 2007
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 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?