From the documentation I have the following about Non-transmittable properties - http://technet.microsoft.com/en-us/library/bb851492(EXCHG.80).aspx "Non-transmittable properties - This range represents properties that are not delivered outside the organization when Exchange delivers a message." I understand the above as when Exchange is delivering a message to a recipient inside the organization the message contains any Non-transmittable properties, but when delivering a message to a recipient outside the organization the Non-transmittable properties are removed. For Exchange 2000 and Exchange 2003 this is also the case, but for Exchange 2010 the Non-transmittable properties are always removed. How to configure Exchange 2010 server to behave as Exchange 2003? Not removing Non-transmittable properties when sending messages inside the organization. Regards, MadsMads Torp Jacobsen

Dear MAds, could you please explain why do you need that? Thanks, Victor Ivanidze

Hi, We are using an application that is setting Non-transmittable properties, and is depending on these properties to exist to work. /MadsMads Torp Jacobsen

Can you change your application to use the named properies instead of non-transmittable ones?

Would like to avoid if possible because it is not something that can be configured so it will require modifications to the application. But of course if the result is that Non-transmittable properties for some strange reason no longer is supported by Exchange it is the only solution to the problem. Mads Torp Jacobsen

In your Exchange 2003 environment, where the sender and recipient on the same mailbox database? Non-transmittable properties are valid for a particular store or location, and are supposed to be dropped from a message when sent. In Exchange 2010 all messages are now “transmitted” through the hub transport server. This happens even if the sender and recipient are both on the same store. This difference in architecture appears to be where the Non-transmittable properties are being stripped out. I found this post that talks about these properties. http://blogs.msdn.com/b/nayan/archive/2008/10/31/what-you-need-to-know-about-mapi-properties.aspx It says that “...Transmittable properties are transferred with a message; non-transmittable properties are not transferred with a message…” I think the best solution to this issue is going to be to write your property in a named property, not as a Non-transmittable property.

Thanks for the respond that is very usefull. Now I know that the only solution is to use named or transmittable properties instead of non-transmittable properties. I just did'nt want to modify the application if the problem could have be solved simple by changing a configuration setting on the Exchange server, but now I know.Mads Torp Jacobsen