Hi there, On Sun, 7 Mar 2010 Steve Holdoway wrote:
> ... I have a remote clamd that my mail server uses ... Er, you mean you want it to use? :( I've never used a remote clamd so I can't speak from experience here, but I believe that others have done so successfully. By which I just mean that I think it will work if it's set up correctly. :) I take it that in clamav-milter.conf on the mail server you tell clamav-milter where to find the clamd socket using the directive "MilterSocket inet:3...@clamd_host_or_ip" and in clamd.conf on the clamd server you tell clamd to listen on the correct socket using the directive "TCPSocket 3310"? I had a little difficulty with your use of the word 'server', as there seem to be two of them, but I think I understand the architecture that you're trying to set up. In a case like this I think I'd first make sure that I could get it all to work with the clamd daemon running on the same machine as the MTA (if necessary, first using Unix sockets, then using TCP sockets), and then simply move the daemon to the remote machine and change the configuration to reflect that. If it works when the daemon is on the same machine but not when it's on the remote machine at least you will have narrowed down the problem to one of network communications. You haven't been very clear about your use of iptables but I think I'd also take that out of the equation to start with, so that there are fewer things to go wrong all at once. Finally when things are failing, have you checked the arp and routing tables on the two machines are as expected? -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
