[Mimedefang] Problem running clamd but not clamscan

[Roedel, Mark]

Has clamd been restarted (or otherwise forced to reload its
configuration) since your signatures were last updated?


--
Mark Roedel
Web Programmer / Analyst
LeTourneau University
 

-----Original Message-----
From: mimedefang-bounces at lists.roaringpenguin.com
[mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of Scott
Harris
Sent: Wednesday, January 28, 2004 10:01 AM
To: mimedefang at lists.roaringpenguin.com
Subject: [Mimedefang] Problem running clamd but not clamscan

I've been debugging why I've not been catching the 
new worm going around for the last day.  This morning 
I finally received a new message that passed through 
my new configuration and was finally caught.  What I 
had to do in order to get it to scan is alter 
mimedefang-filter and change the order of the calls to:

    return message_contains_virus_clamav()   if
($Features{'Virus:CLAMAV'});
    return message_contains_virus_clamd()    if
($Features{'Virus:CLAMD'});

After swapping the first two tests to appear as they 
do now above, the very first virus with the myDoom 
signature was caught.  Why isn't clamd catching this?  
Clamd was able to catch other virii if I send tests 
from www.testvirus.org.