From: "Andrew Donkin" <[EMAIL PROTECTED]>
Kevin Gagel:
I'm finding that scans are taking as long as 798 seconds
Daryl O'Shea:
Scan times of 798 seconds are probably a result of a bayes expiry. If
auto expiry is enabled (default) I'd disable it and run a manually
expiry as a cron job.
This is a tally of SA scan times at my site from January 14th, rounded
down to the nearest 100 seconds, ignoring those below 1000 seconds:
1000 30
1100 41
1200 14
1300 5
3000 3
3100 35
3200 11
4400 1
4500 3
Those are combined figures from two load-balanced spamd hosts. Both
hosts exhibited similar behaviour, so the problem is caused by
something they share: a flood of incoming email, MySQL Bayes, or DNS
lookups. I doubt it's Bayes because I have per-user stats, which
makes the expiry runs rare and quick. And the RBL timeout is 10
seconds.
More interestingly, here are the times and counts for all the scan
times under 1000 seconds on that same day:
100-140 10
300-310 128
950-980 5
So what is about the five minute mark that is so attractive to SA?
None under 100?
I'm going to start putting "gosh this is taking a long time" debugging
into spamd, but I would love to hear from anyone who has any ideas
about it.
That length of time is suggestive of DNS timeouts. Are you actually
able to reach all the BL DNS servers you are trying to use?
{^_^}
