On Feb 18, 2005, at 3:04 AM, Fajar A. Nugraha wrote:
4.34? That's old. If I remember correctly, I had some problem with that version as well.
Use (at least) exim 4.41. That's what I use here, and it runs fine. Both Solaris 8 and 9.
Yes, the version of exim is a little behind (they rev'd through to the current number pretty fast), but I'm not convinced the issue is the MTA. My rationale here is that when my clamd gets into its unhappy state, other clients besides my MTA can't talk to it either (e.g. clamdmon, posted on this list a little while back). If other clients start to fail against the daemon, that makes me want to look hard at the daemon and why it started to fail.
I'm willing to believe that an older version of the MTA, even though it works the vast majority of the time, could find the edge condition to expose a bug (in somebody's code, I'm not pointing finger at clamav by any means). I don't want to be argumentative, but I'd really like to know where that bug is and preferably squash it without having to change my entire MTA in the hopes it will not trigger the bug. I'd be a bit nervous that whatever is leaving clamd in an unresponsive state could surface again later.
I've got to sleep now, but I will work hard tomorrow to try and rebuild clamav to bring it closer to the working configurations already mentioned here. I'm very grateful to everyone who has tried to help so far.
-- dNb
P.S. If you'd like to pass on the build details of your working setup off-list, I'd appreciate it.
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
