On Wed, 20 Aug 2014, redtailjason wrote:
Thank you for your response! Our Bayes is MySQL. Currently, the expiry runs via cron job to run during low volume times.
Does the MySQL log say anything suggestive?
Here is the dump from one of the scanners: netset: cannot include 127.0.0.1/32 as it has already been included 0.000 0 3 0 non-token data: bayes db version 0.000 0 613 0 non-token data: nspam 0.000 0 0 0 non-token data: nham
This doesn't explain the long scan time, but you can't expect Bayes to score at all until you learn some ham too. It needs examples of both to be able to tell the difference.
-- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- Efficiency can magnify good, but it magnifies evil just as well. So, we should not be surprised to find that modern electronic communication magnifies stupidity as *efficiently* as it magnifies intelligence. -- Robert A. Matern ----------------------------------------------------------------------- 4 days until the 1935th anniversary of the destruction of Pompeii
