Sorry if this is an old subject, but it keeps coming up again and again on the procmail and spamassassin lists. I have tried searching archives and the web for answers.
I noticed that there can be differences in results returned by clamscan and clamdscan when called directly from procmail to scan stdin, and noted the cautions about --mbox on the clamscan manpage. I'm making use of some of the wrapper scripts that unencode the message to files, then scan those. This is working VERY WELL, and I'm thrilled with clamav.
What I'd like to get is as close to an official answer as possible to the questions of:
1. Is --mbox recommended for use for scanning mail streams (i.e. from procmail)? Is the fixed, or to be fixed shortly?
2. Is the lack of --mbox on clamdscan permanent? IF --mbox is OK, will it remain only for clamscan.
There is a 'ScanMail' option in clamav.conf, which I think is the same as --mbox for clamscan.
3. Is a wrapper script to un-encode email 1st, then scan the resulting files a good / the best approach?
Thanks,
- Bob
-- Ryan Moore ---------- Perigee.net Corporation 704-849-8355 (sales) 704-849-8017 (tech) www.perigee.net
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
