ClamAV 0.93 released

Randal, Phil prandal at
Tue Jun 3 11:28:13 IST 2008


One buglet...

I'd edited MailScanner.conf to read:

Monitors for ClamAV Updates = /usr/local/share/clamav/*.cld /usr/local/share/clamav/*.cvd

And upgrade_MailScanner_conf complained

Your setting for 'Monitors for ClamAV Updates' is broken.
It should look like this (unless your ClamAV is installed
somewhere else)
Monitors for ClamAV Updates = /usr/local/share/clamav/*.inc/* /usr/local/share/clamav/*.cvd 

As 0.93 no longer uses the .inc subdirectories this is broken.



Phil Randal
Networks Engineer
Herefordshire Council
Hereford, UK

-----Original Message-----
From: mailscanner-bounces at [mailto:mailscanner-bounces at] On Behalf Of Julian Field
Sent: 24 May 2008 23:34
To: MailScanner discussion
Subject: Re: ClamAV 0.93 released

I have just published a new beta of MailScanner including support for Mail::ClamAV 0.22, which is now provided in my ClamAV+SpamAssassin package. These two should work successfully as a pair, and I would appreciate testers.


P.S. It's nice to be out in the big wide world again, I didn't go outside the building for a week, now I just need to get my sleep cycle back to normal. I am too used to sleeping in a hospital bed, and to being awake at 6am (I normally was in the shower by 6:30am in hospital).

The latest news seems to be that they may pass my case back to the liver transplant team, and not do a small bowel transplant after all. But possibilities currently include everything up to, and including, replacing my stomach, duodenum, jejunum, ilium (small intestines, all 26 feet of it), liver, pancreas and all the blood vessels that join them all together. So just about anything is possible right now. Within the next month or two, I should hear what (if any) other tests they want to do, but my case will be discussed at a national level and they all have to agree what is best for me to have done. That could possibly take a few months, so I don't expect any quick news. I managed a very nice chat with a guy from their chronic pain team, and he had several new ideas for painkillers that the people in Southampton had never considered, which was very useful. Southampton's attitude seems to be that if a couple of Paracetomol (Tylenol) don't handle it, then they don't really know much about what to do :-) It's not quite as bad as that, but you get my drift :-) The Cambridge team at Addenbrookes actually appreciate the problem of your body becoming used to opiates and that you build up a tolerance to them, and had some ideas for new drugs which I have only rarely been exposed to before, such as Oramorph and Fentanyl.

That's about the latest news, I'll keep you posted.


P.S. It's my list, and I'll top-post if I want to ;-)

Alex Broens wrote:
> On 5/23/2008 1:21 PM, David Lee wrote:
>> On Mon, 28 Apr 2008, Denis Beauchemin wrote:
>>> Leonardo Helman a écrit :
>>>> Hi I'm using clamavmodule
>>>> I've made a patch for the Mail::ClamAV to compile (later I'll send 
>>>> it to the Mail::ClamAV mantainer)
>>> Hello,
>>> Anything new on the official Mail::ClamAV module? I just looked and 
>>> version 0.21 still supports maxratio which have been removed from 
>>> Clam 0.93...
>>> Since there are known exploits for 0.92 I am beginning to feel the 
>>> urge to upgrade to 0.93...
>> Scott Beck has released version 0.22 of Mail::ClamAV in the last few 
>> days.
>> Could I suggest that some of us with test facilities and with a 
>> little technical experience try the various combinations of the older 
>> and newer versions of ClamAV and Mail::ClamAV and verify which 
>> combinations work and fail?
>>  1. Old+old:  We know that the combined earlier versions work.
>>  2. New ClamAV + old Mail::ClamAV:  It has been reported that the new
>>     ClamAV (0.93) breaks with older Mail::ClamAV (0.20/0.21).  Could
>>     someone provide details of what this breakage is?  Is there a quick
>>     recipe to reproduce the problem that ClamAV 0.93 had introduced?
>>  3. New + new: Julian's Clam+SA package would ultimately be new+new.  
>> Can
>>     we verify that this fixes any previously verified breakage?  Also 
>> that
>>     it does not seem to introduce any new problems.
>>  4. Old ClamAV + new Mail::ClamAV: There are inevitably sites which use
>>     other sources (not Julian's package).  Can we check what happens 
>> with
>>     if someone were to upgrade their Mail::ClamAV module but leave the
>>     main ClamAV software back on 0.92?  (Probably not too important, but
>>     it would be a nice data point to complete the set...)
>> Given Julian's sadly enforced absence from work, I'm sure he would 
>> appreciate it if we can do this tabulation for him.
> Will try to test new Mail::ClamAV with ClamAV 0.93 and on several old 
> versions of MS


Julian Field MEng CITP CEng
Buy the MailScanner book at

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654 PGP public key:

This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website! 

More information about the MailScanner mailing list