Hi all,

I'm running postfix-2.3.3 with clamav-milter-0.95.3 (and therefore
clamd-0.95.3). Postfix is running as user "postfix". OS is RHEL5,
x86_64.

When I start clamd, it creates clamd.sock like so:
$ ls -l /var/run/clamav/clamd.sock 
srwxrwxrwx 1 clamav clamav 0 Dec 29 16:02 /var/run/clamav/clamd.sock

When I start clamav-milter, it creates clmilter.socket like so:
$ ls -l /var/clamav/clmilter.socket
srwxr-xr-x 1 clamav clamav 0 Dec 29 16:02 /var/clamav/clmilter.socket

Because of the mode 755, postfix cannot write to clamav-milter's
socket, so I have to manually 'chmod 755 /var/clamav/clmilter.socket' in
order to make virus checking work. Unless somebody tells me otherwise,
I am sure the modes are the default, at least for my distribution.

I could certainly modify the init script to make the chmod automatic,
but is there a better way people are setting this up, perhaps w/o
world-writable sockets, or configuration done in the conf file rather
than the initscript (I haven't been able to find docs on
clamav-milter.conf other than the included example file)?

Thanks much,
-- 
Noah Sheppard
Assistant Computer Resource Manager
Taylor University CSE Department
nshep...@cse.taylor.edu

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to