Philip Ross wrote:
Another change to the HAVE_POLL code in clamd/others.c has now been
checked in to CVS:
http://cvs.sourceforge.net/viewcvs.py/clamav/clamav-devel/clamd/others.c?r1=1.18&r2=1.19
I haven't yet tried this to see if this fixes the problem.
I'm now running 0.80rc
Trog wrote:
I've never used exiscan, but it sounds like a bug in exiscan (or a
configuration issue).
The issue started occurring (for several people on this list) between
0.80rc2 and 0.80rc3.
According to others, the change that broke it was
http://cvs.sourceforge.net/viewcvs.py/clamav/clamav-de
Brian Morrison wrote:
I'm using Exim 4.43, with exiscan-acl-4.43-28, and all of my incoming
mail has the added X-Scan-Signature header that Exim adds in there to
show that the scanning occurred. I have seen no indication that this is
not happening and I can find nothing in my mail or Exim logs that
Philip Ross wrote:
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):
(that should have been exiscan-acl-4.43-28 rather than 4.33-28 in the above)
I've now rebuilt my
Paul Geldart wrote:
After closer inspection of the logs I found the entry
Mon Oct 4 01:06:39 2004 -> Client disconnected
and have tracked the problem back to clamd/others.c. If I replace others.c with
the version from rc2 the problem disappears.
I've found this change in CVS
(http://cvs.sourcef
Paul Geldart wrote:
Hi, I finally tracked my problem down to a change in clamd/others.c, a line has
been added to undefine HAVE_POLL with the comment "temporarily disabled" and the
return value has been changed in the code block that can now never be called.
This appears to make clamd think th
