Am 17.05.2017 um 17:40 schrieb Kishore Pawar:
Hi Reindl Harald
I am not sure what is wrong with this upgrade/installation. But, here's the
configuration I was using previously and is being used currently
impressing that you talk to me but quote some other stuff
i responded to "where I see that the clam-miller.socket is owned by
clamav:clamav, where as my latest one is owned by clamav:root. Is it
causing the below error? If so how can I make sure the socket gets
proper permissions?" and while it's likely not the problem becaus ethe
milter is talking to clamd and not the other way when you look at my
milter conf it should be *pretty clear* how to "make sure the socket gets
proper permissions"
_____________________________________
$ cat /usr/local/etc/clamav-milter.conf | grep -v "#"
MilterSocket /var/run/clamav/clamav-milter.socket
User clamav
PidFile /var/run/clamav/clamav-milter.pid
ClamdSocket unix:/var/run/clamav/clamd.socket
Whitelist /usr/local/etc/clamav-milter.whitelisted_addresses
LogFile /var/log/clamav/clamav-milter.log
LogTime yes
LogSyslog yes
_____________________________________
/etc/mail/clamav-milter.conf
# usermod -a -G clamilt postfix
# usermod -a -G sa-milt postfix
User clamilt
AllowSupplementaryGroups yes
MilterSocket /run/clamav-milter/clamav-milter.socket
MilterSocketMode 0660
ClamdSocket unix:/run/clamd/clamd.sock
FixStaleSocket yes
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
