Problem solve Get help with specific problems with your technologies, process and projects.

Differences between IMAP and MAPI

We are moving to Exchange and are considering the differences between IMAP and MAPI. We also want to know the advantages...

and disadvantages of using OWA 2000, not .NET and the full Outlook client. Any help you can offer would be greatly appreciated. There are considerable differences between IMAP and MAPI. MAPI, the Messaging API, is proprietary technology from Microsoft that uses RPC-based communication to communicate with a MAPI-based mail server such as Exchange. IMAP, Internet Message Access Protocol, version 4 rev. 1 (IMAP4), is a public standard with features similar to what MAPI will give you.

With IMAP4, your mail is stored on the server, you can download the headers of a message (such as From, Subject, To) and you can decide to open only a few messages. And, like MAPI, with IMAP you can access all of your mailbox folders. The IMAP4 protocol was specified in RFC 2060 and is supported by Exchange Server 5.5 and above.

If you end up with OWA, then you'll be using HTTP (or HTTPS), and not IMAP or MAPI to access your mailbox (technically if you are using Exchange 5.5's OWA, you're still using a MAPI client, but all the MAPI stuff happens on the server, and you use a Web browser for the client). The OWA client keeps getting better and better, but it still does not replace all of the functionality that Outlook provides.

Note that .NET (e.g., the .NET Framework) is not needed for Exchange and Outlook. .NET is a development framework that has nothing to do with Outlook and Exchange.

For more information on Exchange, its protocols and available clients, see Microsoft's Exchange site.

Dig Deeper on Exchange Server setup and troubleshooting