Over the weekend, we shipped a new version of the MAPICDO download. First things first: Right now, the download page refers to something called CDO 1.2.3. This is an error. It should say CDO 1.2.1, as it always has. I’m working to get this corrected. Fixed! Now, on to the release notes:
Is the notification flag fix (or anything within this release for that matter) related to the Blackberry delay issues? To date there still seems to be no formal approach to this problem.
PB: I'm not really involved in that issue, but if it was a performance issue that involved OpenEntry calls after notifications, then the new notification flag would allow them a way to improve performance. Read more on the flag here: blogs.msdn.com/.../mapicdo-and-long-term-entry-ids.aspx
MAPI on the x64 side of 2008 R2 (and probably with the 32 bit version, although MAPI/CDO does not do this) wants to prompt you if no default mail client is registered/defined. In some cases you may not want a client and are just interfacing to the MAPI32.dll for the sake of it (like looking at return codes, instead of checking version information and taking different paths)... and this is okay. However prompting with a message box blocks processes running as service, COM app, etc, if that process tries to load a DLL/EXE/etc that may try to interface to MAPI32.dll in this way.
Can this prompting behaviour be circumvented or better yet completely removed...
Is there a download for TS machines running outlook?
Outlook implements MAPI, so there is no reason you would want to install MAPICDO on a machine running Outlook. It's also not supported.