A while back, Jason posted an Account Management API sample. I’ve threatened promised before that I would post an update to this sample, and I finally got around to it. You can download the updated sample here . In addition to adding a –W command to call DisplayAccountList and show the Account Settings Wizard, I’ve also added a couple new properties that dev have decided to document: #define PROP_ACCT_USER_EMAIL_ADDR PROP_TAG(PT_UNICODE, 0x000C) #define PROP_MAPI_IDENTITY_ENTRYID PROP_TAG(PT_BINARY,

A little follow-up to the Outlook Rules post , concerning getting rules to fire when you’ve got a wrapped PST store. I had noted in the original post that rules “just worked” in Outlook 2003. Turns out I was partially right. They can work in Outlook 2003, but you have to do something a little special that I had somehow overlooked in my original investigation. Here’s how I explained your should fire a notification for Outlook 2003: In Outlook 2003, the way you solve this is to use the IMAPISupport

On my article about enabling rules in the Wrapped PST , Richard pointed out that when you do this, read receipts stop working . We've investigated this and found that there's something a little extra you have to do to get read receipts to fire. Remember that we're using ITEMPROC_FORCE to push the messages through the Item Proc pipeline. As I described earlier, that pipeline handles rules, junk mail, and spam processing. It also handles firing read receipts. Let's take a look at how read receipts

We had a customer here who wondered why messages imported into MAPI using MIMEToMAPI always appeared as draft messages. This is because the default value of PR_MESSAGE_FLAGS includes the MSGFLAG_UNSENT flag. Now - if you know you want your messages to not appear as drafts, the thing to do here is to clear the MSGFLAG_UNSENT flag before saving the message. But what if you're exporting messages from mailbox using MAPIToMIMEStm and importing them using MIMEToMAPI, and want to preserve the sent/unsent

We just released an update to our calendar rebasing library, Tzmovelib.dll . This update includes a refresh to the documentation . One thing that didn't make it into this refresh was an updated sample and documentation for a new exported function, primarily because I didn't have it ready in time. So I'm documenting the new function here, and it will make it into the MSDN the next time we refresh the docs. We've added a new export to tzmovelib.dll in this refresh. It's name is HrCreateApptRebaserEx.

One of our customers reported that if they used IConverterSession::MIMEToMAPI to generate an MSG file, then opened the MSG file and hit Forward, the body would be gone. Further investigation revealed more funkiness. Reply worked, but if you tried Forward, closed the forwarded message, then tried Reply again, the body would be missing there as well. I could also repro the problem with some messages I saved to MSG from MFCMAPI. If you've read my other article on MSG files you know this behavior doesn't

We've decided to document another function in the Account Management API , DisplayAccountList. This function allows you to display the Account Settings dialog: and Add New E-Mail Account property sheet: DisplayAccountList hangs off of IOlkAccountManager interface, occupying the second slot in the v-table, like so: interface IOlkAccountManager : IOlkErrorUnknown { public: //Init Initializes the account manager for use. virtual STDMETHODIMP Init(IOlkAccountHelper* pAcctHelper, DWORD dwFlags); //DisplayAccountList

In a comment on my post about the MAPI download working with Vista, JP pointed out that something in the updated DLLs is changing the current working directory. I got a chance to look at this today and here is what I found: this is the MAPI Stub 's doing. In order to support some wonky old MAPI implementations, the stub library will change the current working directory to the directory of the MAPI implementation it's loading. As far as I can tell, the stub has always done this. It's only being noticed

The April 2008 Release (build 6.0.0.1005) is live: http://www.codeplex.com/MFCMAPI Here's the change list - see the Issue Tracker on Codeplex for more details, or look at the code: A few compatibility issues with older compilers (VC 6 and VC 2005) - thanks to Pete for pointing these out. Added support for the new restriction types Some general cleanup Enjoy.

Those of you wrapping PSTs may see something interesting in the restrictions Outlook 2007 will try to set against your folders. There are a couple of new restriction types you won't have seen before. Outlook will only use these restriction types when it's working with stores it knows supports them (like a PST), so in general you can ignore them and just pass the restriction on to the underlying store. However, if you're trying to make a copy of the restriction structure for some later use, then you