The guard has gone beserk (or how do I keep multiple MAPI clients running together?)

Question

I have a standalone program that I am trying to hook into MAPI to send emails automatically using the default system (Outlook for the most part) available. For the most part, it works quite well, and everything sends fine. However, after a while, Outlook will start to flip out about my program's accessing the MAPI system, and will start to refuse to show anything until all MAPI users (my program and Outlook) are closed and re-opened. My best guess at this stage is that I'm not using a proper set of flags when logging in to the MAPI system, though I can't see why. My current set is MAPI_ALLOW_OTHERS, MAPI_EXTENDED, and MAPI_USE_DEFAULT. Can anyone suggest a different combination that lets Outlook continue to ignore me, and keep the guard placated? Thanks.

Answer 1

I experienced something similar a while back and was able to work around it by centralizing all of my extended MAPI calls from a single point of entry, and added a queue to insure that only one MAPI event from my application was occurring at any point in time.