$ rpm -qa | grep clamav clamav-data-0.97.8-1.fc18.noarch clamav-milter-systemd-0.97.8-1.fc18.noarch clamav-update-0.97.8-1.fc18.i686 clamav-server-sysvinit-0.97.8-1.fc18.noarch clamav-lib-0.97.8-1.fc18.i686 clamav-filesystem-0.97.8-1.fc18.noarch clamav-milter-0.97.8-1.fc18.i686 clamav-0.97.8-1.fc18.i686 clamav-server-0.97.8-1.fc18.i686
So this morning I did some more experimenting. I increased the postfix milter timeouts, which did not help, but was probably wise to do anyway. Then I switched from a named socket to a socket on localhost - actually the hostname localhost didn't work. I had to change it to 127.0.0.1: -ClamdSocket unix:/var/run/clamd.milter/clamd.sock +#ClamdSocket unix:/var/run/clamd.milter/clamd.sock +ClamdSocket tcp:127.0.0.1:3311 And.... ## # TCP port address. # Default: no -#TCPSocket 3310 +TCPSocket 3311 # TCP address. # By default we bind to INADDR_ANY, probably not wise. # Enable the following to provide some degree of protection # from the outside world. # Default: no -#TCPAddr 127.0.0.1 +TCPAddr 127.0.0.1 # Maximum length the queue of pending connections may grow to. # Default: 15 So it appears to be working again .... very strange. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
