Partager via

August 2014 Release of MFCMAPI and MrMAPI

  • Article

The August 2014 Release (build 15.0.0.1042) is live: https://mfcmapi.codeplex.com.

It’s been a chaotic half year and I haven’t been able to get my builds out as often as I’d like, though I did do a ton of work on MFCMAPI.

This month we get a totally rebuilt MAPI property parsing engine. As it’s an engine change, you shouldn’t notice much different in MFCMAPI itself, but all of my XML exports get an upgrade.

Here's a change list - see the Issue Tracker and ChangeSets on Codeplex for more details:

  • Property Parsing engine rebuilt
  • MrMAPI: Fixed malformed XML in profile list when no profiles exist
  • Adding attachments is now possible
  • MrMAPI: Can now dump the receive folder table
  • Export now includes large props by defalt
  • SmartView: Understands PR_PREDECESSOR_CHANGE_LIST

Enjoy.

Comments

  • Anonymous
    October 20, 2014
    The comment has been removed

  • Anonymous
    October 20, 2014
    I don't think the dn you get from the gal in 365 will be sufficient to connect to a mailbox. You need to get the mailbox's proper server dn, like you'd get from autodiscover.

  • Anonymous
    December 09, 2014
    Hi Stephen, As you know, Exchange 2013 SP1 and Outlook 2013 SP1 support MAPI over HTTP. But MFCMAPI seems unable to open other mailbox from GAL by MAPI/HTTP profile, which will work by Outlook Anywhere profile. As below: I created 2 profiles for a user "Test1" which has "receive-as" right for the mailbox database, one profile "Test1-RPC" is for Outlook Anywhere, another profile "Test1-Http" is for MAPI over HTTP. When I logon the "Test1-RPC" with MFCMAPI.exe, and use the session to open another user Test2's mailbox from GAL, everything is OK. But when I use profile "Test1-Http" to logon, I cannot open user Test2's mailbox,  just got "MAPI_E_CALL_FAILED==0x80004005" error code from OpenMsgStore function. Do you have any idea about this issue?