2.7.0: bypass clamd scanning when daemon did not respond

Michael Scheidell michael.scheidell at secnap.com
Tue Oct 25 01:59:50 CEST 2011

On 10/24/11 1:21 PM, Mark Martinec wrote:
> Adding the
>    ['always-clean', sub {0}],
> to @av_scanners or to @av_scanners_backup list should suffice to accomplish
> what you ask for.  If it doesn't, it would be worth investigating the full
> log.  Note that the message "(!)connect to ... failed" would still be logged
> regardless.
>    Mark
and, just for the record, so google keeps it.. DON'T USE THE CLI VERSION 
it takes FOREVER for the cli version to load.

don't believe me?

try it.

get a world readable file (1k will do)

type 'time clamdscan {filename}'

then type 'time clamscan {filename}'

if you use clamscan as your backup, your cpu will peg with just 3 or for 
processes, and amavisd will timeout anyway.

Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
 >*| *SECNAP Network Security Corporation

    * Best Mobile Solutions Product of 2011
    * Best Intrusion Prevention Product
    * Hot Company Finalist 2011
    * Best Email Security Product
    * Certified SNORT Integrator

This email has been scanned and certified safe by SpammerTrap(r). 
For Information please see http://www.spammertrap.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.amavis.org/pipermail/amavis-users/attachments/20111024/4a97f98d/attachment.html>

More information about the amavis-users mailing list