Discussion:
Named prop Issue exchnage 2007
(too old to reply)
Tom B
2008-09-09 17:28:02 UTC
Permalink
I was reading through some prior posts and we have run into the infamous
named prop issue. We just increased the quota size but I don't think that is
going to solve my problem long term at some point in the near future we are
going to max out. The only real solution I see is recreating the database.
That is going to be a hassle to do so every 6 months. The reason we have so
many named props is due to our very large amount of spam.

What is a longer term solution to this? Is there some sort of automated
script we can create to flush the table every month or so the counters
restart?
Andy David {MVP}
2008-09-09 17:32:58 UTC
Permalink
On Tue, 9 Sep 2008 10:28:02 -0700, Tom B
Post by Tom B
I was reading through some prior posts and we have run into the infamous
named prop issue. We just increased the quota size but I don't think that is
going to solve my problem long term at some point in the near future we are
going to max out. The only real solution I see is recreating the database.
That is going to be a hassle to do so every 6 months. The reason we have so
many named props is due to our very large amount of spam.
What is a longer term solution to this? Is there some sort of automated
script we can create to flush the table every month or so the counters
restart?
http://www.codeplex.com/HeaderFilterAgent
Tom B
2008-09-09 17:40:16 UTC
Permalink
I saw that but does this Only allow emails on my internet based servers from
people on my whitelist? Or si this just stripping the headers out and still
allowing the mail to go through?
Post by Andy David {MVP}
On Tue, 9 Sep 2008 10:28:02 -0700, Tom B
Post by Tom B
I was reading through some prior posts and we have run into the infamous
named prop issue. We just increased the quota size but I don't think that is
going to solve my problem long term at some point in the near future we are
going to max out. The only real solution I see is recreating the database.
That is going to be a hassle to do so every 6 months. The reason we have so
many named props is due to our very large amount of spam.
What is a longer term solution to this? Is there some sort of automated
script we can create to flush the table every month or so the counters
restart?
http://www.codeplex.com/HeaderFilterAgent
Andy David {MVP}
2008-09-09 17:52:14 UTC
Permalink
On Tue, 9 Sep 2008 10:40:16 -0700, Tom B
Post by Tom B
I saw that but does this Only allow emails on my internet based servers from
people on my whitelist? Or si this just stripping the headers out and still
allowing the mail to go through?
Just strips the headers. THe whitelist designates which headers not to
strip. I have tested this in the lab and it works.
Post by Tom B
Post by Andy David {MVP}
On Tue, 9 Sep 2008 10:28:02 -0700, Tom B
Post by Tom B
I was reading through some prior posts and we have run into the infamous
named prop issue. We just increased the quota size but I don't think that is
going to solve my problem long term at some point in the near future we are
going to max out. The only real solution I see is recreating the database.
That is going to be a hassle to do so every 6 months. The reason we have so
many named props is due to our very large amount of spam.
What is a longer term solution to this? Is there some sort of automated
script we can create to flush the table every month or so the counters
restart?
http://www.codeplex.com/HeaderFilterAgent
Dgoldman [MSFT]
2008-09-09 18:12:58 UTC
Permalink
Going forward this will be an issue until the next version of exchange where
we have put some planning in to this.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Dgoldman [MSFT]: http://blogs.msdn.com/dgoldman
Download OABInteg: http://code.msdn.com/oabinteg
--
Post by Andy David {MVP}
On Tue, 9 Sep 2008 10:40:16 -0700, Tom B
Post by Tom B
I saw that but does this Only allow emails on my internet based servers from
people on my whitelist? Or si this just stripping the headers out and still
allowing the mail to go through?
Just strips the headers. THe whitelist designates which headers not to
strip. I have tested this in the lab and it works.
Post by Tom B
Post by Andy David {MVP}
On Tue, 9 Sep 2008 10:28:02 -0700, Tom B
Post by Tom B
I was reading through some prior posts and we have run into the infamous
named prop issue. We just increased the quota size but I don't think that is
going to solve my problem long term at some point in the near future we are
going to max out. The only real solution I see is recreating the database.
That is going to be a hassle to do so every 6 months. The reason we have so
many named props is due to our very large amount of spam.
What is a longer term solution to this? Is there some sort of automated
script we can create to flush the table every month or so the counters
restart?
http://www.codeplex.com/HeaderFilterAgent
Loading...