IMAP

IMAP
Name	IMAP
Full name	Internet Message Access Protocol
Introduced	1986
Developer	Jon Postel; Mark Crispin
Type	Application layer protocol
Transport	Transmission Control Protocol
Port	143, 993

IMAP IMAP is a client–server protocol for accessing electronic mail on a remote server, enabling synchronized mailbox management, selective message retrieval, and server-side search. Widely used alongside Post Office Protocol, SMTP, and DNS, IMAP shaped interactions between mail user agents and mail transfer agents, influencing software from Microsoft Exchange Server to Dovecot and client applications such as Mozilla Thunderbird, Apple Mail, and Microsoft Outlook. Implementations and extensions intersect with standards work by Internet Engineering Task Force, experimental deployments at MIT, and operational policies at providers like Google, Yahoo!, and AOL.

Overview

IMAP provides stateful access to mailboxes on a remote host, supporting multiple concurrent clients, folder hierarchies, and message flags. It contrasts with Post Office Protocol by retaining mail on the server, enabling synchronization across devices used by organizations such as NASA, United States Postal Service, and corporations like IBM or AT&T. Core operations include FETCH, STORE, COPY, and SEARCH; these are implemented in servers used in projects like Cyrus IMAP and Courier Mail Server and consumed by clients including Outlook Express, Evolution (software), and K-9 Mail.

History and Development

Design work began in the mid-1980s at institutions such as University of Washington and research by Mark Crispin, with early RFCs produced under auspices of Jon Postel and the IETF working groups. IMAP evolved through versions—IMAP2, IMAP3 proposals, and the widely deployed IMAP4rev1—mirroring contemporaneous protocols like SMTP and influenced by message storage research at MIT Project Athena. Commercial adoption accelerated in the 1990s with services from CompuServe, Procmail integrations, and later with webmail innovations from Hotmail and Gmail, which encouraged IMAP extensions for synchronization and mobile access.

Protocol Specifications

The protocol operates on Transmission Control Protocol ports 143 (unencrypted or STARTTLS) and 993 (implicit TLS). Syntax and semantics are defined in RFC documents produced by the IETF and reference implementations by University of Washington and Cyrus IMAP. Commands such as LOGIN, AUTHENTICATE, SELECT, FETCH, STORE, and LOGOUT follow a tagged command/response model similar to protocols used by FTP and HTTP/1.1 semantics. Message formats rely on Multipurpose Internet Mail Extensions for MIME handling and interact with header fields defined in RFC 5322 and RFC 2045 series.

Authentication and Security

IMAP supports multiple authentication mechanisms standardized by the IETF SASL framework, including PLAIN, LOGIN, CRAM-MD5, DIGEST-MD5, and more secure mechanisms like SCRAM-SHA-1 and SCRAM-SHA-256 used by providers such as Google and Microsoft. Transport security is provided via STARTTLS negotiation or TLS on dedicated ports, following guidance from IETF and cipher recommendations from National Institute of Standards and Technology. Deployment considerations involve account federation with LDAP, integration with Kerberos realms such as those used at MIT, and multi-factor solutions deployed by enterprises including Amazon Web Services and Dropbox.

Client and Server Implementations

Major server implementations include Cyrus IMAP, Dovecot, Courier Mail Server, UW-IMAP, and commercial systems embedded in Microsoft Exchange Server and Zimbra. Client software supporting the protocol spans Mozilla Thunderbird, Apple Mail, Microsoft Outlook, Roundcube, Evolution (software), and mobile apps for iOS and Android like Airmail and K-9 Mail. Integrations exist in mail gateways and filtering stacks involving SpamAssassin, Procmail, Amavis, and storage backends such as PostgreSQL and Cassandra in cloud environments like Google Cloud Platform and Microsoft Azure.

Extensions and Related Standards

The community extended IMAP with capabilities such as IDLE for push notifications, CONDSTORE and QRESYNC for efficient synchronization, and ANNOTATE for metadata. These and related drafts appeared in IETF working groups and interoperate with standards like Sieve (mail filtering language) for server-side filtering and LMTP for local delivery. Cloud and mobile use prompted work on protocols like JMAP as an alternative, while interoperability requires attention to MIME extensions defined by IETF and storage consistency models used by distributed systems such as Apache Cassandra or Ceph.

Usage and Deployment Considerations

Administrators balance storage models (maildir vs mbox), concurrency limits, and indexing strategies to serve user populations at organizations like Universities (e.g., Stanford University mail deployments) and enterprises such as Salesforce. Operational choices include replication via DRBD or GlusterFS, backup strategies using Bacula or Amanda, and scaling with load balancers from vendors like F5 Networks or cloud-native services on Amazon Web Services. Monitoring, compliance, and legal hold integrate with tools from Splunk and Elastic (company), while privacy and data protection must align with regulations such as HIPAA and GDPR in international deployments.

Category:Email protocols