Today I noticed our gateway mailserver running particularly slow -
Investigating further revealed it had a load of 100+!
The culprit was clamscan: One of our clients had sent 500+ e-mails with
a 5Mb zip attachment, with each zip containing a compressed tif image
that was 50Mb+.
Is there anyway to place a limit on the size qmail-scanner will scan
(post uncompressing?) - We have a 10Mb
(/var/qmail/control/databytes)limit in place, but a user can achieve
substantial compression on image files, consequently giving them the
ability to send files that are well over 50Mb.
Or enforce some type of resource limitation on clamscan? (We are running
Debian)
I read the clamdscan performs better than clamscan - but replacing
clamscan with clamdscan in qmail-scanner.pl produces:
451 qq Temporary problem
error_condition: X-Qmail-Scanner-1.20: clamscan: corrupt or unknown
ClamAV scanner error or memory/resourc
e/perms problem - exit status 2
Regardless of how high I raise the softlimit in my run script:
QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl"
export QMAILQUEUE
exec /usr/local/bin/softlimit -m 35000000 \
/usr/local/bin/tcpserver -v -H -R -l 0 \
...
Basically our current setup can be DOS'd quite trivially!
Clam Ver: clamav-0.67-1
Any suggestions are appreciated.
Regards,
MB
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
