Mark wrote: >> > I will note that a number of amavisd users including me saw their >> > average message processing times go up from (e.g.) 2 seconds to 10-12 >> > seconds on upgrading from amavisd 2.2.x and SpamAssassin 3.0.x to >> > amavisd 2.3.3 and SpamAssassin 3.1.0. ... I mention it so that if >> > you see this you will recognize it as now relatively normal; Mark's >> > systems apparently did not experience this. >> >> Indeed I haven't noticed such an increase. If the set of SA checks >> on upgrading SA 3.0.x to 3.1 did not change much, the time for >> a check should be about the same. But there are lots of knobs >> in SA, and the default list of RBL, DNS, SPF, ...
> To my previous post I should add that I've switched bayes to SQL > long time ago. Bayes on a non-SQL database may well be the culprit > after upgrade to SA 3.1 (as just being discussed on the SA list). > Mark I have low powered systems (Celeron 500s), I do use MySQL for Bayes, but after upgrading to 3.1, I got SA timeout errors so I had to increase the default of $sa_timeout = 30; to 60 seconds. I think 3.1 does a better job than 3.0.x (which I never got working as well as 2.64) but I did get a false positive that scored 12.1, the first one I've had in months. Gary V ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
