On Thu, 2005-12-15 at 02:27 +0100, Mark Martinec 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).
> 

My issue finally resolved last night down to duplicate .cf files in my
spamassassin config folder. I run RulesDuJour and it puts the files in a
sub folder, but there were duplicates in the config folder. Thing is,
why did this not cause an issue using SA 3.0?

Once I disabled dns and bayes, things worked, but still the dups were
processing. I removed the dups and whala! Once I got that done, it runs
fine with dns and bayes enabled. I even took amavis back up to
max_server of 10. But I will change to MySQL. Thanks for the help!

--
Robert



-------------------------------------------------------
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/

Reply via email to