Re: [Qmail-scanner-general]Clamav /QmailScan 1.20/451 qq temporary problem

2004-01-06 Thread Jared Seipel
7;t read clamav.conf and dies. So, either changing the ownership of clamav.conf to qscand or changing the perms to 644 should fix this. ------- Jared Seipel - INetU Managed Hosting - http://www.inetu.net E-Mail: [EMAIL PROTECTED] - Phone: (61

Re: [Qmail-scanner-general]Clamav /QmailScan 1.20/451 qq temporary problem

2003-12-22 Thread Jared Seipel
I haven't tried it in this particular case, but using clamdscan instead of clamscan has lessened the load by at least 75% of some our more heavy hitting boxes, so calmscan isn't an option for me. :) ------- Jared Seipel - INetU Manag

Re: [Qmail-scanner-general]Clamav /QmailScan 1.20/451 qq temporary problem

2003-12-18 Thread Jared Seipel
On Thu, 18 Dec 2003, Abraham Lincoln wrote: > Hi, > I just installed netqmail-1.04 and qmail-scanner 1.20 and Clamav 0.65 > > qmail works fine withouth Qmail-Scanner when i installed qmail scanner and using > clamav every time my Email clients sending an email we're getting "451 qq Temporary

Re: [Qmail-scanner-general]spamassassin

2003-06-23 Thread Jared Seipel
ntaining spam. > Evolution stopped when stupidity became painless. Add --scanner fast_spamassassin="SPAM:" to the end of your string when running the configure script to generate qmail-scanner-queue.pl, so it looks like: ./confgiure --scanner fast_spamassassin=&quo