It's not "fixed", it's only hack-fixed. There is no real expiry of bayes_seen, nor the AWL, in SA 3.1.x.
It's now safe to delete bayes_seen, you won't corrupt your whole bayes DB if you do that. That's the only fix I know of that's been applied. See http://issues.apache.org/SpamAssassin/show_bug.cgi?id=2975 >From the bottom: --------------------- 'We need to do something, but a full seen expiry system isn't going to happen for 3.1.' 'I still like the idea of just letting bayes_seen be optional. If people want to trim it, let them delete the file and have it be recreated. IIRC, the only place that's an issue is when going r/o w/ the DB where it requires the file right now.' -------------------- Jason Frisvold wrote: > No takers on this? Have I hit upon a FAQ question? I swear I looked > and searched and I didn't find suitable answers... > > On 11/23/06, Jason Frisvold <[EMAIL PROTECTED]> wrote: >> Greetings, >> >> Just a few quick questions. First, I noticed that prior to 3.1.0 >> bayes_seen was not auto expiriing. That bug is marked as fixed, so is >> it safe to say that bayes_seen is now expiring automatically and that >> a 20+ meg bayes_seen file is valid? >> >> Next, the bayes_tok database is over 3 Gig at this point. I'd like to >> cut that down a bit as the machine is having considerable trouble >> dealing with it. So I have a few questions concerning this. >> >> First, can I modify the expiry time, causing an earlier expiration? >> If so, what are the consequences of such an action? >> >> Second, does the autoexpire run for every instance of spamassassin? >> ie, does it run every time a message is processed? If not, how does >> it determine when to run it? Would it be better to disable auto >> expire and create a cron job that runs later in the evening to deal >> with auto expire? >> >> I noticed in the wiki that when forcing an expire, you should stop >> spamassassin first. Is this strictly necessary? What are the >> consequences of not doing this? >> >> Any other suggestions for increasing the speed of the database? >> >> Thanks! >> >> -- >> Jason 'XenoPhage' Frisvold >> [EMAIL PROTECTED] >> > >
