Re: Spamassassin as memory hog
Losing the functionality of spamassassin is something we would consider a real blow as we filter a bunch of junk automatically to user spam directories with its information. I'd recommend just restarting the mail task with a cron job once a day. Works for us. Let the backup mail server handle things for a few seconds in the middle of the night.
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
Sorry for the late addition. I'd also seriously recommend milter-greylist running ahead of everything else. It's not an ideal solution as there are a small number of badly configured (ahem - exchange) servers that don't properly handle the reply code and won't retry, but you drastically cut down the number of messages you have to deal with in clamav and spamassassin which might help.