------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=926
--- Comment #4 from J R Binks <jethro.binks@???> 2009-12-11 21:43:32 ---
I hadn't realised that av_scanner was expanded at runtime, so thanks
for the hint about that. I used that fact, and a modification to the
technique described at:
http://lists.exim.org/lurker/message/20070918.172526.ff9818ec.en.html
to allow a fallback clamd server as described below.
I had previously been communicating over TCP to a clamd process on the
same host, either via 127.0.0.1 or the real host address. However, I did
not make use of the undocumented "local" feature described above.
I now default to talking to a local Unix socket instead by
specifying /var/run/clamav/clamd.sock, and as a fallback, use TCP to
talk to a clamd running on a remote host. I did not test the "local"
option to force using SCAN to a locally-running clamd. (Maybe someone
who knows about these things would be able to comment on whether it is
more or less efficient to use a Unix socket vs. a TCP/IP socket on
the same host.)
The follow-up post to this bug on exim-dev from Jeremy Harris:
http://lists.exim.org/lurker/message/20091206.140200.f8e840e1.en.html
referencing his previous:
http://lists.exim.org/lurker/message/20070107.160455.b6eea57a.en.html
are also relevant. I have reviewed his patch, and it makes sense to me. If
the "local" option is specified, then do nothing in particular (as this
is part of the "if network socket use STREAM else unix socket prepare socket")
allowing a fall-through to the plain "SCAN" that follows the if condition
(and used with the unix socket).
Phil, I agree with your comment about no requirement to maintain the
old interface. clamd 0.95 came out earlier this year, so assuming this
interface gets changed soon, it will be more than a year since the new
API was introduced, and yes sites should be keeping their clamd fairly
up-to-date.
This message:
http://archive.netbsd.se/?ml=clamav-users&a=2009-06&t=10952709
suggests that STREAM may disappear in the middle of next 2010. That
will be a concern for sites that keep clamd up-to-date, but do not update
Exim. It may be worth notifying the clamd people that when the time comes
for STREAM to go away, they make mention of the minimum version of Exim
that will be required to work with the new API. Exim should do likewise.
This suggests that the new API should be introduced sooner rather
than later so it gets into a release of Exim before the summer.
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
