Re: [Clamav-users] clamd virusevent xmessage

--- Stephen Gran <[EMAIL PROTECTED]> wrote: > On Fri, Jul 29, 2005 at 03:21:35PM +1000, Kevin O'C > said: > > Hi All, > > > > debian sarge system > > > > logging in as root > > > > clam v8.X > > > > configured clamd.conf - do not have copy of file > at > > this location - will post if require

Re: [Clamav-users] clamd virusevent xmessage

On Fri, Jul 29, 2005 at 03:21:35PM +1000, Kevin O'C said: > Hi All, > > debian sarge system > > logging in as root > > clam v8.X > > configured clamd.conf - do not have copy of file at > this location - will post if required. > > line in clamd.conf is this: > VirusEvent /whatever/whatever/xmes

[Clamav-users] clamd virusevent xmessage

Hi All, debian sarge system logging in as root clam v8.X configured clamd.conf - do not have copy of file at this location - will post if required. line in clamd.conf is this: VirusEvent /whatever/whatever/xmessage "virus found" i have tested virus event command line in shell - produces xmes

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

Frank Sfalanga, Jr. wrote: I did have two versions. The original RPM installed to /usr/bin with the config files in /etc. The compiled version installed the binaries in /usr/local/bin and the config files in /usr/local/etc. I'm sure with all the correct ./configure switches I could override

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

On Jul 28, 2005, at 06:59 PM, Dale Walsh wrote: On Jul 28, 2005, at 06:26 PM, OpenMacNews wrote: It looks like you have installed different versions of clamav in / usr and /usr/local oops. missed that, sorry ... nice catch. r One of the biggest issues I've seen is when building Cla

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

Daniel wrote: It looks like you have installed different versions of clamav in /usr and /usr/local Try which -a freshclam which -a clamscan I did have two versions. The original RPM installed to /usr/bin with the config files in /etc. The compiled version installed the binaries in /usr/l

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

On Jul 28, 2005, at 06:26 PM, OpenMacNews wrote: It looks like you have installed different versions of clamav in / usr and /usr/local oops. missed that, sorry ... nice catch. r One of the biggest issues I've seen is when building ClamAV on a Mac prior to 10.4.x The majority of the p

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

It looks like you have installed different versions of clamav in /usr and /usr/local oops. missed that, sorry ... nice catch. r ___ http://lurker.clamav.net/list/clamav-users.html

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

Frank Sfalanga, Jr. wrote: I recently built a new qmail server using the process at qmailrocks.org from which I compiled/installed ClamAV 0.83. Later I upgraded to ClamAV 0.86.2 using this procedure: * Rename /usr/local/bin/clamdscan /usr/local/bin/clamdscan.orig * Copy /usr/local/bin/clam

Re: [Clamav-users] WARNING: Your ClamAV installation is OUTDATED

frank, cref: , and check your DNS refresh ... cheers, richard ___ http://lurker.clamav.net/list/clamav-users.html

[Clamav-users] WARNING: Your ClamAV installation is OUTDATED

I recently built a new qmail server using the process at qmailrocks.org from which I compiled/installed ClamAV 0.83. Later I upgraded to ClamAV 0.86.2 using this procedure: * Download latest tarball from http://clamav.net and place it in the /downloads/qmailrocks/ directory * Untar and ungzi

Re: [Clamav-users] Clamav + maildrop

Julio Maidanik said: > > > Hi, > I have found that adding clamav checking through maildrop is quite easy. > It is so simple, that I would believe it might be useful for other people, > and so I am offering it to included in the clamav's contrib > subdirectory. > > CLAMOUT=`/usr/local/bin/clamdsc

Re: [Clamav-users] uncompressed zip size of Zero

On Wed, Jul 27, 2005 at 03:07:57PM -0500, Noel Jones wrote: > Recent clamav (0.86.2, probably some earlier versions) should detect > modified zips as "Exploit.Zip.ModifiedHeaders" > The detection is built into the unzip code, there isn't an actual signature. > > If your zip file is hacked "correc

[Clamav-users] Clamav + maildrop

Hi, I have found that adding clamav checking through maildrop is quite easy. It is so simple, that I would believe it might be useful for other people, and so I am offering it to included in the clamav's contrib subdirectory. CLAMOUT=`/usr/local/bin/clamdscan --stdout - 2>&1` log $CLAMOUT