[Mimedefang] Debug

[Jonathan Maliepaard]

Hi

I run a small ISP and we process around 50 000 attempted deliveries a
day. I purpose built a SPAM server running, Mimedefang, Spamassassin and
McAfee UVSCAN v4.14.0 as per the read-me's.  It has been running very
well for 8 months, although stressing sometimes and deferring delivery. 

Those interested can see my graphs here....sorry for the speed I'm at
the bottom of Africa!
http://ns1.enetworks.co.za/spam

So....I decided to splash out and have a very nice dual Xeon 3Ghz toy
with 2GB of ram in the process of being built up. I decided to move raid
from software to hardware to save CPU and have done the big move to
Spamassassin 3.02 using MySQL to process the Bayes DB.

As I am running Redhat ES3.0 I decided that I wanted as much as possible
to be via RPM and have rolled most of my own. This I did with the
thought of easing upgrades in the future.

The new system seems stable and is running in a test environment, though
I am almost sure that no virus scanner is not being used. (I run
File::Scan and McAfee)

Sorry for the long pre-amble......my question is this, is there I way
that I can put Mimedefang (2.5.1) into a debug state so that I can see
what it is using and what not, especially the Virus scanner? I
troubleshoot SA this way using the debug flag.

I have noticed that in the mimedefang.pl file that the remark is that
the first scanner available is used. Does this mean File::Scan or
Mcafee. Can I use both? We already push mail though a second server
running CLAM but it would be cool to have a third scanner too.

I did rebuild the RPM once I noticed that the virus scanner was turned
off in the SPEC file. And when I check the compile, Mimedefang sees and
initialises both File::Scan and NAI.

Can anyone shed some light here for me?

As a comment to all the CLAM posts over the last couple of days, we have
been running clam on a second relay server since 0.67 and it is
brilliant. If you run Redhat, move to the RPM's upgrading is dead
simple. Though be careful that you change to the RPM standard for
directories etc  once you install the RPM the first time, from then on
it is a walk in the park and causes minimal disruption. (Just my 5c
worth)

Thanks

Jon.