RFC 9051: Internet Message Access Protocol (IMAP) - Version 4rev2
In plain English — editorial summary, not part of the RFC
The Internet Message Access Protocol Version 4rev2 (IMAP4rev2) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev2 permits manipulation of mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev2 also provides the capability for an offline client to resynchronize with the server. IMAP4rev2 includes operations for creating, deleting, and renaming mailboxes; checking for new messages; removing messages permanently; setting and clearing flags; parsing per RFCs 5322, 2045, and 2231; searching; and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev2 are accessed by the use of numbers. These numbers are either message sequence numbers or unique identifiers. IMAP4rev2 does not specify a means of posting mail; this function is handled by a mail submission protocol such as the one specified in RFC 6409.
Document record
- Document ID
- RFC9051
- Published
- August 2021
- Authors
- A. Melnikov; B. Leiba
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 163
- Also known as
- —
- Obsoletes:
- RFC 3501
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 1730 (1994)
- RFC 2060 (1996)
- RFC 2061 (1996)
- RFC 3501 (2003)
- RFC 9051 (2021)
Read the full history of Internet Message Access Protocol (IMAP) - Version 4rev2 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9586IMAP Extension for Using and Returning Unique Identifiers (UIDs) OnlyCurrent
May 2024
- RFC 9585IMAP Response Code for Command Progress NotificationsCurrent
May 2024
- RFC 8514Internet Message Access Protocol (IMAP) - SAVEDATE ExtensionCurrent
January 2019
- RFC 8474IMAP Extension for Object IdentifiersCurrent
September 2018
- RFC 8438IMAP Extension for STATUS=SIZECurrent
August 2018
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
- RFC 9698The JMAPACCESS Extension for IMAPCurrent
January 2025
- RFC 9755IMAP Support for UTF-8Current
March 2025
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?