Internet Message Access Protocol
Encyclopedia : I : IN : INT : Internet Message Access Protocol
| Layer | Protocols |
|---|---|
| Application | DNS, TLS/SSL, TFTP, FTP, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP, SNMP, SSH, TELNET, BitTorrent, RTP, rlogin, … |
| Transport | TCP, UDP, DCCP, SCTP, IL, RUDP, |
| Network | IP (IPv4, IPv6), ICMP, IGMP, ARP, RARP, … |
| Link | Ethernet, Wi-Fi, Token ring, Point-to-Point Protocol>PPP, SLIP, FDDI, ATM, DTM, Frame Relay, SMDS, … |
The Internet Message Access Protocol (commonly known as IMAP or IMAP4, and previously called Internet Mail Access Protocol) is an application layer Internet protocol that allows a local client to access e-mail on a remote server. The current version, IMAP version 4 revision 1 (IMAP4rev1), is defined by RFC 3501. IMAP4 and POP3 (Post Office Protocol version 3) are the two most prevalent Internet standard protocols for e-mail retrieval. Virtually all modern e-mail clients and servers support both.
E-mail protocols
E-mail messages are generally sent to an e-mail server that stores received messages in the recipient's e-mail mailbox. The user later retrieves these messages with either a web browser or an e-mail client that uses one of a number of e-mail retrieval protocols. While some clients and servers preferentially use vendor specific, typically proprietary protocols, most support the Internet standard protocols SMTP for sending e-mail and POP3 and IMAP4 for retrieving e-mail, allowing interoperability with other servers and clients. For example, Microsoft's Outlook client typically uses a proprietary protocol to communicate with an Exchange server as does IBM's Notes client when communicating with a Domino server, but all of these products also support SMTP, POP3, and IMAP4. Support for the Internet standard protocols allows many other e-mail clients such as Qualcomm's Eudora or Mozilla Thunderbird (see list of e-mail clients) to access these servers and similarly allows the clients to be used with other servers (see list of mail servers).E-mail clients can generally be configured to use either POP3 or IMAP4 to retrieve e-mail and in both cases use SMTP for sending. Most e-mail programs can also use Lightweight Directory Access Protocol (LDAP) for directory services.
Nearly all subscribers to individual Internet service provider e-mail accounts access their e-mail with client software that uses POP3.
IMAP is often used in large networks; for example, a college campus mail system. IMAP allows users to access new messages instantly on their computers, since the mail is stored on the network. With POP3, users either download the e-mail to their computer or access it via the web. Both methods take longer than IMAP, and the user must either download any new mail or "refresh" the page to see the new messages.
History
IMAP was designed by Mark Crispin in 1986 [link] as a modern alternative to the widely used POP e-mail retrieval protocol.IMAP 4
The current version of IMAP, IMAP version 4 revision 1 (IMAP4rev1), is defined by RFC 3501.Unlike many older Internet protocols, IMAP4 natively supports encrypted login mechanisms. Plain text transmission of passwords in IMAP4 is also possible. Because the encryption mechanism to be used must be agreed between the server and client, plain text passwords are used in some combinations of clients and servers (typically Microsoft Windows clients and non-Windows servers). It is also possible to encrypt IMAP4 traffic using SSL, either by tunneling IMAP4 communications over SSL on port 993, or by issuing "STARTTLS" within an established IMAP4 session (see RFC 2595).
IMAP4 works over a TCP/IP connection using network port 143.
Advantages over POP3
- Both connected and disconnected modes of operation
- When using POP3, clients typically connect to the e-mail server very briefly, only as long as it takes to download any 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 much faster response times.
Disadvantages of IMAP
- IMAP is a very heavy and complicated protocol. Implementing IMAP is more difficult and error-prone than implementing POP3 for both client and server implementations. This can result in security issues which are less likely under POP3.
- IMAP generally results in higher server loads than POP3, resulting in higher costs for ISPs and end users.
- Server side searches can potentially use lots of server resources when searching massive mailboxes.
Common implementations
The following IMAP-servers are common:
- Binc IMAP - uses Maildir format, designed to be familiar for users of qmail and qmail-pop3d
- Citadel
- Courier IMAP - uses Maildir format.
- Cyrus IMAP server - a "black box" server that provides access through POP3 and IMAP
- DBMail - uses an SQL backend.
- Dovecot - Secure IMAP server
- FirstClass Server - FirstClass Server [link]
- IBM Lotus Domino Server
- Kerio MailServer
- Mac OS X Server (uses Cyrus)
- Merak Mail Server
- Mercury/32 [link]
- Microsoft Exchange Server
- Mirapoint [link]
- Stalker Communigate Pro [link]
- UW IMAP - supports multiple formats including mbox, mbx, MMDF, tenex, mtx, MH, mx, and Usenet news spools.
- Zimbra
- text-based clients:
- *UW PINE - one of the first IMAP clients
- *Mutt - e-mail client found in many Linux distributions
- GUI clients:
- *Apple Mail
- *The Bat!
- *Novell Evolution
- *KMail
- *Eudora (e-mail client)
- *Microsoft Outlook Express
- *Microsoft Outlook
- *Mozilla Thunderbird
- *Pegasus Mail
- *SeaMonkey Mail
- AOL Instant Messenger [link]
- FastMail
- Fusemail [link]
See also
External links
- RFC 3501 ([HTML version]) - specification of IMAP version 4 revision 1
- [The IMAP connection] - resources for developers of programs using the IMAP protocol
- [IMAP connection's listing of products and service providers supporting IMAP]
From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.
