RFC 9586: IMAP Extension for Using and Returning Unique Identifiers (UIDs) Only
In plain English — editorial summary, not part of the RFC
The UIDONLY extension to the Internet Message Access Protocol (RFCs 3501 and 9051) allows clients to enable a mode in which information about mailbox changes is returned using only Unique Identifiers (UIDs). Message numbers are not returned in responses and cannot be used in requests once this extension is enabled. This helps both clients and servers to reduce resource usage required to maintain a map between message numbers and UIDs. This document defines an experimental IMAP extension.
Document record
- Document ID
- RFC9586
- Published
- May 2024
- Authors
- A. Melnikov; A. P. Achuthan; V. Nagulakonda; A. Singh; L. Alves
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9051Internet Message Access Protocol (IMAP) - Version 4rev2Current
August 2021
- RFC 9585IMAP Response Code for Command Progress NotificationsCurrent
May 2024
- RFC 9698The JMAPACCESS Extension for IMAPCurrent
January 2025
- RFC 9755IMAP Support for UTF-8Current
March 2025
- RFC 9979Registration of Further IMAP/JMAP Keywords and Mailbox Name AttributesCurrent
May 2026
- RFC 10022IMAP UIDBATCHES ExtensionCurrent
July 2026
- RFC 8514Internet Message Access Protocol (IMAP) - SAVEDATE ExtensionCurrent
January 2019
- RFC 8474IMAP Extension for Object IdentifiersCurrent
September 2018
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?