Visual RFC.
ALL RFCs / RFC 9051
Read the RFC ↗
RFC 9051 / MECHANISM GUIDE

Unsolicited updates and resync

05

The server can report changes while a client is connected, and saved UID state helps reconnecting clients.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5.2 ↗
RFC 9051 · § 5.2EXAMPLE
3 / 3
Unsolicited updates and resyncThe server can report changes while a client is connected, and saved UID state helps reconnecting clients.Unsolicited updates and resyncClientServerIDLE* 4 EXISTSreconnect: check UIDVALIDITYA changed UIDVALIDITY invalidates saved mappings
03
Resynchronize on reconnect

Check UIDVALIDITY before reusing saved UID mappings.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Clients must be prepared for allowed untagged responses.

  • Clients must be prepared for allowed untagged responses.
  • IDLE is incorporated into IMAP4rev2 for waiting on mailbox updates.
  • UIDVALIDITY changes invalidate assumptions about saved UID identity.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Session and mailbox states
  2. UIDs versus sequence numbers
  3. Selective FETCH and SEARCH
  4. Flags and deletion
  5. Unsolicited updates and resync
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗