This came up in a case and the cause wasn’t immediately obvious. The customer used MAPI to open a number of mailboxes using OpenMsgStore. They found that if they tried to multithread their code, they’d open a few mailboxes, then they’d start getting MAPI_E_FAILONEPROVIDER. The odd thing was the same code running against Exchange 2007 did not experience this problem. It turns out what they were running in to was Exchange 2010’s new client throttling feature. The purpose of this feature is to prevent

Earlier i had a requirement, how to obtain Proxy addresses for a specific user programmatically'; also they preferred to do this by using Outlook Object Model API. Please Note: The ExchangeUser object does not directly expose the proxy addresses for the user. However, you can use the PropertyAccessor object to obtain the MAPI property PR_EMS_AB_PROXY_ADDRESSES . This property is a multi-valued string property that contains all the foreign addresses for a given user. Here is a simple code snippet,

In the Publish Form As dialog box, when you type a name in the Display name field, you will notice that the Form name field reflects the display name by default. You can leave the form name to be the same as the display name or you can change the form name. The display name will be the caption at the top of your form. The display name will also be used to construct the name under which your form will be published. When you publish your form, the display name will be listed in the Choose Form dialog

Recently one of my customer updated that they have a requirement to implement the following logic: 1) Get Contact info from GAL or Address book for the specified contact 2) Get Contact information regarding his CompanyName etc. In the scenario, i provided the following suggestions: If you try Outlook 2003 & its prior versions: Using the Microsoft Outlook object model, you can access information that is stored in various address books. For example, you can retrieve information about entries in

We recently had a customer who was copying messages around using CopyTo . They found that for certain messages, if the target message store was a PST, they’d get MAPI_E_NO_ACCESS (0x80070005). They saw this for the same messages every time, when other messages would copy to the same PST just fine. When I debugged the failure, I found the root of the problem was that the source message had an attachment with the property 0x67100003 set on it. The PST provider does not allow this property to be set

It used to be that if you wanted to track a message through various Object Model events such as NewInspector and ItemSend , one way to do it was to grab PR_SEARCH_KEY . A customer recently discovered that this doesn’t always work after applying a recent hotfix. Before applying the hotfix, PR_SEARCH_KEY would remain unchanged during the various events. After applying the hotfix, if they were in cached mode they would see the search key change during the send event, but only if the user saved the message,

We just announced a new release of the MAPI Download that’s pretty much mandatory if you want to work with Exchange 2010. You’ll also need to get and apply Rollup 1 (RU1) for Exchange 2010 . Details about the MAPI Download: The first version of the MAPI download which is compatible with Exchange 2010 is 6.5.8147 If you already have a version of the MAPI Download installed, you must unininstall it before installing the new version. The installer does not upgrade, nor does it warn you if you try to

Angela’s put together a good set of guidelines for developing for Outlook 2010 , particularly as it relates to whether your code is built for 32 bit or 64 bit (what we’re calling Bitness). To summarize, all MAPI or Outlook Object Model based apps and non-managed add-ins will need to be built in both 32 and 64 bit flavors to support both target environments, managed add-ins can be built as Any CPU , and VB 6 based add-ins and apps need to be scrapped and rewritten entirely. Read the full article to

The November 2009 Release (build 6.0.0.1016) is live: http://mfcmapi.codeplex.com . The September 2009 release was downloaded over 18 thousand times, with nearly 1700 of them being the 64 bit build. This exceeded the July build by about 4000 downloads. Yay MFCMAPI! Mostly bug fixes this time around. Win 7 finally made me dig into why Close All Windows wasn’t working, and I did a bit of work to make MFCMAPI a better multimon client. Here's a change list - see the Issue Tracker on Codeplex for more

From time to time, I get asked to explain where CDO publishes Free Busy information in the Public Folder store, so I figured I’d put this article together. The basic process CDO uses for updating FB information is outlined in the More Information section of KB 278954 . We’re concerned with the part of the process summarized as “queued up to be sent to the site’s Free/Busy public folder.” The first thing CDO does is to open the Public Folder store and read a couple properties off of it, PR_FREE_BUSY_FOR_LOCAL_SITE_ENTRYID