On Tue, Aug 17, 2004 at 04:10:25PM +0100, "Rogers, Zo� A." wrote: > I have reduced the size in local.cf - bayes_expiry_max_db_size 80000, > however this has no effect because token expiry never takes place and the > database just grows and grows, this is what check_bayes_db looks like.
FYI: expiry is best effort. if you have out of control growth, 1) blow away your bayes DBs (aka: restart), 2) learn fewer messages. > 0.000 0 1735776000 0 non-token data: newest atime that's your problem, which is why expiry fails. that atime value is somewhere in January 2025. I have yet to have someone show me a message that exhibits this behavior, so I can't debug why atimes in the future occur, but there is a kluge in 3.0 which prevents future atime values from being used. You may want to consider just removing your current DBs, letting them get back up to speed, and switching to 3.0 (there is currently a release candidate, and a final version should be out soon...) -- Randomly Generated Tagline: "If you want to waste food, throw a vegetable." - The Drew Carey Show
pgpQewITDc7hG.pgp
Description: PGP signature
