On Thu, 2005-05-12 at 12:20 -0500, Jon Dossey wrote:I'd go through your maillog, and check the spamassassin processing times, and see if you can pinpoint where the processing time shoots up. Then, go through your mqueue and take a look at the offending message.
It wasn't just one message. It was every message.
I think what he's getting at is that one message can consume enough CPU and memory to bog down processing all the other ones, too. I saw this with spamd and large attachments, before I started bypassing large messages around spamassassin.
