> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Nigel Horne
>
> cl_mbox() isn't being called. Please ensure that the file you give it
> (eicar-binhex) is a valid email.
It is, and I've put it up at http://macgregor.myby.co.uk/eicar-binhex,
howeve
On Saturday 28 February 2004 11:15 am, Rob wrote:
> A test run showing it all not working:
>
> $ clamscan --debug -r --mbox eicar-binhex
> LibClamAV debug: Loading databases from /usr/local/share/clamav
> LibClamAV debug: Loading /usr/local/share/clamav/main.cvd
[snip]
cl_mbox() isn't being calle
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Nigel Horne
>
> Whoops I meant message.c. Anything later than
1.30 - dated 13 Feb for 0.67
1.34 - dated 20 Feb for the snapshot
> It stops BinHex encoded messages from testvirus.org for me.
Hmmm
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Nigel Horne
>
> What version of mbox.c do you have? Binhex was only disabled
> in CVS for a couple of days.
Just tried the latest CVS with exactly the same result. With the following
inside a mai
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Nigel Horne
>
> What version of mbox.c do you have? Binhex was only disabled
> in CVS for a couple of days.
V1.44
I'd guess then that there never was a message saying that the functionality
had b
On Saturday 28 Feb 2004 7:52 am, Rob wrote:
> I've got 0.67 installed and the BinHex encodings still get through. I
> wonder if the following comment in message.c might be related:
>
> * Revision 1.23 2004/02/03 23:04:09 nigelhorne
> * Disabled binhex code
>
> I'm running it on FreeBSD 5.2-CU
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Nigel Horne
>
> On Friday 27 February 2004 10:27 pm, Bryce wrote:
> > Test # 17, 8, 5, 4, and 2 are making it through. I am using
> version .65.
> > What can I do to prevent this?
>
> Binhex was a
OK but I am running freebsd 4.7.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Lucas
Albers
Sent: Friday, February 27, 2004 4:24 PM
To: [EMAIL PROTECTED]
Subject: RE: [Clamav-users] Re: 5 from testvirus.com came through
Just wait for .67 to hit testing
Just wait for .67 to hit testing from unstable on debian.
2 more days and it will be in testing.
Then it will take 10 seconds to upgrade.
--
Luke Computer Science System Administrator
Security Administrator,College of Engineering
Montana State University-Bozeman,Montana
---
> Nigel Horne wrote:
>
>>On Friday 27 February 2004 10:27 pm, Bryce wrote:
>>
>>
>>>Test # 17, 8, 5, 4, and 2 are making it through. I am using version .65.
>>>What can I do to prevent this?
>>>
>>>
>>
>>Binhex was added in 0.67, so all binhex encoded e-mails will get through
>>unless you upgrade.
Is the upgrade an easy one?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of John Jolet
Sent: Friday, February 27, 2004 3:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [Clamav-users] Re: 5 from testvirus.com came through
Nigel Horne wrote:
>On Friday
Nigel Horne wrote:
On Friday 27 February 2004 10:27 pm, Bryce wrote:
Test # 17, 8, 5, 4, and 2 are making it through. I am using version .65.
What can I do to prevent this?
Binhex was added in 0.67, so all binhex encoded e-mails will get through
unless you upgrade.
-Nigel
I guess that
On Friday 27 February 2004 10:27 pm, Bryce wrote:
> Test # 17, 8, 5, 4, and 2 are making it through. I am using version .65.
> What can I do to prevent this?
Binhex was added in 0.67, so all binhex encoded e-mails will get through
unless you upgrade.
-Nigel
13 matches
Mail list logo