On Fri, 1 Jun 2007, Rob Sterenborg wrote: > > Start with your mail log, which messages are causing the problem? are > > they big, do they have certain type of attachments, etc. (all these > > attributes can be controlled with MailScanner) If you can isolate > > one sample, better, that way you'll have something to test directly. > > From what I see in the logs it times out on virtually all email. If I > let the MTA continue receiving and scanning email, it will hangup > itself. > > > Have you tested clamav? for instance running clamscan on the test > > directory that comes with the source. > > Yes I tested clamscan and it is working, I suppose clamavmodule should > be working too then. > > We also use Sohpos so, after I wrote this message I disabled ClamAV and > tried with just Sohpos: the same timeout occurred. > So I deleted and reinstalled all of ClamAV. At first it didn't timeout > but later it started again. > Next I noticed SpamAssassin also started to timeout *a lot*. > > Since we suffered a crash because of poweroutage (it's quite silly: the > UPS-es worked great and we would have survived it if it weren't for the > airco's that were not connected to an external power aggregate. A lot of > machines shutdown -some more, some less- because of heat problems) I > figure we have data corruption or something. > > So, I'm not so sure if this is ClamAV related. Maybe this doesn't belong > here... I'll continue searching.
Are you using clamscan instead of clamdscan? That could be the reason for your trouble. Both programs take a long time to start up, easily long enough to overrun a timeout. But clamdscan starts up only once, whereas clamscan starts up fresh for every new mail message. Alan Stern _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
