[Mimedefang] Re: MD 2.51/clamav .88.1 failure

[Kris Deugau]

[someone] wrote:
>> On Friday, 4/7, I updated clamav from version .88 to .88.1. When I did 
>> so, virus scanning broke. Maillog was filled with entries like:
>> Apr  7 15:49:23 hoover mimedefang.pl[66764]: Problem running virus 
>> scanner: code=999, category=cannot-execute, action=tempfail Apr  7 
>> 15:49:23 hoover sm-mta[67374]: k37JnNo4067374: Milter: data, 
>> reject=451 4.3.0 Problem running virus-scanner
>> Apr  7 15:49:23 hoover sm-mta[67374]: k37JnNo4067374: 
>> to=<sbrege at rhnet.org>, delay=00:00:00, pri=145673, stat=Problem 
>> running virus-scanner
>>
>> The clamd.log showed no problems. It seemed to be happy as a, well, 
>> clam. I'm running MD version 2.51 on FreeBSD 5.4.
>> I was able to fix it by re-installing clamav .88
>> Has anyone else seen this problem? Do I need to update MD? Any other 
>> thoughts?

Shawn Gendle wrote:
> Same problem here running RedHat EL4 latest update. No indication as to 
> what is causing the problem.

I recently updated a number of systems here;  no issues.  (I *have* had 
weird things happen in the past, however.)

RH7.3, MD 2.51
Debian woody, MD 2.51
WBEL3, MD 2.54

All of the MIMEDefang installs are locally-built packages, no 
particularly special customizations.

ClamAV is installed from Dag Wieers/RPMForge on the RH and WB systems, 
and from the Debian package maintainer's people.debian.org woody 
backport for the Debian system.

The RH7.3 and Debian systems run clamd as the defang user;  the WBEL3 
box runs it as root (WTF? - gotta look closer at that - but it's working 
fine).

The most common problem I've seen with a Clamav upgrade is that the 
clamd socket gets its permissions mangled somewhere and MD can't 
communicate with clamd.

For RHEL4, you might be seeing an issue with SELinux.  No idea for the 
BSD system;  my *BSD experience so far has been downloading the ISO 
install images only to be unable to boot any of them.

HTH,
-kgd