RFC 5258: Internet Message Access Protocol version 4 - LIST Command Extensions
In plain English — editorial summary, not part of the RFC
IMAP4 has two commands for listing mailboxes: LIST and LSUB. As we have added extensions, such as Mailbox Referrals, that have required specialized lists we have had to expand the number of list commands, since each extension must add its function to both LIST and LSUB, and these commands are not, as they are defined, extensible. If we've needed the extensions to work together, we've had to add a set of commands to mix the different options, the set increasing in size with each new extension. This document describes an extension to the base LIST command that will allow these additions to be done with mutually compatible options to the LIST command, avoiding the exponential increase in specialized list commands. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5258
- Published
- June 2008
- Authors
- B. Leiba; A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5819IMAP4 Extension for Returning STATUS Information in Extended LISTCurrent
March 2010
- RFC 1730Internet Message Access Protocol - Version 4Obsoleted
December 1994
- RFC 8440IMAP4 Extension for Returning MYRIGHTS Information in Extended LISTCurrent
August 2018
- RFC 9590IMAP Extension for Returning Mailbox METADATA in Extended LISCurrent
May 2024
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 2008
- RFC 5173Sieve Email Filtering: Body ExtensionCurrent
April 2008
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5703Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and EnclosureCurrent
October 2009
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?