Start with your mail log, which messages are causing the problem? are
they big, do they have certain type of attachments, etc. (all these
attributes can be controlled with MailScanner) If you can isolate
one sample, better, that way you'll have something to test directly.
From what I see in
On Fri, 1 Jun 2007, Rob Sterenborg wrote:
Start with your mail log, which messages are causing the problem? are
they big, do they have certain type of attachments, etc. (all these
attributes can be controlled with MailScanner) If you can isolate
one sample, better, that way you'll have
Hi all,
In my setup I have several mail-relay and wanted to use a dedicated
server running clamd to scan viruses for all my mail-relays. For this
purpose, I am using a program called clamd-stream-client on each
mail-relay to check for viruses, all pointing to my clamd server. This
gives me
I seem to be having trouble with clamscan 0.91rc1 choking with the
current daily.wmd file. It was working fine until the most recent db update.
# clamscan --version
ClamAV 0.91rc1-exp/3337/Fri Jun 1 18:05:09 2007
# clamscan /tmp/email.txt
Segmentation fault (core dumped)
Now remove the
On Fri, 1 Jun 2007, Noel Jones wrote:
I seem to be having trouble with clamscan 0.91rc1 choking with the current
daily.wmd file. It was working fine until the most recent db update.
I don't have this problem, but I don't seem to have a daily.wmd file in my
daily.inc either. I have
At 09:56 PM 6/1/2007, Christopher X. Candreva wrote:
On Fri, 1 Jun 2007, Noel Jones wrote:
I seem to be having trouble with clamscan 0.91rc1 choking with the current
daily.wmd file. It was working fine until the most recent db update.
I don't have this problem, but I don't seem to have a
On Fri, 1 Jun 2007, Noel Jones wrote:
fatfinger error on the name, I am referring to daily.wdb as the
pasted session shows.
Ah, sorry. Bleary-eyed error not catching it in the sesion. :-)
Are you using 91rc1? It's very repeatable here. I have
Yes, so far it has been running fine. My
At 10:20 PM 6/1/2007, Christopher X. Candreva wrote:
On Fri, 1 Jun 2007, Noel Jones wrote:
fatfinger error on the name, I am referring to daily.wdb as the
pasted session shows.
Ah, sorry. Bleary-eyed error not catching it in the sesion. :-)
Are you using 91rc1? It's very repeatable here.
On Fri, 1 Jun 2007, Noel Jones wrote:
Ok, I've narrowed it down to the following TWO lines in daily.wdb:
X:http.//www\.ebay\.co\.uk.+:.+emailpics.\.ebay\.com:14-
X:http.//info.citibank.com.+:https.//offer.citibank.com:14-
I removed the files in the .inc directories and freshclam pulled down a
At 10:48 PM 6/1/2007, jef moskot wrote:
On Fri, 1 Jun 2007, Noel Jones wrote:
Ok, I've narrowed it down to the following TWO lines in daily.wdb:
X:http.//www\.ebay\.co\.uk.+:.+emailpics.\.ebay\.com:14-
X:http.//info.citibank.com.+:https.//offer.citibank.com:14-
I removed the files in the
Noel Jones wrote:
At 09:56 PM 6/1/2007, Christopher X. Candreva wrote:
On Fri, 1 Jun 2007, Noel Jones wrote:
I seem to be having trouble with clamscan 0.91rc1 choking with the current
daily.wmd file. It was working fine until the most recent db update.
I don't have this problem, but I don't
On Fri, 1 Jun 2007, Noel Jones wrote:
So you're having this same problem?
Yes, I was getting core dumps trying to clamscan.
I used sigtool -u to unpack daily.cvd, then hand-created a daily.inc
directory with all the unpacked files, then hand-edited daily.wdb to
remove the offending lines.
At 11:39 PM 6/1/2007, Dennis Peterson wrote:
Noel Jones wrote:
I'm running Solaris 10 x86 here and cannot duplicate your error. I moved
the daily.wdb file to /tmp and clamd died. I restarted it with svcadm
and it started and ran file. I then rsync'd daily.wdb from /tmp back to
the working
13 matches
Mail list logo
