Paul,
On Fri, 12 Nov 2004, Paul Constable wrote:
> Tim,
> Cheers for that, it has moved it along further but still a problem
> remains..............
>
> I now get:- 'malware acl condition: clamd: unable to read from socket (No such
> file or directory)'
>
> This now presumably is whatever exim is offering to clamd, cannot be read as
> there is nothing there. What would stop exim putting mails in the 'scan'
> directory? Because that appears to be the problem at the mo.
You didn't mention what versions of Exim and exiscan you are running.
There is a problem with older versions of exiscan running against newer
versions of ClamAV; basically exiscan closes its connection to ClamAV
prematurely, and ClamAV gets upset in precisely the way you describe. IIRC
the exiscan change log documents exactly when this was fixed - yes ...
21 - Remove "shutdown socket for writing" from clamd malware
code. It seems to cause problems with the latest
clamd 0.70 release.
So an Exim/exiscan upgrade may be the way forward. (Though it may well be
trivial to patch the exiscan you have; I think it was just a case of
removing a call to 'shutdown()')
HTH,
Richard
>
> Thanks,
> Paul
>
> On Thursday 11 November 2004 22:23, Tim Jackson wrote:
> > On 11 Nov 2004, Paul Constable wrote:
> > > When running and the I get the following :- 'malware acl condition:
> > > clamd: ClamAV returned /var/spool/exim/scan/1CS0dW-0007iD-Fl: Can't
> > > access the file ERROR'
> > >
> > > This is obviously an ownership/rights problem, but having changed each
> > > for the other's owner to no avail. Where do I go from here ????????????
> >
> > If you haven't already, put the clamav user in the "exim" group and enable
> > the AllowSupplementaryGroups option in clamd.conf.
> >
> > Tim
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
