Package: clamav-milter Version: 0.96.1+dfsg-1 Severity: normal The README.Debian says: POSTFIX
Recent versions of postfix have support for milters. This allows clamav-milter to be used reasonably well with postfix, although the problem of group permissions on the actual socket is a problem. See /usr/share/doc/clamav-milter/INSTALL.gz for some details. A solution for the frequent "I have to change the init script to make sure postfix can communicate with the socket" problem is making the directory for the socket setgid. So: uncomment "USE_POSTFIX=yes" in /etc/default/clamav-milter and choose the appropriate socket option. mkdir -p /var/spool/postfix/clamav/ chown clamav:postfix /var/spool/postfix/clamav/ chmod g+s /var/spool/postfix/clamav/ ls -l /var/spool/postfix/clamav/ srwxrwxr-x 1 clamav postfix 0 2006-12-15 03:37 clamav-milter Another option is to use a TCP socket for milter <-> postfix communication. For this option, you can use the syntax: SOCKET=inet:[email protected] (p...@host, in case it's not clear) in /etc/default/clamav-milter. This has the disadvantage that you lose filesystem permission-based protections on the socket, so use with some caution. All of this is wrong... USE_POSTFIX is without effect and SOCKET is the same. The configuration is all dealt with clamav-milter.conf which is itself generated with debconf. Please review that file and update it to match the current situation. Wrong documentation is very misleading for end-users, in particular when README.Debian is the one that should always be right because the package maintainers know what he did. :-) Cheers, -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
