Protocols
Saved & recent

IMAP

Also called: Internet Message Access Protocol, IMAP4rev2

Internet Message Access Protocol lets a client work with email stored on a server. It supports mailboxes, message flags such as read status, searching, and fetching selected message parts. This server-based model helps multiple devices maintain a consistent view while also allowing local caches for offline use.

For example, a phone can fetch message headers first and download a large attachment only when opened. Marking the message as read changes a server flag that another client can observe. IMAP manages mailbox access; sending a new email uses a separate submission service. IMAP4rev2 is specified in RFC 9051.

Related
Email submission, POP3, MIME
Further reading
RFC 9051 — Internet Message Access Protocol (IMAP) — Version 4rev2
phone server mailbox laptop fetch header first header returned fetch attachment later attachment returned mark read header unread → read attachment shared mailbox state
IMAP exposes the server’s message headers, flags and attachment parts separately. The phone can fetch headers first and an attachment later. A laptop can update the shared seen flag; other clients observe it when they synchronize. Sending mail is a different service.

View in the full Protocols collection