Browse by Tags

The issue of using MAPI or (most commonly) CDO 1.21 in managed (.NET) code is one that comes back to us a lot on the Messaging Developer Support team. Both the messaging technologies in question and the .NET framework have been around for many years at this point. As well have the KB articles that state...

...We'll be publishing a KB article to establish this support policy update on CDO 1.21. I'll update this post with KB number, in the meantime, here is the content of the article... Calling the Respond method to accept or decline a meeting request using CDO 1.21 is only supported through the MeetingItem...

The Outlook 2003 Object Model does not have anyway to delete Search Folders, although you can create them. The only way to delete them is to use CDO 1.21 code. However, it is not supported to run CDO 1.21 or MAPI code (yes, this includes Redemption any third party APIs or components you write that use...

A couple notes from the field as we enter the window of time that is DST 2007... Due to the security dialogs added to CDO 1.21 in the Outlook 2000 timeframe many people started to copy CDO 1.21 from an Exchange installation for us on client machines and application servers. As I have blogged about...

The rebasing tool adds time zone information to appointments that it touches. This time zone information is the same that Outlook 2007 (and patched versions of CDO 1.21) puts on appointments when it creates them. These time zone structures are described here… http://blogs.msdn.com/stephen_griffin...

...I'm back from a happy holiday vacation; I hope yours was happy too. Below is one of my favorite questions about CDO 1.21 because it gets asked a fair amount and the answer is simple, frustrating, and a little embarrassing for me as an MS employee. I haven't yet delivered this answer without a sheepish...

You can now download the MAPI subsystem and CDO 1.21 from Microsoft and install them separate from Exchange or Outlook. This is a totally standalone download that is comprised from the Exchange 2003 build tree and is fully supported. Here is the download link… Microsoft Exchange Server MAPI Client...

Summary Using PR_URL_COMPNAME to bind to an item in WebDAV from CDO/MAPI involves understanding the encoding rules for the Exchange version where the item is homed. These rules are different and incompatiable between Exchange 2000, Exchange 2000 SP 1, and Exchange 2003. These rules are not documented...

...Don't know if many people try to use this anymore but it is worth noting... SYMPTOM Receive MAPI_E_FAILONEPROVIDER when attempting to log on anonymously to Exchange 200x using CDO 1.21. ...OR... After anonymous log on to Exchange 200x using CDO 1.21, session object's AddressLists...

FYI IMO there a lot of TLA's out there these days. Some acronyms get pronounced phonetically like ISAPI ("eye-sap-ee") and MAPI ("map-ee") while others are enunciated simply by reading the letters like ESM ("E-S-M") and NTFS ("N-T-F-S"). Usually the presence of vowels in acronyms or resemblance to an...

The Exchange Team's Blog has a great post on how certain time zones with variable daylight time shifting affect Outlook... ... Time zones are an important thing to keep in mind when working with appointments. We get cases sometimes related to preceived bugs in CDO 1.21 or Outlook Object Model were...

It's late so I'm going to keep this brief but since we don't have any public content I wanted to get the word out. Exchange's CDO 1.21 was never tested and will not work with Kerberos authentication. While Outlook's version of CDO 1.21 does have Kerberos support, it is not suitable for use in serviced...

As more and more developers move to managed code (.NET), especially with the release of Visual Studio 2005, it is important to be reminded of what current API's are supported for use in managed code and which are not. The following KB article is a must read when starting .NET development against Exchange...