Skip to main content

Internet Message Access Protocol (IMAP) - Version 4rev2
RFC 9051

Revision differences

Document history

Date By Action
2023-07-28
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2022-02-03
(System) Received changes through RFC Editor sync (added Errata tag)
2021-08-26
(System) IANA registries were updated to include RFC9051
2021-08-23
(System)
Received changes through RFC Editor sync (created alias RFC 9051, changed abstract to 'The Internet Message Access Protocol Version 4rev2 (IMAP4rev2) allows a client …
Received changes through RFC Editor sync (created alias RFC 9051, changed abstract to '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.', changed pages to 163, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-08-23, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-extra-imap4rev2 and RFC 3501)
2021-08-23
(System) RFC published