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

Not many people are aware of the feature, but MFCMAPI implements a MAPI Form Viewer . This means MFCMAPI can use MAPI to ask Outlook to display messages. You might have run into this if you ever double-click on a message in MFCMAPI. If you’re on a machine with Outlook installed, the message will open up like it does when you double-click it in Outlook. And if Outlook isn’t installed and you’re using Exchange’s MAPI, you get a scary dialog saying we couldn’t open the MAPI form manager . This is one

Matt’s very excited about the release of EWSEditor . This tool does for EWS what MFCMAPI does for MAPI. With this tool, Matt does what I did with MFCMAPI and what I recommend to anyone trying to learn a new API: the best way to learn an API is to write tools that use it. As you work with EWSEditor, you may notice a few things which are similar to MFCMAPI. This is no coincidence. EWS and MAPI, both designed primarily to interact with an Exchange server, share much of the same object hierarchy, which

As Paul Thurrott notes, we just announced that we’re documenting the PST file structure . I haven’t decided yet if I’ll be writing a standalone parser/viewer/validator, but I’m sure I’ll be adding some interesting stuff to MFCMAPI . I’ll let you know when I know more. digg_url = "http://blogs.msdn.com/stephen_griffin/archive/2009/10/26/inside-the-pst.aspx";digg_title = "Inside the PST";digg_bgcolor = "#FFFFFF";digg_skin = "compact"; digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin

Dave has a post up about the fate of the System Attendant Mailbox in Exchange 2010 . Since this mailbox isn’t there anymore in 2010, if you have a solution that depended on it, you’ll need to rework it. Dave gives a few suggestions, such as creating your own mailbox/account (the best option since you can then control your exact permission set) or using the System Mailbox . Enjoy! digg_url = "http://blogs.msdn.com/stephen_griffin/archive/2009/10/09/so-long-system-attendant-mailbox.aspx";digg_title