On Tue, 19 Oct 2004 10:23:04 +0200 in [EMAIL PROTECTED] "Graham Dodd" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] <> wrote: > > On Tue, 19 Oct 2004 15:03:13 +0700 "Fajar A. Nugraha" wrote: > > > > [ ... ] > > > >> exim 4.24 (the exiscan patch of it, to be exact) seems to have that > >> problem. Use exim 4.41 instead. > > > > Or use the newest exim-4.43/exiscan-acl-4.43-28 combination. Works > > great with ClamAV 0.80. > > > > --Frank Elsner > > > > Upgrading Exim is not an option at the moment so I guess I'll switch > back to 0.75.1 I think the patch needed is as shown below, from a previous posting to the list: I've just compared the clamd code between exiscan-acl-4.33-20 and exiscan-acl-4.33-28 and found the following (which looks like it could be the cause of the problem): --- exiclam.old 2004-10-13 21:04:43.036454125 +0100 +++ exiclam.new 2004-10-13 21:04:08.433816809 +0100 @@ -87,8 +87,14 @@ + return DEFER; + } + -+ /* we're done sending, close socket for writing */ -+ shutdown(sock, SHUT_WR); ++ /* ++ We're done sending, close socket for writing. ++ ++ One user reported that clamd 0.70 does not like this any more ... ++ ++ */ ++ ++ /* shutdown(sock, SHUT_WR); */ + + /* Read the result */ + memset(av_buffer, 0, sizeof(av_buffer)); It may be possible to patch your existing Exim with this simple change. -- Brian Morrison bdm at fenrir dot org dot uk GnuPG key ID DE32E5C5 - http://wwwkeys.uk.pgp.net/pgpnet/wwwkeys.html _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
