<html>
<head>
<title>MAPIClientLibraries 0.8 API Documentation</title>
<link href="doxygen.css" rel="stylesheet" type="text/css"/>
<link href="apidocs.css" rel="stylesheet" type="text/css"/>
</head>
<body>
<div id="website">
<div class="header"></div>
<div id="middle_side">
<div id="right_side_home">
<!-- Generated by Doxygen 1.5.9 -->
<div class="navigation" id="top">
<div class="tabs">
<ul>
<li class="current"><a href="index.html"><span>Main Page</span></a></li>
<li><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="annotated.html"><span>Data Structures</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
<li><a href="examples.html"><span>Examples</span></a></li>
</ul>
</div>
</div>
<div class="contents">
<h1>Opening Exchange to a wider world</h1>
<p>
<h3 align="center">0.8 </h3><h2>OpenChange Project Goals</h2>
<p>
The OpenChange Project aims to provide a portable Open Source implementation of Microsoft Exchange Server and Exchange protocols. Exchange is a groupware server designed to work with Microsoft Outlook, and providing features such as a messaging server, shared calendars, contact databases, public folders, notes and tasks.<p>
The OpenChange project has three goals:<p>
<ul>
<li>To provide a library for interoperability with Exchange protocols, and to assist implementors to use this to create groupware that interoperates with both Exchange and other OpenChange-based software.</li></ul>
<p>
<ul>
<li>To provide an alternative to Microsoft Exchange Server which uses native Exchange protocols and provides exactly equivalent functionality when viewed from Microsoft Outlook clients.</li></ul>
<p>
<ul>
<li>To develop a body of knowledge about the most popular groupware protocols in use commercially today in order to promote development of a documented and unencumbered standard, with all the benefits that standards bring.</li></ul>
<p>
<h2>MAPI Overview</h2>
<p>
MAPI is the glue between Exchange and Outlook, but a common misconception is to consider it as a network protocol. MAPI, an acronym for Messaging Application Programming Interface, refers to a proprietary set of function call interfaces developed by Microsoft before Microsoft Exchange existed. By purchasing licenses to Microsoft's proprietary and Windows-only MAPI libraries, anyone can create message services that communicate using these functions. A mail server implemented in this way is what Microsoft calls a MAPI Service Provider. Any protocol could be used as a transport for these MAPI communications.<p>
When Microsoft Exchange 5.5 was developed in 1997, the decision was taken to create a proprietary transport protocol for MAPI which closely matches the MAPI calling interface. This protocol is called ExchangeRPC and used in Outlook-Exchange communications. ExchangeRPC is the only transport OpenChange supports, and in practice is the only transport of interest today. Most of the world is being forced to use Microsoft Exchange servers, so that defines the transport that matters.<p>
When OpenChange team members first looked at the network network traffic these generated by calling MAPI functions on Windows operating systems, we noticed blobs of data first either compressed or obfuscated, then encapsulated by an RPC transport protocol function (EMSMDB) and finally pushed on the wire. Transporting memory-image blobs on the wire is not good protocol design, however for a number of reasons the result now works quite reliably.<p>
<h2>Looking at a MAPI Conversation</h2>
<p>
A high-level view of a MAPI conversation follows. We also introduce important terminology:<ul>
<li>MAPI applications call MAPI providers, using the API to pass data (eg a mail message body) or MAPI conversation requests and responses (eg 'search for this address').</li><li>MAPI providers pack the client or server MAPI information in a blob. There are only two really important providers, one for data destined for what is somewhat strangely termed the Message Store (although it handles more than just messages), and the other for data to be sent to the Address Book. These are called the EMSMDB and EMSABP providers, respectively.</li><li>ExchangeRPC protocol is used to transport the MAPI information over the wire, encapsulating inside it one of two MAPI-specific protocols: the EMSMDB Message Store Protocol, or the NSPI Addressbook Protocol.</li><li>The store provider on the server side associated with the protocol used (either EMSMDB or EMSABP) extracts the MAPI blob from RPC protocol functions, analyzes its content and performs operations embedded within it. </li></ul>
</div>
</div>
<br/>
<table style="clear:both; margin: 0.5em auto; width:80%; text-align: center; background-color:#f8f8f8; border:2px solid #e0e0e0; padding:5px;">
<tr>
<td>
<img alt="Creative Commons License" src="CC_SomeRightsReserved.png" width="90" height="30" border="0" /><br />
<img alt="Creative Commons Attribution icon" src="24px-Cc-by_white.svg.png" width="24" height="24" border="0" />
<img alt="Creative Commons Share Alike icon" src="24px-Cc-sa_white.svg.png" width="24" height="24" border="0" />
</td>
<td> <i><strong class="selflink">This content</strong> is licensed under the Creative Commons<br />
Attribution ShareAlike License v. 3.0:<br />
<a href="http://creativecommons.org/licenses/by-sa/3.0/" class="external free" title="http://creativecommons.org/licenses/by-sa/3.0/" rel="nofollow">http://creativecommons.org/licenses/by-sa/3.0/</a></i>
</td></tr></table>
<br/>
</div>
</div>
</body>
</html>
