634 captures
24 Dec 2004 - 02 Jul 2022
About this capture
Internet Message Access Protocol
Jump to: navigation, search
"IMAP" redirects here. For the antipsychotic, see Fluspirilene​.
Internet protocol suite
Application layer
Transport layer
Internet layer
Link layer
This article's lead section may not adequately summarize key points of its contents. Please consider expanding the lead to provide an accessible overview of all important aspects of the article. (February 2014)
Internet Message Access Protocol (IMAP) is a protocol for e-mail retrieval and storage developed in 1986 by Mark Crispin.
1 E-mail protocols
2 History
2.1 Original IMAP
2.2 IMAP2
2.3 IMAP3
2.4 IMAP2bis
2.5 IMAP4
3 Advantages over POP
3.1 Connected and disconnected modes of operation
3.2 Multiple clients simultaneously connected to the same mailbox
3.3 Access to MIME message parts and partial fetch
3.4 Message state information
3.5 Multiple mailboxes on the server
3.6 Server-side searches
3.7 Built-in extension mechanism
4 Disadvantages
5 Security
6 Dialog example
7 See also
8 References
9 Further reading
10 External links
E-mail protocols​[​edit​]
The Internet Message Access Protocol (commonly known as IMAP) is an Application Layer Internet protocol that allows an e-mail client to access e-mail on a remote mail server. The current version, IMAP version 4 revision 1 (IMAP4rev1), is defined by RFC 3501. An IMAP server typically listens on well-known port 143. IMAP over SSL (IMAPS) is assigned well-known port number 993.
IMAP supports both on-line and off-line modes of operation. E-mail clients using IMAP generally leave messages on the server until the user explicitly deletes them. This and other characteristics of IMAP operation allow multiple clients to manage the same mailbox. Most e-mail clients support IMAP in addition to Post Office Protocol (POP) to retrieve messages; however, fewer e-mail services support IMAP.[1] IMAP offers access to the mail storage. Clients may store local copies of the messages, but these are considered to be a temporary cache.[2]
Incoming e-mail messages are sent to an e-mail server that stores messages in the recipient's e-mail box. The user retrieves the messages with an e-mail client that uses one of a number of e-mail retrieval protocols. Some clients and servers preferentially use vendor-specific, proprietary protocols, but most support SMTP for sending e-mail and POP and IMAP for retrieving e-mail, allowing interoperability with other servers and clients. For example, Microsoft​'s Outlook client uses MAPI, a Microsoft proprietary protocol to communicate with a Microsoft Exchange Server. IBM's Notes client works in a similar fashion when communicating with a Domino server. All of these products also support POP, IMAP, and outgoing SMTP. Support for the Internet standard protocols​[​citation needed] allows many e-mail clients such as Pegasus Mail or Mozilla Thunderbird to access these servers, and allows the clients to be used with other servers.
IMAP was designed by Mark Crispin in 1986 as a remote mailbox protocol, in contrast to the widely used POP, a protocol for retrieving the contents of a mailbox.​[​3​]
IMAP was previously known as Internet Mail Access Protocol, Interactive Mail Access Protocol (RFC 1064), and Interim Mail Access Protocol​.​[​4​]
Original IMAP[edit]
The original Interim Mail Access Protocol was implemented as a Xerox Lisp machine client and a TOPS-20 server.
No copies of the original interim protocol specification or its software exist.​[​citation needed] Although some of its commands and responses were similar to IMAP2, the interim protocol lacked command/response tagging and thus its syntax was incompatible with all other versions of IMAP.
The interim protocol was quickly replaced by the Interactive Mail Access Protocol (IMAP2), defined in RFC 1064 (in 1988) and later updated by RFC 1176 (in 1990). IMAP2 introduced command/response tagging and was the first publicly distributed version.
IMAP3 is an extremely rare variant of IMAP.[5] It was published as RFC 1203 in 1991. It was written specifically as a counter proposal to RFC 1176, which itself proposed modifications to IMAP2.[6] IMAP3 was never accepted by the marketplace.​[​7​]​[​8​] The IESG reclassified RFC1203 "Interactive Mail Access Protocol - Version 3" as a Historic protocol in 1993. The IMAP Working Group used RFC1176 (IMAP2) rather than RFC1203 (IMAP3) as its starting point.​[​9​]​[​10​]
With the advent of MIME, IMAP2 was extended to support MIME body structures and add mailbox management functionality (create, delete, rename, message upload) that was absent in IMAP2. This experimental revision was called IMAP2bis; its specification was never published in non-draft form. An internet draft of IMAP2bis was published by the IETF IMAP Working Group in October 1993. This draft was based upon the following earlier specifications: unpublished IMAP2bis.TXT document, RFC1176, and RFC1064 (IMAP2).​[​11​] The IMAP2bis.TXT draft documented the state of extensions to IMAP2 as of December 1992.[12] Early versions of Pine were widely distributed with IMAP2bis support[5] (Pine 4.00 and later supports IMAP4rev1).
An IMAP Working Group formed in the IETF in the early 1990s took over responsibility for the IMAP2bis design. The IMAP WG decided to rename IMAP2bis to IMAP4 to avoid confusion with a competing IMAP3 proposal from another group that never got off the ground.​[​citation needed] The expansion of the IMAP acronym also changed to the Internet Message Access Protocol. The latest version, IMAP4, allows an email client to manipulate email messages stored on a server in the same way as a client using local folders. This ability allows multiple clients for a single user to see the same mailbox status. For example, if a user moves a message from the user's INBOX to some other folder using one client, when later accessing the mailbox from another client the message appears in the folder to which it was moved.
Advantages over POP[edit]
Connected and disconnected modes of operation​[​edit​]
When using POP, clients typically connect to the e-mail server briefly, only as long as it takes to download new messages. When using IMAP4, clients often stay connected as long as the user interface is active and download message content on demand. For users with many or large messages, this IMAP4 usage pattern can result in faster response times.
Multiple clients simultaneously connected to the same mailbox​[​edit​]
The POP protocol requires the currently connected client to be the only client connected to the mailbox. In contrast, the IMAP protocol specifically allows simultaneous access by multiple clients and provides mechanisms for clients to detect changes made to the mailbox by other, concurrently connected, clients. See for example RFC3501 section 5.2 which specifically cites "simultaneous access to the same mailbox by multiple agents" as an example.
Access to MIME message parts and partial fetch[edit]
Usually all Internet e-mail is transmitted in MIME format, allowing messages to have a tree structure where the leaf nodes are any of a variety of single part content types and the non-leaf nodes are any of a variety of multipart types. The IMAP4 protocol allows clients to retrieve any of the individual MIME parts separately and also to retrieve portions of either individual parts or the entire message. These mechanisms allow clients to retrieve the text portion of a message without retrieving attached files or to stream content as it is being fetched.
Message state information​[​edit​]
Through the use of flags defined in the IMAP4 protocol, clients can keep track of message state: for example, whether or not the message has been read, replied to, or deleted. These flags are stored on the server, so different clients accessing the same mailbox at different times can detect state changes made by other clients. POP provides no mechanism for clients to store such state information on the server so if a single user accesses a mailbox with two different POP clients (at different times), state information—such as whether a message has been accessed—cannot be synchronized between the clients. The IMAP4 protocol supports both predefined system flags and client-defined keywords. System flags indicate state information such as whether a message has been read. Keywords, which are not supported by all IMAP servers, allow messages to be given one or more tags whose meaning is up to the client. IMAP keywords should not be confused with proprietary labels of web-based e-mail services which are sometimes translated into IMAP folders by the corresponding proprietary servers.
Multiple mailboxes on the server[edit]
IMAP4 clients can create, rename, and/or delete mailboxes (usually presented to the user as folders) on the server, and copy messages between mailboxes. Multiple mailbox support also allows servers to provide access to shared and public folders. The IMAP4 Access Control List (ACL) Extension (RFC 4314) may be used to regulate access rights.
Server-side searches​[​edit​]
IMAP4 provides a mechanism for a client to ask the server to search for messages meeting a variety of criteria. This mechanism avoids requiring clients to download every message in the mailbox in order to perform these searches.
Built-in extension mechanism​[​edit​]
Reflecting the experience of earlier Internet protocols, IMAP4 defines an explicit mechanism by which it may be extended. Many extensions to the base protocol have been proposed and are in common use. IMAP2bis did not have an extension mechanism, and POP now has one defined by RFC 2449.
While IMAP remedies many of the shortcomings of POP, this inherently introduces additional complexity. Much of this complexity (e.g. multiple clients accessing the same mailbox at the same time) is compensated for by server-side workarounds such as Maildir or database backends.
The IMAP specification has been criticised for being insufficiently strict and allowing behaviours that effectively negate its usefulness. For instance, the specification states that each message stored on the server has a "unique id" to allow the clients to identify the messages they have already seen between sessions. However, the specification also allows these UIDs to be invalidated with no restrictions, practically defeating their purpose.​[​13​]
Unless the mail storage and searching algorithms on the server are carefully implemented, a client can potentially consume large amounts of server resources when searching massive mailboxes.
IMAP4 clients need to maintain a TCP/IP connection to the IMAP server in order to be notified of the arrival of new mail. Notification of mail arrival is done through in-band signaling, which contributes to the complexity of client-side IMAP protocol handling somewhat.​[​14​] A private proposal, push IMAP, would extend IMAP to implement push e-mail by sending the entire message instead of just a notification. However, push IMAP has not been generally accepted and current IETF work has addressed the problem in other ways (see the Lemonade Profile for more information).
Unlike some proprietary protocols which combine sending and retrieval operations, sending a message and saving a copy in a server-side folder with a base-level IMAP client requires transmitting the message content twice, once to SMTP for delivery and a second time to IMAP to store in a sent mail folder. This is remedied by a set of extensions defined by the IETF LEMONADE Working Group for mobile devices: URLAUTH (RFC 4467) and CATENATE (RFC 4469) in IMAP and BURL (RFC 4468) in SMTP-SUBMISSION. POP servers don't support server-side folders so clients have no choice but to store sent items on the client. Many IMAP clients can be configured to store sent mail in a client-side folder, or to BCC oneself and then filter the incoming mail instead of saving a copy in a folder directly. In addition to the LEMONADE "trio", Courier Mail Server offers a non-standard method of sending using IMAP by copying an outgoing message to a dedicated outbox folder.[15]
STARTTLS can be used to provide secure communications between the MUA communicating with the MSA or MTA implementing the smtp protocol.
Dialog example​[​edit​]
This is an example IMAP connection as taken from RFC3501 section 8:

C: <open connection> S: * OK IMAP4rev1 Service Ready C: a001 login mrc secret S: a001 OK LOGIN completed C: a002 select inbox S: * 18 EXISTS S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) S: * 2 RECENT S: * OK [UNSEEN 17] Message 17 is the first unseen message S: * OK [UIDVALIDITY 3857529045] UIDs valid S: a002 OK [READ-WRITE] SELECT completed C: a003 fetch 12 full S: * 12 FETCH (FLAGS (\Seen) INTERNALDATE "17-Jul-1996 02:44:25 -0700" RFC822.SIZE 4286 ENVELOPE ("Wed, 17 Jul 1996 02:23:25 -0700 (PDT)" "IMAP4rev1 WG mtg summary and minutes" (("Terry Gray" NIL "gray" "cac.washington.edu")) (("Terry Gray" NIL "gray" "cac.washington.edu")) (("Terry Gray" NIL "gray" "cac.washington.edu")) ((NIL NIL "imap" "cac.washington.edu")) ((NIL NIL "minutes" "CNRI.Reston.VA.US") ("John Klensin" NIL "KLENSIN" "MIT.EDU")) NIL NIL "<B27397-0100000@cac.washington.edu>") BODY ("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 3028 92)) S: a003 OK FETCH completed C: a004 fetch 12 body[header] S: * 12 FETCH (BODY[HEADER] {342} S: Date: Wed, 17 Jul 1996 02:23:25 -0700 (PDT) S: From: Terry Gray <gray@cac.washington.edu> S: Subject: IMAP4rev1 WG mtg summary and minutes S: To: imap@cac.washington.edu S: cc: minutes@CNRI.Reston.VA.US, John Klensin <KLENSIN@MIT.EDU> S: Message-Id: <B27397-0100000@cac.washington.edu> S: MIME-Version: 1.0 S: Content-Type: TEXT/PLAIN; CHARSET=US-ASCII S: S: ) S: a004 OK FETCH completed C a005 store 12 +flags \deleted S: * 12 FETCH (FLAGS (\Seen \Deleted)) S: a005 OK +FLAGS completed C: a006 logout S: * BYE IMAP4rev1 server terminating connection S: a006 OK LOGOUT completed
See also[edit]
  1. ^ Mullet, Diana (2000). Managing IMAP. O'Reilly. p. 25. ISBN 0-596-00012-X​.
  2. ^ See e.g. Timo Sirainen, Dave Cridland. "IMAP Client Coding HOWTO".
  3. ^ The IMAP Connection - IMAP Status and History
  4. ^ Service Name and Transport Protocol Port Number Registry. Iana.org (2013-07-12). Retrieved on 2013-07-17.
  5. ^ a b "RFC 2061 - IMAP4 COMPATIBILITY WITH IMAP2BIS"​. IETF. 1996. Retrieved 2010-08-21​.
  6. ^ "INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 3". IETF. 1991. Retrieved 2010-08-21​.
  7. ^ "IMAP2, IMAP2bis, IMAP3, IMAP4, IMAP4rev1 (LAN Mail Protocols)"​. Retrieved 2010-08-21​.
  8. ^ "IMAP Overview, History, Versions and Standards"​. Retrieved 2010-08-21​.
  9. ^ "Protocol Action: Interactive Mail Access Protocol - Version 3 to Historic (IETF mail archive)". 1993. Retrieved 2010-08-21​.
  10. ^ "Innosoft and POP/IMAP protocols? (mail archive)". 1993. Retrieved 2010-08-21​.
  11. ^ "INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 2bis (Internet Draft)". IETF. 1993. Retrieved 2010-08-21​.
  12. ^ "IMAP2BIS -- EXTENSIONS TO THE IMAP2 PROTOCOL (DRAFT)"​. 1992. Retrieved 2010-08-21​.
  13. ^ "IMAP implementation in Sup, an e-mail client written in Ruby". rubyforge.com​. Retrieved 2011-02-22​.
  14. ^ "IMAP IDLE: The best approach for 'push' e-mail". Isode.com​. Retrieved 2009-07-30​.
  15. ^ "Courier-IMAP: Sending mail via an IMAP connection"​. Double Precision, Inc. Retrieved 2013-09-24​.
Further reading​[​edit​]
External links[edit]
Look up IMAP in Wiktionary, the free dictionary.
Email clients
Free software
Related technologies
Related topics
URI scheme
Protocol list
Categories: Internet mail protocolsApplication layer protocols
Create account
Log in
This page was last modified on 25 March 2014 at 20:06.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy.
Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Contact Wikipedia
Mobile view
ReadEditView history
Visit the main pageMain pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikimedia ShopHelpAbout WikipediaCommunity portalRecent changesContact pageWhat links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationData itemCite this pageCreate a bookDownload as PDFPrintable versionالعربيةAsturianuAzərbaycancaБългар�?киCatalàČeštinaDanskDeutschΕλληνικάEspañolEsperantoEuskara�?ارسیFrançaisGalego한국어ՀայերենHrvatskiBahasa IndonesiaItalianoעבריתLatviešuLietuviųLimburgsMagyarМакедон�?киമലയാളംBahasa MelayuNederlandsनेपाली日本語Norsk bokmålNorsk nynorskPolskiPortuguêsRomân�?Р�?�?�?кийSimple EnglishSlovenčinaSlovenščinaСрп�?ки / srpskiSrpskohrvatski / �?рп�?кохрват�?киSuomiSvenskaதமிழ்ไทยTürkçeУкраїн�?ькаTiếng ViệtYorùbá中文Edit links