Carl Thompson wrote:
> I believe the problem is a hard code issue. The setting --server
> isn't telling clamav-milter to listen on a specified IP for
> connections its telling clamav-milter to connect to clamd on the
> specified IP thus making the INSTALL documentation in error (unless
> i'm seriously confused)
>
> Sendmail must connect to clamav-milter not clamd directly but
> clamav-milter will not listen on a TCP port it will only connect to
> clamd on a TCP port.
>
> Carl
OH...
You're correct, clamav-milter won't listen on a TCP port, only on a local
socket. This is a limitation of clamav-milter.
You could probably write a simple daemon to listen on a TCP port and then relay
all commands it hears to the socket, and all responses back to the TCP port.
But why? Why not have sendmail and clamav-milter on one machine, and tell
clamav-milter to communicate with clamd on the other machine?
Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -e"map{y/a-z/l-za-k/;print}shift" "Jjhi pcdiwtg Ptga wprztg,"
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
