We just rolled out SpamAssassin 2.60 as a spam filtering option to our users (after using it on IT staff guinea pigs for about a month), and only have about 20 people using it so far out of a possible 800 or so. In theory, the mail server (dual 1.13 PIIIs, 1Gb RAM, FreeBSD 4.8-STABLE) should be able to handle the load just fine (it currently delivers about 25000 messages a day via sendmail and procmail (didn't blink for the SoBig virus rush), and probably runs about a tenth of that through SA).
However, in the last two weeks, I've had SA go haywire, and take up mucho CPU time. The first time, I was up to a load average of 16, and sendmail quit sending mail (the default cutoff for sendmail is a load of 12, which we've never hit). I've limited spamd to 5 concurrant processes, but that doesn't seem to help. When there were 5 haywire jobs this morning, the entire SA system quit working altogether (spams weren't getting filtered), so that's obviously not what I want. Any idea what would cause SA to start grabbing huge amounts of CPU time? I'm just running the basic rulesets, no evil or anything like that. I can't even tell if it's hanging up on a particular message--I'm not sure where to find that information. It's usually hanging on messages being delivered to me, but that may be just because I get an insane amount of email. -- Dan Bongert [EMAIL PROTECTED] SSCC Unix System Administrator ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
