Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

Retrieving Profile and Service Store using Extended MAPI

0.00/5 (No votes)
6 Jul 2004 1  
This application is written to retrieve profile name and associated message stores.

Introduction

This code is written to retrieve existing profiles and and associated service/s. This app uses Extended MAPI for retrieval of this information.

I take no responsibility for support or any kind of issues that may arise with this code.

Overall, there are very less articles available for Extended MAPI, that's the reason I am putting this code. I have tested this code on Win2000 and Outlook XP. UI is not good for this project. After retrieval of the profiles and services, this app will show some message boxes and nothing else. These message boxes will be of Profile Name and Message Store Services. Still I am working on this code and will try to make it more attractive.

I welcome all Extended MAPI developers to pass comments on this code:

Here are some details:

To deal with the Extended MAPI, we need to know a few basic things. In the following paragraphs, I will try to explain these basics.

The MAPI structure is a complex structure that requires understanding of C / C++ even for basic implementation. The MAPI subsystem exposes various interfaces using which we can interact with it. The IProfAdmin is one of the interfaces exposed by MAPI. This description is focused on IProfAdmin.

To start with, we need "MAPIInitialize" function that initializes the global data of MAPI DLL and increments the reference to the MAPI Subsystem. Once the MAPI sub system is initialized, we need to take control of the profiles to work with them. To create the administration profile, we need to declare a variable of �LPPROFADMIN� type and create the administration profile using �MAPIAdminProfiles� function.

Once we have the Admin profile, we can work with the profiles with administrative privileges.

As a basic, the MAPI exposes various tables using which we can retrieve the MAPI data. For profiles, the MAPI exposes the Profile Table. Almost all tables can be declared as �LPMAPITABLE�.

The data is stored in the tables in the form of rows and columns. Again, to reach to the data, we need to get the row set, individual row, and then the actual properties.

The LPMAPITABLE has a function �GetRowCount� using which we can retrieve the count of the data rows. Similarly, using �QueryRows� function, row set can be retrieved. Here, the row set variable should be declared as �LPSRowSet�. The LPSRowSet is an array of the individual rows.

Using normal for / while / do while (whichever is applicable) loop, we can iterate through all rows. The individual row should be declared as �LPSRow�. Each row is an array of properties, and each property is of �LPSPropValue� type. The LPSPropValue has two members namely Property Tag and Property value. The property tag is of unsigned long type and value is a union.

Please refer MAPI documentation for the property tags. These are already defined in MAPITags.h file and these tags are self descriptive. E.g., PR_DISPLAY_NAME.

Once we have the property, then we can compare the required tag with the retrieved tag and get the property value from the property structure.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here