DELPHI 6, 7, 2005, 2006 win32, 2007, 2009, 2010, XE, XE2-XE8, Delphi 10 Seattle/Berlin  (x32/x64) compatibles

Microsoft Exchange Server 5.5/2000/2003/2007/2010/2013 compatibles
Microsoft Outlook 97/98/2000/2002/2003/2007/2010/2013/2016 (x32/x64)  compatibles

The Extended MAPI is one of the first COM technologies provided by Microsoft. Extended MAPI is core API for Microsoft Exchange Server, Microsoft Outlook, CDO, messaging, etc.
We provide lots of examples, which demonstrates how inside DELPHI you can get the Extended MAPI power in your hands. They are grouped as "package" of simple applications and library. Our "library" includes "one file" ExtendedMAPI unit, some useful utility functions which you can find inside MAPIUtils.pas, and unique translation of EDK (Exchange Development Kit). You will have in your hands, more that 70 Interfaces, few hundreds procedures and functions, thousands constants, structures, etc  - all of them described inside MSDN or PSDK. For most of them, you can use shipped with Delphi help (excluding EDK). We strongly recommends MSDN as the primary help system for Extended MAPI and EDK.

• The source code of "Extended MAPI in DELPHI" examples are delivered via electronic Internet download after registration

Microsoft Exchange Server 5.5/2000/2003/2007 compatibles
Microsoft Outlook 97/98/2000/2002/2003/2007 compatibles

DELPHI 4, 5, 6, 7, 2005, 2006 win32 compatibles
Turbo Delphi Explorer and Turbo Delphi Professional compatibles


CDO 1.2.1 (Collaboration Data Objects, version 1.2.1) is a package providing access to Outlook-compatible objects through a COM-based API. Using either CDO or MAPI, a program can connect to a MAPI store, and then perform operations against that store.

(Extended MAPI in DELPHI - Service Providers)
AKA MAPI Inferno
 

This section of our DEVELOPMENT site is for MAPI Service Providers. That means that you have to cover the following requirements: Very good (expert) DELPHI knowledge (this does not includes knowledge for working with third party components and VCLs), good understanding of Low-Level Microsoft API (functions, structures, pointers, memory managements, etc..), very good Extended MAPI background, and not last - strong will to learn more and investigate further.

After a few years of investigating and building MAPI clients applications, we shifted part of our development team to the "MAPI inferno" - the service providers. This area of MAPI cannot be done with any kind of third-party custom MAPI components we know - they all have proved inapplicable here. Each MAPI service provider is unique, and moreover - they work in opposite sides.

There are three common types of MAPI service providers:

- Address book providers
- Message store providers
- Transport providers
 

Knowing both ADO and Extended MAPI very well one may develop one's own design of MAPI Service Provider that would unify them. We started off with the easiest to implement but also most commonly used Service Provider - Address Book.

We did our best to make our Address Book work on all Outlook versions since 1996 - starting with Windows Messaging and covering the last version. The code also can be compiled with minimal changes by Delphi 5 to Delphi 2005.

In addition we wanted the information provided by our Address Book to be used not only in Outlook but also in the form of a desktop application.