Jump to content

MAPI

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 23.31.43.189 (talk) at 16:33, 8 April 2021 (→Details). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Not to be confused with Manufacturers Alliance for Productivity and Innovation.
"MAPI" redirects here. Not to be confused with IMAP, an email protocol.

Messaging Application Programming Interface (MAPI) is an API for Microsoft Windows which allows programs to become email-aware. While MAPI is designed to be independent of the protocol, it is usually used to communicate with Microsoft Exchange Server.[1]

I am so crazy, email danielacy2009@gmail.com thank you


Any questions/comments/concerns/issues? Email danielaac2009@outlook.com! You'll be all set in no time.

Service provider interface

The full Extended MAPI interface is required for interfacing messaging-based services to client applications such as Outlook. For example, several non-Microsoft e-mail server product vendors created "MAPI service providers" to allow their products to be accessed via Outlook. Notable examples include Axigen Mail Server, Kerio Connect, Scalix, Zimbra, HP OpenMail, IBM Lotus Notes, Zarafa/Kopano, and Bynari.

MAPI also had a service provider interface of sorts. Microsoft used this to interface MS Mail to an email system based on Xenix, for internal use.

Extended MAPI is the main e-mail data access method used by Outlook, to interface to Microsoft Exchange, via MAPI service providers shipped with Outlook.

MAPI/RPC protocol details

Microsoft has released full details of the MAPI/RPC protocol since August 2007.[2]

"MAPI protocol" is a colloquial name for the MAPI/RPC. At times, Microsoft has also called it "Exchange RPC" and "Outlook-Exchange Transport Protocol".

Microsoft provides a sample MAPI/RPC-based application called MFCMAPI[3] to assist developers. It is also widely used as a diagnostics tool by both developers and Microsoft Exchange administrators.

MAPI over HTTP

The original implementation was designed for use on a local network, or LAN. The "Outlook Anywhere" feature extended this to an external Internet-facing interface but MAPI/HTTP, introduced in 2014 with Exchange 2013 SP1 replaced this with a more 'normal' HTTP-based stack.[4]

Reimplementations

Several open-source software projects have started working on implementing MAPI libraries, including:

  • The OpenMapi project (now demised)[5] had a C# implementation.
  • Kopano (software) Groupware Core has a C++2011 implementation called "mapi4linux" (continuation of the same from Zarafa), which offers an API that is source-backwards-compatible with the Messaging API (code written for M4L also build with the Windows SDK). Kopano GWC comes with a connector for the Zarafa/Kopano-based SOAP/HTTP transport.
  • OpenChange has a "libmapi" component written in C that only partially resembles MAPI. (Lacks interfaces like IMsgStore, the OpenEntry function.)
  • The OpenChange subproject Evolution-MAPI is a connector for Exchange implementing the MAPI/RPC transport.
  • The Gnome Evolution project develops evolution-ews, which has implemented much of MAPI.[6]

References

  1. ^ "MAPI over HTTP in Exchange 2016". Microsoft TechNet. 2016-12-20.
  2. ^ Exchange Server Protocols. Msdn.microsoft.com. Retrieved on 2013-07-17.
  3. ^ Mfcmapi - Home. https://github.com/stephenegriffin/mfcmapi. Retrieved on 2017-07-26.
  4. ^ "Outlook Connectivity with MAPI over HTTP". You Had Me At EHLO…. Microsoft. Retrieved 17 December 2018.
  5. ^ openmapi.org used to host the downloads; it no longer exists
  6. ^ "EWS Operations Features' Parity Matrix". Retrieved 17 December 2018.
Retrieved from "https://en.wikipedia.org/w/index.php?title=MAPI&oldid=1016701024"