Hi, > Yeah the locking up was a bit of a shock to us too :) I mean, we thought maybe > mail would crash and burn, which is relatively easy to fix, but machines > completely locking up is a bit of a rarity. The worst part was having to do > an fsck on 40 gigs of mail when it rebooted, not fun at all :) > > Our MTA is qmail 1.03, modified in places to suit our needs (which means we > can't really use any off the shelf virus checking software because the > patches no longer work with our code :) The server is also running apache to > run imp webmail, but i doubt that would be causing any problems. Binc IMAP > is running in the background as well, but thats been running with no problems > for a while now so probably isn't part of the equation either. The OS > Slackware 8.1 running kernel 2.4.18.
What are you using to decode the message? We found several emails would cause clamd to lock up when trying to parse (assertion errors would throw a SIGABRT that would lock up the threads). We ended up turning off ScanMail option, and instead use ripmime to decode the mail and scan the attachments. Works great at very high rates (over 30 messages a second). If you are interested, I can email you our qmail-antivirus we put together. It's a qmail-queue replacement that decodes the email attachments, scans them via clamd, and then calls the real qmail-queue if it's clean, otherwise's exits if it's a virus (causing qmail-smtpd to not accept the message). Email me if you are interested. Cheers, Alex -- Alex Krohn <[EMAIL PROTECTED]> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
