PRXF_IGNORE_SEC_WARNING doesn’t work in MAPI CDO

The flag PRXF_IGNORE_SEC_WARNING doesn’t work in MAPI \ CDO as it should.  The flag was introduced to support RPC over HTTP in the updated MAPI \ CDO that was released around the time of Exchange Server 2013’s release.  The flag is supposed to instruct the MAPI subsystem to use this flag RPC_C_HTTP_FLAG_IGNORE_CERT_CN_INVALID when configuring the…

2

Handbook for the Recently Present

One of the common calls I take in my job are from developers trying to write Instant Messaging and Presence (IM & P) providers to integrate with Office and Sharepoint.  The number of cases I see are increasing so I wanted to start a series dedicated to that topic.  The purposes of this series is…

0

How to use CDO 1.2.1 to connect to Exchange 2013 using a dynamic profile

NOTE: This article only applies to Exchange’s MAPI \ CDO download.  It doesn’t apply to using CDO 1.2.1 with an Outlook 2007 client. I was discussing an issue recently with a customer and I asked him to connect to the Exchange server using CDO 1.2.1.  Then I realized that I had never tried that myself. …

0

Async MAPI Notifications in Exchange are a problem for MAPI clients that impersonate

I had a case six months ago where the customer was using Exchange’s MAPI against Exchange 2013 and was seeing a number of MAPI_E_NETWORK_ERRORs in his application. After discussing the issue with him it was determined that the application was running in the security context of Local System but would impersonate a user who has…

0

Exchange’s MAPI repeatedly prompts for credentials

I had a case recently where the customer’s symptoms where that his application was causing a security credential dialog over and over again even though correct credentials were supplied. Upon further investigation we found that the LmCompatibilityLevel registry value was set to 1.  Since the application was using Windows RPC over HTTP (ROH) and the…

3

EXHTTP settings don’t appear in Exchange 2013’s Autodiscover response

MAPI clients wishing to get the correct Autodiscover settings for Exchange 2013 need to get the EXHTTP nodes in the Autodiscover response to configure the client correctly.  However, the Plain Old XML (POX) Autodiscover will not return this information if the client is not above a certain version of Outlook.  Furthermore, the authentication packages may appear…

2

Using Basic Authentication for RPC over HTTP with MAPICDO

I had a case recently where the customer was trying to use Basic Authentication for RPC over HTTP with MAPI\CDO.  The customer’s symptom was that no matter what was entered into the credentials dialog it would not accept the credentials.  When I reviewed the IIS logs there wasn’t even a request being made to the…

1

How to create an Outlook profile for Office 365

I had another case involving creating a profile to an Office 365 mailbox.  However, this time it was for Outlook’s MAPI, not Exchange’s MAPI as previously documented.  After discussing this with the Outlook product team they agreed to document the minimum number of properties to create a profile using MFCMAPI.  Here are the steps.  For…

5

How to configure an Outlook profile using MFCMAPI for Exchange 2013

I had another case involving creating a profile to an Exchange 2013 server.  However, this time it was for Outlook’s MAPI, not Exchange’s MAPI as previously documented.  After discussing this with the Outlook product team they agreed to document the minimum number of properties to create a profile using MFCMAPI.  Here are the steps.  For…

0

A new MAPI interface is available to let you force connections to go to a specific Exchange Server

[Edit: 1/23/2014 – This new interface did not ship in the December 2013 CU.  I was incorrect.  I am currently looking into it.] [Edit: 4/23/2014 – This fix should’ve released in February] [Edit: 11/21/2014 – This change was ported to Outlook 2013 in the April 2014 Cumlative Update for Outlook 2013.  http://support.microsoft.com/kb/2878323] [Edit: 11/17/2016 – This…

8