One of my favorite things about my job is that I get to learn new stuff everyday! It's like being in school all of the time! And yes, I was that person in class that always ruined the curve for eve...
Updated Jul 01, 2019
Version 2.0
Blog Post
7 MIN READ
Confused About Named Properties Quotas in Exchange 2003 and Exchange 2007? Join the Club!
@Jason - Correct, until you get to SP2. In Sp2 and later, you can set Header Promotion mode to turn off creation of x-header named props, period.
@Pete_Heilig_Gartner - Re-read the original "Named Properties, X-Headers, and You" post. The issue is (of course) that all clients consuming MAPI everywhere would need to be recompiled (along with new versions of MAPI.DLL, all service providers, and all utilities). It isn't just a matter of sticking more bits on the _SPropValue, modifying the macros to work against 64 bit ints, modifying all existing property tags, creating a mapping scheme from old PTAGs to EPTAGS, changing the unpacking (and packing) code and changing the underlying database format. It's getting every client (including ones that no longer even have source code) to be able to retrieve a list of properties where things get dicey.
As mentioned, named properties are now a per mailbox resource in E14.
@Pete_Heilig_Gartner - Re-read the original "Named Properties, X-Headers, and You" post. The issue is (of course) that all clients consuming MAPI everywhere would need to be recompiled (along with new versions of MAPI.DLL, all service providers, and all utilities). It isn't just a matter of sticking more bits on the _SPropValue, modifying the macros to work against 64 bit ints, modifying all existing property tags, creating a mapping scheme from old PTAGs to EPTAGS, changing the unpacking (and packing) code and changing the underlying database format. It's getting every client (including ones that no longer even have source code) to be able to retrieve a list of properties where things get dicey.
As mentioned, named properties are now a per mailbox resource in E14.