In my last blog post on named properties, I detailed the history of named properties, how they are arranged, mapped, and how Exchange (since Exchange 2000) has created named property mappings for x...
Updated Jul 01, 2019
Version 2.0
Blog Post
We own a Barracuda Spam Firewall which adds x-header information to all mail from the internet. Some examples are:
X-Barracuda-Spam-Score
X-Barracuda-Start-Time
X-Barracuda-Connect
These are the only x-header information that is useful to us. We would like to be able to remove named properties that got added from internet mail before we started stripping them out with the HeaderFliter agent by Codeplex so we don't have to increase the quota on our databases for named properties.
Thanks for the update on this post, but it still doesn't give us the answer that if we are at the quota limit right now before applying Rollup 8 for SP1, after we install the update, what do we do with the quota limit? Do we still need to increase it?
In our case, we dont' have any applications that need to promote custom named properties with the exception of people installing stupid mailplugins every now and then.
X-Barracuda-Spam-Score
X-Barracuda-Start-Time
X-Barracuda-Connect
These are the only x-header information that is useful to us. We would like to be able to remove named properties that got added from internet mail before we started stripping them out with the HeaderFliter agent by Codeplex so we don't have to increase the quota on our databases for named properties.
Thanks for the update on this post, but it still doesn't give us the answer that if we are at the quota limit right now before applying Rollup 8 for SP1, after we install the update, what do we do with the quota limit? Do we still need to increase it?
In our case, we dont' have any applications that need to promote custom named properties with the exception of people installing stupid mailplugins every now and then.