RFC 5182: IMAP Extension for Referencing the Last SEARCH Result
In plain English — editorial summary, not part of the RFC
Many IMAP clients use the result of a SEARCH command as the input to perform another operation, for example, fetching the found messages, deleting them, or copying them to another mailbox. This can be achieved using standard IMAP operations described in RFC 3501; however, this would be suboptimal. The server will send the list of found messages to the client; after that, the client will have to parse the list, reformat it, and send it back to the server. The client can't pipeline the SEARCH command with the subsequent command, and, as a result, the server might not be able to perform some optimizations. This document proposes an IMAP extension that allows a client to tell a server to use the result of a SEARCH (or Unique Identifier (UID) SEARCH) command as an input to any subsequent command. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5182
- Published
- March 2008
- Authors
- A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 3501
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5162IMAP4 Extensions for Quick Mailbox ResynchronizationObsoleted
March 2008
- RFC 5161The IMAP ENABLE ExtensionCurrent
March 2008
- RFC 4978The IMAP COMPRESS ExtensionCurrent
August 2007
- RFC 4959IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client ResponseCurrent
September 2007
- RFC 5464The IMAP METADATA ExtensionCurrent
February 2009
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
- RFC 5466IMAP4 Extension for Named Searches (Filters)Current
February 2009
- RFC 4731IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is ReturnedUpdated
November 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?