EDIT 8/10/2010: Please note that this blog post covers namely the history of named properties in Exchange. For updated and current guidance of how to deal with named properties issues, please see t...
Updated Jul 01, 2019
Version 2.0
Blog Post
As someone new to the exchange scene from a background in *nix i am astonished by this. I understand that you are having to deal with a legacy design, but the whole tone of the article seems to imply that data in the x-headers are useless unless you've seen one before in a previous version of exchange or an authorised mapi application has requested one.
x-headers are very useful sources of information about the message and it's history.
Even if you don't expose the x-header data via PropIDs then at the very least keep it so that if an email is forwarded out of exchange via smtp these headers could be reattached.
Or why not store all the unknown x-headers in a text field that is always attached to PropID 0xFFFF?
Perhaps I'm naive and simply dont understand some of the concepts - entirely possible. But it seems to me that just losing that data is not acceptable.
x-headers are very useful sources of information about the message and it's history.
Even if you don't expose the x-header data via PropIDs then at the very least keep it so that if an email is forwarded out of exchange via smtp these headers could be reattached.
Or why not store all the unknown x-headers in a text field that is always attached to PropID 0xFFFF?
Perhaps I'm naive and simply dont understand some of the concepts - entirely possible. But it seems to me that just losing that data is not acceptable.