Is there limitation in setting aging rule?

By aging rule do you mean expiration rule ?

If that be carefull, the release notes says:

Use of expiration rule could cause you to unintentionally delete messages. (400343)

A problem exists with the attribute store.expirerule.name.foldername.folderpattern.

Expiration rules that include this attribute will select folders outside the criteria you specify. This could create serious problems, including the unintentional deletion of messages. Therefore, do not use this attribute to limit a folder selection.

I expect to have been of help

juanpaulocabezas at 2007-6-29 17:40:54 >

That bug is long fixed, for both 5.1 and 5.2, as long as you have a current hotfix.

Your initial question, "is it ok to have several thousand rules", though. . .

I can't imagine anybody has actually tested this. I would expect to see some performance impact when the expiration pass is run overnight. Depending on the size of your store, you might find that too many rules would prevent any from actually being completed overnight.

The most I've seen is in the tens, less than a hundred. Most places are able to get by with less than 10 rules.

jay_plesset at 2007-6-29 17:40:54 >