On So 19 Okt 2003 05:35:45p Theo Van Dinter wrote: > On Sat, Oct 18, 2003 at 10:23:39PM +0200, Bernd Kuhls wrote: >> The only solution I see is to delete the Bayes database and start >> from scratch:-( > > the real solution is to let more tokens get learned, and then the > expiry code can properly function. the sa-learn "EXPIRATION" > section talks about the issue.
Hi, the problem might be that from 2.5x to 2.6x the mechanism to save the age of tokens has changed. At the time when the conversion took place all tokens already present got the time of the conversion, those might apply to thousands of tokens. Since then there could be only some hundreds of tokens newly learned so there is a disbalance of age count present in the Bayes db which prevents it from expiring older tokens. Is there a way to remove all those tokens which where imported from the old Bayes db without removing the later tokens? Lets say: Kill all tokens which have the oldest date? Greetings, Bernd ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
