INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
RFC 3501, “INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1”, is a Proposed Standard document published in March 2003 by M. Crispin. It obsoletes RFC 2060. It has since been updated by RFC 4466, RFC 4469, RFC 4551, RFC 5032, RFC 5182, RFC 5738, RFC 6186, RFC 6858, RFC 7817, RFC 8314, RFC 8437, RFC 8474, RFC 8996. It has been obsoleted by RFC 9051 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev1 permits manipulation of mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev1 also provides the capability for an offline client to resynchronize with the server. IMAP4rev1 includes operations for creating, deleting, and renaming mailboxes, checking for new messages, permanently removing messages, setting and clearing flags, RFC 2822 and RFC 2045 parsing, searching, and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev1 are accessed by the use of numbers. These numbers are either message sequence numbers or unique identifiers. IMAP4rev1 supports a single server. A mechanism for accessing configuration information to support multiple IMAP4rev1 servers is discussed in RFC 2244. IMAP4rev1 does not specify a means of posting mail; this function is handled by a mail transfer protocol such as RFC 2821. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3501 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3502 Internet Message Access Protocol - MULTIAPPEND Extension
- RFC 3499 Request for Comments Summary RFC Numbers 3400-3499
- RFC 3503 Message Disposition Notification profile for Internet Message Access Protocol
- RFC 3498 Definitions of Managed Objects for Synchronous Optical Network Linear Automatic Protection Switching Architectures
- RFC 3504 Internet Open Trading Protocol Version 1, Errata
- RFC 3497 RTP Payload Format for Society of Motion Picture and Television Engineers 292M Video
- RFC 3505 Electronic Commerce Modeling Language : Version 2 Requirements
- RFC 3496 Protocol Extension for Support of Asynchronous Transfer Mode Service Class-aware Multiprotocol Label Switching Traffic Engineering