MAPI and Exchange 2007

re: MAPI and Exchange 2007

hauld — Thu, 29 Mar 2012 23:46:00 GMT

i'm getting *MAPI_E_UNCONFIGURED == 0x8004011C* when attempting to connect to an exchange 2010. this worked in the past. also found another server this fails on.

re: MAPI and Exchange 2007

Stephen Griffin - MSFT — Mon, 04 Oct 2010 21:15:05 GMT

It is untrue. You have to put MAPI on machines where MAPI clients run. Exchange is always a MAPI server and does not need the MAPI client bits to operate as a MAPI server. Now - if you plan on running a MAPI client on the Exchange server, you'd need to install MAPI for that client's sake, but not for the server's sake.

re: MAPI and Exchange 2007

Brendon — Mon, 04 Oct 2010 20:19:58 GMT

Hi Steve, Your post says to me that you "can" put MAPI on the Exchange 2007 server. Is it also true that you "have" to put MAPI on the Exchange 2007 server so that clients such as the Blckkberry BES server can successfully access the Exchange?

re: MAPI and Exchange 2007

venkat — Wed, 18 Nov 2009 05:59:14 GMT

How does one set the PKI certificate info, in case the email is S/MIME encoded? Is PR_CONNECT_FLAG control this?

re: MAPI and Exchange 2007

tdl — Mon, 12 Oct 2009 08:35:46 GMT

I couldn't find directly related topic, so i'm asking under this topic (cause it may be an Exchange 2007 issue);

I set a latest delivery time for a message to get a non delivery report after a given time via PR_LATEST_DELIVERY_TIME (10 minutes i.e.). However, NDR arrives after the time which the "maximum expiry time" settings of MS Exchange 2007 indicates (1 day by default) even though i set PR_LATEST_DELIVERY_TIME. Isn't it possible to set the latest delivery time using MAPI on Exchange 2007? I used to use this property on Exchange 2003.

re: MAPI and Exchange 2007

Stephen Griffin - MSFT — Fri, 24 Jul 2009 15:55:38 GMT

You should confirm gcreconnect works - there may be a problem with your environment.

re: MAPI and Exchange 2007

Cash — Fri, 24 Jul 2009 10:33:14 GMT

Using GcReconnect code, I've written the code below. Although it seems to change the flag to 0x8002, OpenMsgStore still fails with MAPI_E_FAILONEPROVIDER.

MAPIAdminProfiles(0, &lpProfAdmin);

lpProfAdmin->AdminServices((LPTSTR)Profile,

NULL,

&lpSvcAdmin);

SvcAdminOpenProfileSection(lpSvcAdmin,(LPMAPIUID)&pbGlobalProfileSectionGuid, NULL, MAPI_MODIFY, &lpGlobalProfSect);

SizedSPropTagArray(1,sptTags) = {1, PR_PROFILE_CONNECT_FLAGS};

hRes = lpGlobalProfSect->GetProps((LPSPropTagArray) &sptTags, 0, &ulValues, &pPropArray);

if (SUCCEEDED(hRes) && (MAPI_W_ERRORS_RETURNED != hRes))

{

pPropArray[0].Value.ul |=

CONNECT_IGNORE_NO_PF;

hRes = lpGlobalProfSect->SetProps(1,

pPropArray, NULL);

}

else

{

}

if (FAILED(hr = lpGlobalProfSect->SaveChanges(FORCE_SAVE)))

{

}

And then...

MAPILogonEx(0,cProfile,"",ulFlags,&lpSession);

HrMAPIFindDefaultMsgStore(lpSession, &cbDefStoreEid, &pDefStoreEid);

lpSession->OpenMsgStore(0, cbDefStoreEid, pDefStoreEid, NULL, MAPI_BEST_ACCESS,&lpMDB);

What may be wrong?

re: MAPI and Exchange 2007

Stephen Griffin - MSFT — Thu, 23 Jul 2009 14:45:04 GMT

Cash - you shouldn't be logging on to the profile first. All the modifications should happen before you log on. Take a look at the source for gcreconnect if you want to see code that sets this flag.

re: MAPI and Exchange 2007

cash — Thu, 23 Jul 2009 12:12:18 GMT

I'm using the recent MAPI CDO library (6.5.8069.0) for connecting to an Exchange Server 2007 without a public folder.

If I edit the PR_PROFILE_CONNECT_FLAGS using MFC MAPI program, both the MFC MAPI and my program can connect via this profile, it works. But when i change the flag programmatically, i get MAPI_E_FAILONEPROVIDER from OpenMsgStore.

The windows account and the mail account are the same (administrator)..

I call MapiLogonEx, change the flags and then try to open the message store. Is it about the order of methods? When exactly i should change the flag?

re: MAPI and Exchange 2007

Stephen Griffin - MSFT — Mon, 08 Dec 2008 17:42:32 GMT

It is possible, but you'll need to read through the Exchange protocol documentation to figure out what you need to do. Start by looking at the MSDN article on creating task items: http://msdn.microsoft.com/en-us/library/cc963264.aspx