[EMAIL PROTECTED] said: > I can also not say I understand why ClamAV would hang on STREAM, and not on > SCAN
Your STREAM problem may be different of course. The messages that gave our clamd a hard time would do exactly the same for clamscan ( "of course" ). I just wanted you to check that you weren't suffering from the same problem that we were, especially as it was relatively easy to use a recent snapshot tar-ball to avoid the problem. [EMAIL PROTECTED] said: > I cannot say this makes me happy We have to find a way to be vigilant and happy at the same time. :-) Steve PS I'm very happy with what ClamAV has done for us, even in my fumbling fists. However, it seems to me that there will always be dangers in running "potentially recursive" checks in real time on incoming mail. I turned off the ScanMail option to avoid future recurrences but am aware this may be letting some viruses in (eg in bounce messages). I am still not convinced that I understand what happened in our Solaris-based, Exim/exiscan+clamd setup in the minutes/hours after the first dodgy email arrived. In the end, exim quit and we had no mail system. Shortly before that we had a clamd process with many threads, only one of which was doing anything. Calls to clamd were stacking up correctly but none were being processed (it seemed). I don't understand why that happens. _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
