ClamAV only scanning message headers
mailscanner_list at phisch.ca
Thu Oct 15 17:48:31 IST 2009
Thanks. I have reviewed the performance tips for MailScanner, and our
system is extremely well optimized. We can easily push 500K messages/day
through Mailscanner/Spamassassin, in addition to the several million
that we drop at the MTA with DNSBLs.
The problem is that clamdscan does get properly called from
/opt/MailScanner/lib/clamav-wrapper (actually, a slightly modified
version of it to call calmdscan rather than clamscan). The problem is
that only the message headers make it into my '
Incoming Work Dir’, which is set to /tmp.
Here's what clamd writes out in its log, which shows that only headers
are being scanned
+++ Started at Thu Oct 15 11:15:29 2009
clamd daemon 0.95.2 (OS: solaris2.8, ARCH: sparc, CPU: sparc)
Log file size limited to 2097152 bytes.
Reading databases from /var/opt/csw/clamav/db
Not loading PUA signatures.
Loaded 1174218 signatures.
LOCAL: Unix socket file /tmp/clamd.socket
LOCAL: Setting connection queue length to 15
Limits: Global size limit set to 104857600 bytes.
Limits: File size limit set to 26214400 bytes.
Limits: Recursion level limit set to 16.
Limits: Files limit set to 10000.
Archive support enabled.
Algorithmic detection enabled.
Portable Executable support enabled.
ELF support enabled.
Mail files support enabled.
OLE2 support enabled.
PDF support enabled.
HTML support enabled.
Self checking every 600 seconds.
<etc, etc, etc>
What would cause only the headers to be extracted? Is there any way
to debug MS to figure out what's going wrong with the interaction with
Spamassassin has no troubles at all, by the way.
Any help and/or guidance is greatly appreciated.
SunOS <snip> sun4v sparc SUNW,SPARC-Enterprise-T5220
This is Perl version 5.008008 (5.8.8)
This is MailScanner version 4.56.8
Module versions are:
Optional module versions are:
Scott Silva wrote:
> on 9-29-2009 1:23 PM Jared spake the following:
>> Greetings, MailScanner community,
>> I have been using MailScanner with Postfix and ClamAV for several years
>> now and it has been an extremely effective system for combating spam and
>> malware for my users. I have just refreshed our system to bring the
>> relevant software up to a reasonable rev as well as putting it on much
>> more capable hardware.
>> Everything seems to be working with the exception of my virus scanning.
>> Here’s the situation:
>> My ‘Incoming Work Dir’ is set to /tmp (as it’s in RAM rather than on
>> disk for speed). As mail comes in, I can see that a MailScanner child
>> creates a subdirectory of /tmp with its PID, and then calls the ClamAV
>> wrapper to scan that directory. My expectation is that MailScanner
>> decodes all MIME parts and decodes Base64 for the AV engine to troll and
>> will leave them in that temporary directory.
>> The problem is that the only file being written out into those
>> directories is the message header – no other MIME parts (or even a
>> plain-text part, for that matter) ever make it into the directory. As a
>> result, ClamAV is unable to detect infections because it will never see
>> I have confirmed that ClamAV is able to detect viruses (by using an
>> EICAR test file) when run from the command line and/or the MailScanner
>> wrapper script, and that Clam is only being “fed” files like
>> Is there something that I’m missing in my install? Do I have a
>> fundamental misunderstanding of how MailScanner interacts with ClamAV
>> via the wrapper? I have tried running MailScanner in debug mode, but
>> there’s really no useful information in there.
>> Any guidance would be very much appreciated!
> Read http://wiki.mailscanner.info/doku.php?id=maq:index#optimization_tips
> and maybe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MailScanner