> delivered to local mail boxes, or the outside world, and my cpu is about
> pegged with the Mailscanner process. If I disable spamassassin in
> MailScanner everything works as expected???
There are a few possibilities here, all pretty much similar.
You might have a bad rule that is taking too much processor time.
You might have too many rules
You might have too many spamd children (Or however MS does this)
You might be trying to do a huge Bayes or AWL expire on each mail scan, and
MS is killing the SA instance before it has a chance to complete. So the
next one does the same thing.
Look to the size of your bayes/all DBs and see if they are huge. Look at
the log and see if it looks like the SA children seem to be trying to do
bayes or awl stuff and getting killed in the middle. You can do a manual
expire run and see if that cleans things up.
If that isn't it, loop at 'top' and see if you are swapping like crazy.
Probably not, as at least *some* mail should get thru this way.
If you are completely processor bound and it isn't an expire run, you might
have a bad rule. Try removing any local rules files temporarily.
Loren
