RFC 5162: IMAP4 Extensions for Quick Mailbox Resynchronization
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7162.
Current document in this lineage: RFC 7162 — IMAP Extensions: Quick Flag Changes Resynchronization (CONDSTORE) and Quick Mailbox Resynchronization (QRESYNC)
In plain English — editorial summary, not part of the RFC
This document defines an IMAP4 extension, which gives an IMAP client the ability to quickly resynchronize any previously opened mailbox as part of the SELECT command, without the need for server-side state or additional client round-trips. This extension also introduces a new response that allows for a more compact representation of a list of expunged messages (and always includes the Unique Identifiers (UIDs) expunged). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5162
- Published
- March 2008
- Authors
- A. Melnikov; D. Cridland; C. Wilson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 23
- Also known as
- —
- Obsoleted by:
- RFC 7162
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 4551 (2006)
- RFC 5162 (2008)
- RFC 7162 (2014) ✓
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 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
- RFC 5466IMAP4 Extension for Named Searches (Filters)Current
February 2009
- RFC 5738IMAP Support for UTF-8Obsoleted
March 2010
- RFC 4550Internet Email to Support Diverse Service Environments (Lemonade) ProfileObsoleted
June 2006
- RFC 5957Display-Based Address Sorting for the IMAP4 SORT ExtensionCurrent
July 2010
- RFC 4314IMAP4 Access Control List (ACL) ExtensionCurrent
December 2005
- RFC 5161The IMAP ENABLE ExtensionCurrent
March 2008
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?