[Apologies if this is a common question, but I've gone through the list archives and searched for FAQ answer with no luck. This is a common question on both the procmail and spamassassin lists, and I don't want to give out bad information on such an important topic.]

Tomasz Kojm wrote:

ScanMail is optional and must be enabled manually.


I have run into some problems calling clamscan/clamdscan from procmail. It *seemed* to be working well in my initial testing (debian linux), but another user (bsd) got very different and disturbing results.

In my searching, I have seen postings indicating that clamscan/clamdscan works most reliably when used to scan files on disk, and that the --mbox function is NOT reliable at present. Is that the case? I've found scripts that unpack MIME-encoded messages, then call clamdscan to scan the extracted files. Is that considered the best approach? Is calling clamdscan to scan stdin reliable?

If it's useful, I can summarize my testing results. Otherwise, I suspect it's old news.

Thanks!

- Bob


------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to