check out amavis-new. it's what I use. runs clam and spamassassin on
every mail. Note, this is my home server, VERY low volume. I'm not
sure what load would look like on a heavily loaded system
On Thursday, April 29, 2004, at 12:33 PM, Faustino Benitez wrote:
Hi:
I have a question about th
On Thursday, April 29, 2004, at 09:35 AM, Dave Ewart wrote:
On Thursday, 29.04.2004 at 08:38 -0500, John Madden wrote:
Update to ClamAV version 0.70
What are the consequences of not upgrading? I'd have to plan
downtime,
There shouldn't be any need for (significant) downtime - build the new
clam
just a word of advice for the future.i'd have put symlinks in the
old locations, not copied executablesthat's a good way to end up
with multiple versions down the line. if you make a symlink, then when
you upgrade in location a, location b now points to the correct
things...
On Monday
what comes out with "rpm -qa|grep -i clam" ?
On Monday, April 26, 2004, at 11:16 AM, Ricardo Bernardes wrote:
weird
this is the output of "freshclam --version"
freshclam / ClamAV version 0.70-rc
and from "clamd --version" i got
clamd / ClamAV version 0.70-rc
i've installed the new rpm and chec
if your smtp outgoing server is the same server clam is running on,
that should happen. for instance, i'm running postfix and clam on the
same server via amavis..if i'm on that box, or using that box as
outgoing smtp, it gets scanned. in fact, it gets scanned user to user
local to the box via
