September 2011 Release of MFCMAPI and MrMAPI

Before we get to business, a comment: MFCMAPI does not appear anywhere in Wikipedia. This is a sad. Very very sad.

The September 2011 Release (build is live:

We got a handful of new features this time. MrMAPI can now parse flags on the fly, For instance, if you want to know what 0x3a means in PR_MESSAGE_FLAGS, MrMAPI can tell you:
C:>mrmapi PR_MESSAGE_FLAGS -flag 3a
Found property PR_MESSAGE_FLAGS (0x0E070003).

Additionally, I added a feature to MFCMAPI to sort the names of properties such that the more common name is listed first. For instance, if you looked at an Exchange profile for the property 0x6612001E, you used to see the following list of property names, in alphabetical order:
Now, when you look at the same property, we see the name we expect to see come first:

I also added property name lookup to the restriction editor and a switch in Options to force MFCMAPI to load MAPI from the System directory, useful for older Exchange servers where Outlook Express may also be installed.

Here’s a change list – see the Issue Tracker on Codeplex for more details, or look at the code:

  • MFCMAPI: Better property name sorting. All alternate property names are now hand sorted with the most common name first. Please let me know if you find any which could be sorted better!
  • MrMAPI: Flag lookup via the new –Flag switch.
  • MFCMAPI: Force System MAPI, allowing MFCMAPI to work again on older Exchange servers.
  • MFCMAPI: Prop lookup in the Restriction Editor
  • Hex Editor: Bug fix when editing Base64.
  • SmartView: Found a type of Public Folder entry ID I wasn’t parsing correctly.
  • MFCMAPI: Count Named Properties will now report the highest named property in more situations.


Comments (2)

  1. Gulab says:

    Nice update and changes. I am going to try it on the server TODAY!

  2. Lev says:

    SG: MFCMAPI does not appear anywhere in Wikipedia. This is a sad. Very very sad.

    LK: I'm surprised MAPI is mentioned there.  I'm just happy it's NDY.