Using IMAP
An IMAP server is a form of MRA, just as a POP server is. Typically, one finds IMAP servers operating alongside or in place of POP servers.
As of this writing, the current version is IMAP Version 4, Revision 1, commonly called IMAP4revl. Note that this is not the same as IMAP4, although most people mean the current version when they say either one. The distinction becomes important when checking to see which version of IMAP your software supports. IMAP4rev1 is an Internet-proposed standard and is defined in RFC 2060.
An IMAP server is a TCP application daemon that listens for IMAP requests on TCP port 143. Any IMAP clients wishing to connect to a server try to connect to this “well-known port.” The server responds by either spawning a thread or forking a copy of itself to handle the new request. The session handler sends a banner greeting to the client and awaits further commands from the client. Each IMAP command is discussed in detail in this chapter.
IMAP daemons may be run either standalone or via the inet service under Unix. Under Windows NT, they may run as an NT service.
MUAs that provide support for the IMAP protocol implement an IMAP client. Most MUAs that support IMAP also support the POP3 protocol. An IMAP client may manipulate email messages on a remote IMAP server on the maildrop host.
Commercial IMAP servers are available from Netscape, Microsoft, and others. Open source IMAP servers ship by default with most Linux distributions and are available for most flavors ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access