Hello, >>> I have also this kind of problems... I think it is more related to >>> SpamAssassin because I had to disable all spam scanning on my system >>> to get it working again. >>> >>> Any hints ? >> >> Collect a sample of a problematic message, feed it to >> a command-line spamassassin running in its debug mode, >> and see where it gets stuck: >> >> # su vscan -c 'spamassassin -t -D <sample.msg' > > Big problems is that I have tooo mutch messages in queue (about 3000) > and it seems to lock on random messages, I didn't found yet a pattern > and still working on it...
After testing a lots and used a lot monit (thanks to it), it seems that my setup for AWL etc... that used MySQL is able to trigger the problems very fast. I had reverted into plain db as before and the problem has more or less gone for now... /Xavier ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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/
