> -----Original Message----- > From: RW [mailto:rwmailli...@googlemail.com] > Sent: Wednesday, August 29, 2012 1:23 PM > To: users@spamassassin.apache.org > Subject: Re: When force-expire doesn't work... > > On Wed, 29 Aug 2012 09:40:29 +0200 > Rob Sterenborg wrote: > > > Hello, > > > > I'm in the process of installing a new relay MTA, and part of it > > means moving the current Bayes database to the new server (bdb -> > > MySQL). > > > > The database is quite big because of the bayes_token and > > bayes_seen tables, so I wanted to expire old data. I've set > > bayes_expiry_max_db_size=1000000 in local.cf[1] (there were *way* > > more entries) and ran "sa-learn -D --force-expire -u > > '<username>'" > > -u is for virtual users with per user bayes
I know. I am planning to use virtual users, this was just done with a first import meant for general use/testing.. > you should run this as the unix user that runs spamd or equivalent. In which case sa-learn will choose the wrong user. This will not be the case in the future. > > What bothers me is that I can't update the > > spam_count and ham_count fields because AFAIK I don't have > > information about that. > > You shoudn't normally touch those in an expire. Why not? Is it not related to the number of tokens that are in the table? > > Because bayes_seen was also quite big I read up on that too. > > Since the table doesn't include any age information and (most) > > everything I found says "just delete it", I emptied the table. > > Although I think it's strange to just throw away information about > > previous seen messages that have been classified as either spam or > > ham. Any other insight in this would be valued.. > > Some people include atime information for that purpose. Yes, thanks.. I ran into a post that mentioned that some time after I posted, and added such field which will indeed do what I want. (It isn't going to help with the imported data though, because that info is not available in the original bdb files.) -- Rob
