Noticed today (again) how long some messages take to test. The first thing that comes to mind is some dns is getting overloaded answering joe-job rbldns backskatter, causing timeouts or slow responce times.
Then I was thinking about how some tests are excluded because they generate too much regex load, which can be problematic even if it's a good test. Some time back I recall a thread, amounting to why not quit remaining tests if spam threshold is reached, the answer was some tests have negative scores and could change the result. So, here are two ideas, on startup, after all the conf files are parsed create a hash that has tests sorted by score, with the largest positive tests starting after zero, ordered like this -5 -5 -2 -1 0 6 5 4 2 2 1 then test in that order, whenever a test brings the message to a spam score level, exit with result. (and add a switch to optionally run all tests) Another approach might be simpler to integrate than above, simply do all the negative score tests first and pull out if the score gets to spam level. // George -- George Georgalis, information system scientist <IXOYE><
