RFC 4551: IMAP Extension for Conditional STORE Operation or Quick Flag Changes 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
Often, multiple IMAP (RFC 3501) clients need to coordinate changes to a common IMAP mailbox. Examples include different clients working on behalf of the same user, and multiple users accessing shared mailboxes. These clients need a mechanism to synchronize state changes for messages within the mailbox. They must be able to guarantee that only one client can change message state (e.g., message flags) at any time. An example of such an application is use of an IMAP mailbox as a message queue with multiple dequeueing clients. The Conditional Store facility provides a protected update mechanism for message state information that can detect and resolve conflicts between multiple writing mail clients. The Conditional Store facility also allows a client to quickly resynchronize mailbox flag changes. This document defines an extension to IMAP (RFC 3501). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4551
- Published
- June 2006
- Authors
- A. Melnikov; S. Hole
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 25
- Also known as
- —
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 4550Internet Email to Support Diverse Service Environments (Lemonade) ProfileObsoleted
June 2006
- RFC 4520Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)Current
June 2006
- RFC 4519Lightweight Directory Access Protocol (LDAP): Schema for User ApplicationsCurrent
June 2006
- RFC 4518Lightweight Directory Access Protocol (LDAP): Internationalized String PreparationCurrent
June 2006
- RFC 4517Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching RulesCurrent
June 2006
- RFC 4516Lightweight Directory Access Protocol (LDAP): Uniform Resource LocatorCurrent
June 2006
- RFC 4515Lightweight Directory Access Protocol (LDAP): String Representation of Search FiltersCurrent
June 2006
- RFC 4514Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished NamesCurrent
June 2006
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?