>> 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.
Long enough for a timeout of 600 seconds = 10 minutes??? That would be a real problem.. However from what I see when starting clamd I can't second that. > But clamdscan starts up only once, whereas clamscan starts up fresh > for every new mail message. Yes I'm aware of that. But.. clamdscan was as "slow" as clamscan as clamavmodule. All timed out. In reality, the word was not "slow" but clam[d]scan became "disfunctional" after a short time. As said, I also saw Sophos and SpamAssassin timeout from whithin MailScanner which made it look even more like file corruption on disk or something. Since I *had* to make this work again, I installed both clamav and spamassassin from source instead of using apt-get and this time it worked (using clamdscan). I don't understand why it wasn't working when I *completely* (personally checked) remove the package (using apt-get and dpkg) and reinstall it, but I'm not going to complain: this was my excuse to install the latest version from source. Thanks, Rob _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
