MAILSCANNER Digest - 7 Nov 2003 to 8 Nov 2003 (#2003-315)

[Alessandro Bianchi]

Hi Julian

My files were overwrited because I removed the package completely, so
it did a full and clean install.

I expected that.
Anyway I double checked the wrappers and they look OK.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitdefender7-autoupdate
Type: application/octet-stream
Size: 20829 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20031110/874efcce/bitdefender7-autoupdate.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitdefender7-wrapper
Type: application/octet-stream
Size: 1334 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20031110/874efcce/bitdefender7-wrapper.obj
-------------- next part --------------


So I don't understand the reason it stops scanning...

I'll investigate further and let you know, in the meantime any
suggestion is welcome...

I enclose the bitdefender 7 autoupdate and wrapper

The line to be added to the virus.scanners.conf is the following

bitdefender     /usr/lib/MailScanner/bitdefender7-wrapper       /opt/bdc


WHAT CHANGES
==============
path now defaults to /opt/bdc and binaries are'nt placed in a "shared"
subdirectory anymore

There are no changes in the output:

I've tested these files with 4.24 with no problems at all.

The two files enclosed are "zero conf" so that they don't require any
configuration from the users.

Best greetings to everyone

Alessandro Bianchi

> Hi everyone
>
> I've just experienced a panic problem.
>
> I wanted to test the disarm action (very good idea) so I installed and
> compiled on my Red Hat 9 box the latest beta.
>
> On this box I'm running the stable relase with no problem and I use the
> following virus scanners:
>
> bitdefender7 f-prot clamav
>
> In this exact order (bitdefender7 is a self modified bitdefender script
> to ensure compatibility with le latest bitdefender release, it works
> fine in the stable release)
>
> After I installed the 4.25.6 everything seemed fine, so I tried to mail
> me an OpaServ virus that I always keep on hand for testing purposes.
>
> Well, it passed and I was very surprised of that.
>
> I double checked the virus scanner conf file and it was OK so were the
> wrappers files.
>
> I took a look at the mailog and discovered that MailScanner reported
> the following:
>
> starting content checking
> not infected
>
> Well it really didn't seem to take care of the scanners output.
>
> I sow the bitdefender.lock f-prot.lok and clamav.lock in my temp dir,
> but MailSacanner seamed to ingore the scanners output.
>
> I tried to scan the Opaserv file and some EICAR signatures with the
> line tools of every scanner and they all ewere functioning properly, so
> I had to go bach to 4.24.5.
>
> Is someone else having the same experience?
>
> Thanks to all
>
> Alessandro Bianchi
>
> ------------------------------
>
> Date:    Sat, 8 Nov 2003 22:34:55 +0000
> From:    Julian Field <mailscanner at ECS.SOTON.AC.UK>
> Subject: Re: Problem with latest beta: stops scanning!
>
> I tested it originally myself with EICAR and it detected all of them
> just fine.
> You aren't using an old -wrapper with a newer MailScanner are you? I
> changed the command-line spec of the -wrapper scripts a couple of
> versions ago.
>
> Can you give me your bitdefender modifications please to get everyone
> up to
> the latest release of bitdefender?
>
> At 21:26 08/11/2003, you wrote:
>> Hi everyone
>>
>> I've just experienced a panic problem.
>>
>> I wanted to test the disarm action (very good idea) so I installed and
>> compiled on my Red Hat 9 box the latest beta.
>>
>> On this box I'm running the stable relase with no problem and I use
>> the
>> following virus scanners:
>>
>> bitdefender7 f-prot clamav
>>
>> In this exact order (bitdefender7 is a self modified bitdefender
>> script
>> to ensure compatibility with le latest bitdefender release, it works
>> fine in the stable release)
>>
>> After I installed the 4.25.6 everything seemed fine, so I tried to
>> mail
>> me an OpaServ virus that I always keep on hand for testing purposes.
>>
>> Well, it passed and I was very surprised of that.
>>
>> I double checked the virus scanner conf file and it was OK so were the
>> wrappers files.
>>
>> I took a look at the mailog and discovered that MailScanner reported
>> the following:
>>
>> starting content checking
>> not infected
>>
>> Well it really didn't seem to take care of the scanners output.
>>
>> I sow the bitdefender.lock f-prot.lok and clamav.lock in my temp dir,
>> but MailSacanner seamed to ingore the scanners output.
>>
>> I tried to scan the Opaserv file and some EICAR signatures with the
>> line tools of every scanner and they all ewere functioning properly,
>> so
>> I had to go bach to 4.24.5.
>>
>> Is someone else having the same experience?
>>
>> Thanks to all
>>
>> Alessandro Bianchi