RFC 2359: IMAP4 UIDPLUS extension
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4315.
Current version: RFC 4315 — Internet Message Access Protocol (IMAP) - UIDPLUS extension
In plain English — editorial summary, not part of the RFC
The UIDPLUS extension of the Internet Message Access Protocol [IMAP4] provides a set of features intended to reduce the amount of time and resources used by some client operations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2359
- Published
- June 1998
- Authors
- J. Myers
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 4315
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 2221IMAP4 Login ReferralsCurrent
October 1997
- RFC 2195IMAP/POP AUTHorize Extension for Simple Challenge/ResponseCurrent
September 1997
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 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
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?