Jason Haar <[EMAIL PROTECTED]> wrote: > > Bad clam release? It's the latest stable release, for what that's worth. I could believe that's the problem, but it sure looks like it's working.
> You can turn up debuging: set it above 100 ($DEBUG=100) and Q-S won't delete > anything after it runs. Then you can hand-check the remanents to see what > happened in /var/spool/qmailscan/ OK, I did that. Still didn't catch it, but when I ran the exact same command that qmail-scanner says it's running, it works fine: # /usr/local/bin/clamscan -r --tempdir=/var/spool/qmailscan/sparge10297234564232519 --disable-summary --unzip --unrar --unace --unarj --zoo --lha --jar --tar --tgz /var/spool/qmailscan/sparge10297234564232519 /var/spool/qmailscan/sparge10297234564232519/eicar.txt: Eicar-Test-Signature FOUND # echo $? 1 # The weird thing is that clamscan works when I do contrib/test_installation.sh, but not when it's run via SMTP. I even ran the test as user qmaild and it worked fine. Argh, this is frustrating. OK, one last thought... I disabled softlimit and tried again. Bingo: worked like a charm. Why the hell didn't clamscan/qmail-scanner/tcpserver/perl/whatever complain that it was running out of memory? And why the hell does clamscan need more than 10,000,000 bytes? Sigh. Oh well, sorry to bother you and thanks for your help. -Dave ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
