On Wed, 14 Jun 2017 13:38:49 +0100 RW <rwmailli...@googlemail.com> wrote:
> The way I suggested has advantages: > - there's no need to clean-out expired rules manually A minor advantage at best. And nothing stops you from keeping your expiring rules in a separate .cf file so they can be auto-purged. > - it's clear which rules are permanent, temporary and expired No advantage at all; it's clear with the tflags expiry=xxxx method. > - grep can easily separate the three classes No advantage for your method. > - expired body rules aren't compiled by sa-compile So what? Does that really matter given that probably only a tiny percentage of rules will have expiries? > - it doesn't complicate the core modules. :) Have you read the code? SpamAssassin is pretty complex as it is. This is a very minor addition. The benefits of a standard, supported, maintained way to do expiry far outweigh everything else. Regards, Dianne.
