> > On Tue, Oct 12, 2004 at 09:31:28PM -0400, Jason Frisvold wrote: > > Is there any accepted method for expiring AWL entries? I'm > currently > > using the SQL implementation of AWL. > > > > If there was no accepted method, my plan was to add a > TIMESTAMP field > > to the database and expire old records... > > > > How odd, I was just writing a blurb about this in my > ApacheCon presentation. In the future, AWL will have some > sort of expiration, in the mean time, with SQL, I've had > great success with a lastupdate of type TIMESTAMP column that > gets automatically updated whenever the row is changed, which > also happens to be last access for AWL. > > Then you can do cool things like: > delete from awl where lastupdate < 2040701000000; to delete > anything that hasn't been updated since the first of July. > > Also lets you do a quick: > > delete from awl where count = 1; > > To get rid of all the single message hits. >
John, if you need expiry right now, you can use my patch on bug 3802 if you want. It will basically do what Michael is talking about except for purging count=1 entries. http://bugzilla.spamassassin.org/show_bug.cgi?id=3082 I use it with my AWL in mysql and it works fine. It adds a 'auto_whitelist_expiry' conf option which you can set to however many seconds you want to expiry old entries on (1 month is the default setting), then just the sa-learn --awl-expire call. Its not auto-expiry, and its SQL specific, but it works for me! :) FYI, That patch was created against a -preX, so minor changes to the patch may be needed for current SVN... you may have to hand patch it in. Dallas
