On Fri, 18 Jun 2004 at 15:08:32 -0700, Michael D. Crawford wrote: > I've been using formail, procmail and clamav to > disinect a 200 MB mailbox, and since last night it's > only processed 80 MB of mail so far. It's a 350 Mhz
That's a very slow progress! I suspect you use clamscan. So clamscan is called to scan every single message (a maildir file), the database is loaded into memory and so on. It's not a optimum way of using ClamAV. To scan all these messages quicker you can use 2 approaches: 1) transform all the mailbox into maildir and _after then_ run clamscan one time against all the maildir (not one time for every message), or 2) scan messages "in the fly" (while converting) - scan them with clamdscan (not clamscan). In this method a user running clamd must have access to the scanned maildir of course (the user calling clamdscan doesn't matter). Be sure to have ScanMail enabled in clamav.conf. > box that I'm running it on, and clamav must be pretty > CPU intensive. [...] -- Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only [EMAIL PROTECTED] http://www.lodz.tpsa.pl/iso/ | ones and zeros. [EMAIL PROTECTED] http://www.ClamAV.net/ A GPL virus scanner ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
