Thanks a lot Alex, I'm testing trim_whitelist.pl at this exact time. I'll have a look to your script too and will test it on another copy of the file (for the moment I've copied it on another machine and disabled use_auto_whitelist in my local.cf to see the result)
I'll give you feedback on this Regards, Stephane -----Message d'origine----- De : Alex Bramley [mailto:[EMAIL PROTECTED] Envoyé : mercredi 20 septembre 2006 12:01 À : users@spamassassin.apache.org Objet : Re: AutoWhitelistExpiry Theo Van Dinter wrote: > On Mon, Sep 18, 2006 at 05:48:35PM +0200, Stéphane LEPREVOST wrote: >> I'm surprised that nobody seems to complain for problems with >> auto-whitelist file growing. Of course, it may be only a question of >> free time to do this (I understand SO much these problems...) but >> does someone knows if someone plan to code it in a few time ? > > Last I heard, AWL was going to be replaced by the History plugin, > which would do expiry and such, but that plugin has since never gone anywhere. > > I was also thinking about changing our DBM access to generically > support timestamps for all entries, then have some general functions > included to support expiry. That way we'd have expiry for all > DBM-related systems, instead of currently where Bayes has it's own > stuff specifically coded in, and things like AWL have none. > > As usual, patches welcome. :) > In the interim, there's the check_whitelist and trim_whitelist scripts, and I've amalgamated their functionality into the attached maintain_whitelist script which can be cronned up easily. I guess you could consider this a "patch" ;) The usual caveats apply; I've only given this minimal testing but it seems to work fine. General usage is: maintain_whitelist -d /path/to/auto-whitelist -c -t See maintain_whitelist --help for detail. Cheers, Alex
