16/3/2004 Released unstable version 4.29.1-1. Fix for passing archives through properly when allowing all password-protected archives. Minor speed-ups. Expect to see "defunct" processes appear with this version, it is quite normal.
#!/bin/sh
killall MailScanner
sleep 8
/usr/mailscanner/bin/check_mailscanner
How did you send the eicar test - was it in a normal text email, or was it in an html email or was the eicar string in an attached text file?I send Eicar test and I receive email with in-line warning and warning attachment... and I receive two alerts, one in sender email, and other one in destination email.
I'm managing MailScanner on many servers and have never had a problem with high CPU usage despite high mail loads. It's generally a matter of configuring it correctly and making sure you use ClamAV appropriately.high cpu usage
With a PIV 2.4Ghz, 1GB Ram and 20-30k mails a day mailscanner kills the box. You are probably one of those lucky ones who is not facing this problem. Whereever i have seen i have seen mailscanner heavy on the cpu. Anyways its good to know atleast for someone it works properly.Originally posted by chirpy
I'm managing MailScanner on many servers and have never had a problem with high CPU usage despite high mail loads. It's generally a matter of configuring it correctly and making sure you use ClamAV appropriately.
I've had it running on 2 RaQ4's (350Mhz CPU's with 128MB RAM) with no problems.
But, as you say, if your server is somewhat overloaded to start with, you may well experience issues and there are , of course, other solutions. I do think, however, that you'll find it hard to beat MailScanner for its feature set and simple configurability and scalability.