Re: [Clamav-users] CLAM 0.65 Not Identifying Anything

> > Both CLAM 0.60 and Solo Antivirus identify the following file as bieng > > infected with W97/Marker. But since upgrading to CLAM 0.65, CLAM does > > not detect the infection; either as a regular file or as a mail > > attachment via clamav-milter. But the message - > X-Virus-Scanned: ClamAV ve

[Clamav-users] CLAM 0.65 Not Identifying Anything

Both CLAM 0.60 and Solo Antivirus identify the following file as bieng infected with W97/Marker. But since upgrading to CLAM 0.65, CLAM does not detect the infection; either as a regular file or as a mail attachment via clamav-milter. But the message - X-Virus-Scanned: ClamAV version 'clamd / Cl

Re: [Clamav-users] Upcoming Clamav Stable

> Fortunately almost all the issues reported by Ed have been fixed (and > they were not critical). I think there will be no delay this time :) Excellent! We've really been looking forward to a new release. Anyone know if a fix for scanning of OLE2 files is in? Before it was giving false positiv

Re: [Clamav-users] production issues?

> I just installed ClamAV yesterday on my mail server and so far it works great Recent snapshots work well, the 0.60 release is hopeless under any kind of load. > - I am only using it to scan my personal mail so far. I've seen references in this > list that clamd can fail once in a while - and

Re: [Clamav-users] clamscan paranoid?

> > I have a samba fileserver, and I run clamscan every night as a cron job, > > moving infected files to a quanrantine directory (to help prevent any > > virii that have made it in from spreading). > > The next morning I look in quarantine and see some files. So I > > disinfect them from a Win32P

[Clamav-users] clamscan paranoid?

I have a samba fileserver, and I run clamscan every night as a cron job, moving infected files to a quanrantine directory (to help prevent any virii that have made it in from spreading). The next morning I look in quarantine and see some files. So I disinfect them from a Win32PC with either Macaf

Re: [Clamav-users] Stability clamav-milter + clamd

> > A) sometimes clmilter.sock disappears > > B) sometimes clamd crashes > > During the last night A) happend 22 times and B) happened 4 times. So it seems > > that with this version problem A) is the bigger problem. > I made some major changes in libclamav and clamd that should fix stability > p

[Clamav-users] clamav milter seems stable

I pulled clamav-devel from CVS yesterday (9-19-2003), and the milter and clamd has now been running > 24 hours. This is the longest I've ever seem the milter run without wedging. Hopefully it keeps it up, thanks guys. --- This sf.net email is

Re: [Clamav-users] clamav-20030829

> > > > Is this the milter fixing release? > > > The clamd+clamav_milter duet should work more stable but this is not yet > > > a final fix. > > Yep, it ran for about a day - > What about the CVS version ? The couple of times I have tried I haven't had any luck getting the CVS version. Can you

Re: [Clamav-users] clamav-20030829

> > Is this the milter fixing release? > The clamd+clamav_milter duet should work more stable but this is not yet > a final fix. Yep, it ran for about a day - [EMAIL PROTECTED] root]# ps ax | grep clam 32011 ?S 0:00 clamd 32014 ?Z 0:00 [clamd ] 32015 ?S 0:0

Re: [Clamav-users] clamav-20030829

Is this the milter fixing release? > The snapshot doesn't contain the virus databases. ... --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Clamav-u

Re: [Clamav-users] Re: clamd [defunct]

> Well, I can prove the failure for > root # /usr/clamav/sbin/clamd --version > clamd / ClamAV version 20030806 > selfbuilt with exim/exiscan 4.21. > one thread goes defunct, the master thread idles around and the third is > stuck in an empty event loop. > Exim connections pile up to (i

Re: [Clamav-users] Building CLAMd Snapshot fails

> I'm trying to use the spec file from the 0.60 src rpm, to build an RPM > from the clamav-20030806.tar.gz snapshot (to see if the milter/clamd is > more stable). > Just unpacking the tar ball, running ./configure, and make works. > But rpmbuild -bb clam.spec dies with - > source='clamav-milter.c'

[Clamav-users] Building CLAMd Snapshot fails

I'm trying to use the spec file from the 0.60 src rpm, to build an RPM from the clamav-20030806.tar.gz snapshot (to see if the milter/clamd is more stable). Just unpacking the tar ball, running ./configure, and make works. But rpmbuild -bb clam.spec dies with - source='clamav-milter.c' object='c

Re: [Clamav-users] Win32 Virii Scanner

> > I'm curious if there is, or anyone is working on, a Win32 client > > filesystem scanner that uses clamd? Or if there is a good trick for > > scanning Win32 workstations with clam? > If you share (and mount) the disk via samba, you can use clamscan to > scan files a win disk. True, I was just

[Clamav-users] [clamd ]

I'm trying to use clamav-milter. But clamd goes walk about after awhile - [EMAIL PROTECTED] root]# ps ax | grep clam 6878 ?S 0:00 clamd 6879 ?Z 0:00 [clamd ] 15107 pts/1S 0:00 grep clam [EMAIL PROTECTED] root]# rpm -q clamd clamd-0.60-4 [EMAIL PROTECTED] root]

Re: [Clamav-users] Win32 Virii Scanner

> > I'm curious if there is, or anyone is working on, a Win32 client > > filesystem scanner that uses clamd? Or if there is a good trick for > > scanning Win32 workstations with clam? > I'm going to write a simple (graphical) win32 client for clamd in September. Excellent! > Currently you can mo

[Clamav-users] Win32 Virii Scanner

I'm curious if there is, or anyone is working on, a Win32 client filesystem scanner that uses clamd? Or if there is a good trick for scanning Win32 workstations with clam? --- This SF.net email is sponsored by: VM Ware With VMware you can run