On Tue, Feb 21, 2012 at 17:24, Matt Garretson <[email protected]> wrote: > On 2/18/2012 10:23 AM, Mișu Moldovan wrote: >> And in that setup it was SpamAssassin doing all the heavy lifting, >> which resulted in +90% of the incoming mail being rejected before >> reaching the ClamAV filter. In the end I have disabled AV scanning > > Funny... on my system it's the exact opposite. Scans with clamd are > basically free, and spamassassin is the cpu hog. As a result, every > single message goes through clam first. [snip]
I didn't say SpamAssassin used less resources than ClamAV, just that it was more reliable even though spam filtering kicked in before AV filtering in our setup. The ClamAV daemon, although automatically restarted in case of a crash, still hanged occasionally or crashed repeatedly, both requiring manual intervention. -- mișu _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
