We use AWL via SQL. We wrote a script that will prune certain records from the database weekly to keep AWL small. Basically we delete any entries with a positive score and a count of 1 (as these are mostly randomly generated addresses that will never happen again).
> -----Original Message----- > From: derringer [mailto:[EMAIL PROTECTED] > Sent: Monday, March 20, 2006 7:01 PM > To: users@spamassassin.apache.org > Subject: RE: AWL growing too large > > > I'll post my reply here, since my question on manipulating the AWL hasn't > been responded to. > > Basically, and forgive me for saying this, I am contemplating moving the > AWL > database to mySQL is well, not only because of what has been mentioned > here, > but also because the supplied tools to even modify the database are > really, > really poor. You cannot, unless I have missed it, remove an 'address:IP' > pair from the database via the spamassassin supplied commandline > options... > it simply either removes every entry for whatever 'address' you supply, or > it parses all email addresses out of an email (which is not what you > want), > then removes every instance of them from all source IPs, or it adds 100 to > every single instance of that 'address' that you supply, and not > necessarily > the address:IP 'pair' that you want. > > Have I missed something? I mean, can you send spamassassin a parameter on > the commandline like"[EMAIL PROTECTED]:X.X" so it removes a specific > instance, or is that unsupported? > > The AWL lacks sufficient manipulation tools at this point in time, that it > really should have. As an administrator, I get emails that the AWL has > adjusted badly, and I want to fix that specific email address:IP pair, and > I > simply can't do that with the current tools. > > Any suggestions other than switching to MySQL and directly manipulating > the > database? > > -- > View this message in context: http://www.nabble.com/AWL-growing-too-large- > t1284694.html#a3506512 > Sent from the SpamAssassin - Users forum at Nabble.com.
