Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3501

Author:

A. Melnikov

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5182

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5182

Abstract

Many IMAP clients use the result of a SEARCH command as the input toperform 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 RFC3501; however, this would be suboptimal. The server will send the listof found messages to the client; after that, the client will have toparse the list, reformat it, and send it back to the server. Theclient can't pipeline the SEARCH command with the subsequent command,and, as a result, the server might not be able to perform someoptimizations.

This document proposes an IMAP extension that allows a client to tella server to use the result of a SEARCH (or Unique Identifier (UID)SEARCH) command as an input to any subsequent command. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.