Skip to main content

Email protocols: POP, IMAP and MAPI

 Email protocols: POP, IMAP and MAPI

What are these?

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one). The most important reason for knowing of their existence? To understand that the correct protocol must be selected, and correctly configured, if you want your email account to work.

The Post Office Protocol (currently in version 3, hence POP3) allows email client software to retrieve email from a remote server. The Internet Message Access Protocol (now in version 4 or IMAP4) allows a local email client to access email messages that reside on a remote server. There's a related protocol called SMTP, which we also discuss below.
The Messaging Application Programming Interface (MAPI) is a proprietary email protocol of Microsoft, that can be used by Outlook (Microsoft's email client software) to communicate with Microsoft Exchange (its email server software). It provides somewhat more functionality than an IMAP protocol; unfortunately, as a proprietary protocol, it works only for Outlook-Exchange interactions.


POP is the older design, and hails from an era when intermittent connection via modem (dial-up) was the norm. POP allows users to retrieve email when connected, and then act on the retrieved messages without needing to stay "on-line." This is an important benefit when connection charges are expensive.
The basic POP procedure is to retrieve all inbound messages for storage on the client, delete them on server, and then disconnect. (The email server functions like a mailbox at the Post Office -- a temporary holding area until mail gets to its final destination, your computer.)
Outbound mail is generated on the client, and held for transmission to the email server until the next time the user's connection is active. After it's uploaded, the server forwards the outgoing mail to other email servers, until it reaches its final destination.
Most POP clients also provide an option to leave copies of email on the server. In this case, messages are only removed from the server when greater than a certain "age" or when they have been explicitly deleted on the client. It's the copies on the client that are considered the "real" ones, however, with those left on the server merely temporary backups.


IMAP is the newer protocol and oriented toward a "connected" mode of operation. The standard IMAP procedure is to leave messages on the server instead of retrieving copies, so email is only accessible when "on-line."
IMAP is more suited to a world of always-on connections, particularly the fast connections offered by broadband mechanisms. Having to be connected to read your email is a trivial obstacle when the connection is always available. (It's a little like leaving your messages at the Post Office, and going there every time you want to read them. That might be difficult in the physical world, but it's easy in the virtual one.)
Because messages remain on the server, until explicitly deleted by the user, they can be accessed by multiple client computers -- an important advantage when you use more than one computer to check your email.
IMAP does not preclude keeping copies on the client, but, in an inversion of the way POP works, it's the server's copies that are considered the "real" ones. That offers an important security benefit -- you won't lose your email if, for some reason, your client computer's storage media fails.
IMAP has other advantages over POP (detailed in the links provided below). It is the standard we recommend if you can't use MAPI.


At the risk of overloading you with information, you should know that strictly speaking it's only the incoming mail that is handled by a POP or IMAP protocol. Outgoing mail for both POP and IMAP clients uses the Simple Mail Transfer Protocol (SMTP).
When you set up a POP or IMAP email account on email client software, you must specify the name of the (POP or IMAP) mail server computer for incoming mail. You must also specify the name of the (SMTP) server computer for outgoing mail. These names are typically in the same form as Web addresses (e.g., ""). Depending on the client, there may also be specifications for email directories and searching.

As noted, MAPI is Microsoft's proprietary email protocol. It provides greater functionality than IMAP for Outlook email clients interacting with an Exchange email server. It doesn't work for anything else. (In Outlook you may simply see the connection option "Microsoft Exchange Server" rather than MAPI. It's offering the same thing.)
Remote access using MAPI may require use of a VPN connection, because the ports (communications channels) that MAPI uses are otherwise blocked for security reasons. (That's the case when accessing the medical campus Exchange system remotely.)
Web browser email access

Many email systems can now be accessed using only a Web browser. There is no need to install client email software of any kind. Logically, Web browser interfaces to email are like IMAP, in that all the messages remain on the server unless explicitly deleted. (Message copies can be saved on the client computer.)
For example, the medical campus Exchange email system can be accessed by Outlook Web Access (OWA); it provides most of the functionality of an installed version of Outlook. OWA is compatible with most browsers, such as Firefox, Netscape, Opera or Safari, though it works best with Microsoft's Internet Explorer browser.
More information

POP (Wikipedia)
Information about POP, including links to the formal standards
IMAP (Wikipedia)
Information about IMAP, including links to the formal standards
Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP (IMAP Connection)
All about why IMAP is better than POP
SMTP (Wikipedia)
All about SMTP
MAPI (Wikipedia)
Information about MAPI, including links to Microsoft reference materials


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664