Affirmative, this took care of it. I am sure it was just me over
looking something in documentation, but it seems to be humming right
along now.
Thanks everyone!
-Geoff
On Wed, 2004-02-04 at 23:18, Geoff Sweet wrote:
> AHA! Ok I bet I glazed right over this in the reading... but in the
> logs
AHA! Ok I bet I glazed right over this in the reading... but in the
logs I get:
Wed, 04 Feb 2004 23:05:44 -0800:8979: --output of clamuko was:
/var/spool/qmailscan/tmp/gstc01.gstcsystems.com10759647444618979: Can't
access the file ERROR
--
I bet I am suppose to be having clamd running as the sam
Rob wrote:
Are you running qmail with daemontools ? It is possible that your
softlimit for is set too low. The memory requirements for clamav
recently went up due to adding a large number of virus definitions.
When I had this problem, the following information was present in the
qmail-scanner
On Tue, Feb 03, 2004 at 08:56:42AM -0800, Geoff Sweet wrote:
> I am using clamav on OpenBSD 3.2 with Spamassassin and qmail and
> qmail-scanner. Recently I upgraded clamav from 0.5x to 0.65,
> spamassassin to 2.63 and upgraded qmail-scanner to 1.20 as well. Now
> however no infected email payload
greetings all.
I am using clamav on OpenBSD 3.2 with Spamassassin and qmail and
qmail-scanner. Recently I upgraded clamav from 0.5x to 0.65,
spamassassin to 2.63 and upgraded qmail-scanner to 1.20 as well. Now
however no infected email payloads are getting stopped.
I am trying to figure out wh
