RFC 5819: IMAP4 Extension for Returning STATUS Information in Extended LIST
In plain English — editorial summary, not part of the RFC
Many IMAP clients display information about total number of messages / total number of unseen messages in IMAP mailboxes. In order to do that, they are forced to issue a LIST or LSUB command and to list all available mailboxes, followed by a STATUS command for each mailbox found. This document provides an extension to LIST command that allows the client to request STATUS information for mailboxes together with other information typically returned by the LIST command. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5819
- Published
- March 2010
- Authors
- A. Melnikov; T. Sirainen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5258Internet Message Access Protocol version 4 - LIST Command ExtensionsCurrent
June 2008
- RFC 4314IMAP4 Access Control List (ACL) ExtensionCurrent
December 2005
- RFC 5364Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource ListsUpdated
October 2008
- 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 5825Displaying Downgraded Messages for Email Address InternationalizationObsoleted
April 2010
- RFC 5804A Protocol for Remotely Managing Sieve ScriptsUpdated
July 2010
- RFC 5784Sieve Email Filtering: Sieves and Display Directives in XMLCurrent
March 2010
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?