Kyle, > Gary/Henrik, thanks for the responses. I set $log_level = 2 and it is > showing about 18 seconds to scan a message (see output below). It was > taking on average about 600ms before.
Turning on SA logging may show where the processing stalls (by observing the running SA log on the screen): # amavisd debug-sa Or perhaps running command line spamassassin utility during such times may show the same stall in an interactive session, where it is more readily perceived: # su vscan -c 'spamassassin -t -D <0.msg' Mark ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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/
