Thomas, Thomas,
> spamassassin < /var/lib/amavis/tmp/...-09604/parts/p002 ... > Segmentation fault > > So it really doesn't seem to be Amavisd-new's fault - I'll go on and > stress other people ;-) Thanks a lot for your help! Ok. If there are pictures in the mail, my next suspect is a SpamAssassin plugin ImageCheck, which is known to segfault on certain corrupted images. It just wasn't designed with robustness in mind. Btw, a simple temporary workaround for segfaulting SpamAssassin is to let amavisd run SA in a subprocess: $sa_spawned = 1; It is somewhat more memory hungry on the system due to increased number of processes, but is a simple way out to clear a queue of messages with broken images. > NB: amavisd-nanny is a tool allowing me to have a quick overview of > what's currently going on - and not thought to run "forever" > as some kind of a daemon. So if amavis likes to "go away" whenever > a single component fails - how do I let the cleanup (as done by > nanny - while running) happen automagically? (Or did I completely > missunderstand something?) Your understanding is correct. There is not much need to clear a database of process statuses, unless there are hundreds or thousands of stale entries left there, but in this case you'd have a more serious problem to solve anyway. Apart from amavisd-nanny, an amavisd restart also clears the database. I wouldn't worry, even if you run amavisd-nanny very rarely or not at all. Mark ------------------------------------------------------------------------- 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/
