> So does that mean you no longer use Exiscan's "demime" facility, because, > if I understand this correctly, it is sufficient to pass the mime parts > to clamd for scanning. Using it and ScanMail would appear to bring some > "competition" between Exiscan's demime and ClamAV's ScanMail. > > Could someone clarify this point?
I'd appreciate similar clarification... I'd heard on the list of people having problems with clamd / clamdscan and the various mail scanning options (can't remember if the problems were related). For now (running courier on freebsd) I invoke an external mime unpacker, and then run clamscan on the unpacked message parts. I know clamscan is less efficient, but I keep hearing people commenting about run away memory use etc, and haven't followed it all in enough detail to know if it's still a problem? (currently the extra cpu cyles are less "costly" than the downtime caused by run away ram or processor use...) Can someone in similar config (courier and freebsd) confirm that they are no longer having (or never have had) stability issues with clamd / clamdscan and what changes I make to clam config to properly scan a single mime encoded message (not an entire mbox). As a small measure of comfort it would also be nice to know how heavily loaded your machines are (i.e. small corporate network or ISP/ enterprise class) Thanks a bunch! m/ ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
