RFC 6237: IMAP4 Multimailbox SEARCH Extension
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7377.
Current version: RFC 7377 — IMAP4 Multimailbox SEARCH Extension
In plain English — editorial summary, not part of the RFC
The IMAP4 specification allows the searching of only the selected mailbox. A user often wants to search multiple mailboxes, and a client that wishes to support this must issue a series of SELECT and SEARCH commands, waiting for each to complete before moving on to the next. This extension allows a client to search multiple mailboxes with one command, limiting the round trips and waiting for various searches to complete, and not requiring disruption of the currently selected mailbox. This extension also uses MAILBOX and TAG fields in ESEARCH responses, allowing a client to pipeline the searches if it chooses. This document updates RFC 4466. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6237
- Published
- May 2011
- Authors
- B. Leiba; A. Melnikov
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
Topics
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 6203IMAP4 Extension for Fuzzy SearchCurrent
March 2011
- RFC 6154IMAP LIST Extension for Special-Use MailboxesCurrent
March 2011
- RFC 6132Sieve Notification Using Presence InformationCurrent
July 2011
- RFC 6131Sieve Vacation Extension: "Seconds" ParameterCurrent
July 2011
- RFC 6686Resolution of the Sender Policy Framework (SPF) and Sender ID ExperimentsCurrent
July 2012
- RFC 5721POP3 Support for UTF-8Obsoleted
February 2010
- RFC 5703Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and EnclosureCurrent
October 2009
- RFC 6785Support for Internet Message Access Protocol (IMAP) Events in SieveCurrent
November 2012
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?