Adriel wrote: > I have come across some other threads in the mailing list that > resemble my problem, though I haven't found anything exactly like it. > I have run 'amavisd debug-sa > ~/amavisd_log 2>&1 &' and analyzed the > output when one of the processes goes wild. However, it doesn't seem > like there was anything wrong in the debug log, except for SA not > being able to open the auto-whitelist (which I fixed). That wasn't the > problem though.
> When I have to 'kill -9' the process, it leaves an email in the tmp/ > folder. It seems to be one message that keeps getting retried and > causing the amavisd process to go wild. It is an undeliverable mail > message that is trying to be sent back to the sender. It contains a > jpg image and Postfix has added some lines about an error not being > able to write to the queue, like so: > host xx.xxx.x.xxx[xx.xxx.x.xxx] said: 451 Error: queue > file write error (in reply to end of DATA command) If you are running amavisd-new as a before queue filter, I believe this tells you what you already know, amavisd-new is fubar'd at this point in time. > In the maillog every time I come across this situation, the process > gives a warning: WARN: MIME::Parser error: part did not end with > expected boundary. I didn't think it was such a big deal since it was > a warning, but it seems to happen every time this occurs. > Adriel So, if the message is in the deferred queue, and you know the sender's address, and there are not 300 messages in there from the same sender, grep the sender using mailq so you can obtain the ID number, then use the ID number to delete the message, for example: # mailq | grep [EMAIL PROTECTED] ID size time sender B588616D23 643 Thu Sep 8 11:51:20 [EMAIL PROTECTED] # postsuper -d B588616D23 This ID should match the problem message in your logs (so I suppose you could simply get the ID from your log). At least this is one option. It does not help determine why MIME::Parser had a problem with the message however. Sometimes keeping a sample of a message like this would be good for debugging purposes. However, I'm not certain how you would go about doing that without disabling amavisd-new and subsequently letting other mail through unscanned. Gary V ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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/
