Scott: putting our conversation back on the list: >> http://www200.pair.com/mecham/spam/clamav-amavisd-new.html >> Read this and get your system set up properly. Make sure you actually >> have installed clamd (it may be a separate package on some systems) >> and then uncomment the Clamd section in amavisd.conf, and then make >> sure it works. >> >> >> # ### http://www.clamav.net/ >> # ['ClamAV-clamd', >> # \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd"], >> # qr/\bOK$/, qr/\bFOUND$/, >> # qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ], >> # # NOTE: the easiest is to run clamd under the same user as amavisd; match >> the >> # # socket name (LocalSocket) in clamav.conf to the socket name in this entry >> # # When running chrooted one may prefer: ["CONTSCAN {}\n","$MYHOME/clamd"],
> ok, thanks to your great help, I got ClamAV clamd working... check out > the before and after timers on it.. before = clamscan, after = clamd > Before > AV-scan-1: 87193 (92%)97, > After > AV-scan-1: 20 (4%)36, > also speaking of Timers, what would cause SA-check to sit here like this: > Apr 20 22:12:02 ns1.freedyhome.com /usr/local/sbin/amavisd[30991]: > (30991-01) spam_scan: DSPAM not available, skipping it > Apr 20 22:12:02 ns1.freedyhome.com /usr/local/sbin/amavisd[30991]: > (30991-01) timer set to 320 s for SA (was 480 s) > Apr 20 22:12:02 ns1.freedyhome.com /usr/local/sbin/amavisd[30991]: > (30991-01) calling SA parse, SA version 3.1.1 > Apr 20 22:12:02 ns1.freedyhome.com /usr/local/sbin/amavisd[30991]: > (30991-01) CALLING SA check As far as the above goes, I don't see anything sitting here. The time is 22:12:02. I do see below that it took a total of 24.5 seconds to process the message and SpamAssassin took up 23.6 seconds of that. Notice 22:12:26. > Then after the email is sent, the timer shows > Apr 20 22:12:26 ns1.freedyhome.com /usr/local/sbin/amavisd[30991]: > (30991-01) TIMING [total 24524 ms] <...> > SA check: 23635 (96%)99, <...> With version 3.1.1 of SpamAssassin I think you are going to see some rather long SA check times. Short of going with a faster CPU, are you using SQL for Bayes storage (or at least set "lock_method flock" in local.cf)? Are you using many custom add-on rules sets (like SARE and others)? It would be good to debug spamassassin and look for timeout errors in Razor, Pyzor, DCC (if you use them) and other network tests. Often using a local caching DNS server decreases time spent on network tests. I use bind9 as a caching only server. su vscan -c 'spamassassin --lint -D' You can capture the debug output with something like this (the directory the test.log file is sent to must be writable by the amavisd-new user). su vscan -c 'spamassassin --lint -D >/var/amavis/test.log 2>&1 &' wait about 40 seconds, then see what you captured: less /var/amavis/test.log or grep the file for 'timed' and 'timeout' It is not unusual for me to see a couple timeouts. Gary V ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
