Package: clamav-milter
Version: 0.91.2-3
These issues were originally reported under Ubuntu here:
https://bugs.launchpad.net/bugs/151850
I've noted several problems running the clamav-milter installation with the
default chrooted postfix package.
- The postfix default given in /etc/defaults/clamav-milter is a directory
name rather than a socket file name:
#SOCKET=local:/var/spool/postfix/clamav/
- The clamav-milter daemon does not have permission to create a socket file
under the postfix chroot. I fix this by using the socket path given above,
then manually creating the 'clamav' sub-directory on the first run, and
giving it the same permissions as the socket file (clamav/postfix, 775).
This could be automated by the init script.
- There is a race condition in the init script that prevents the chmod g+w
from being applied on startup. The socket file isn't created immediately by
clamav-milter, so the chmod tends to fail silently.
- The clamav-milter creates the socket file writable by clamav. You need to
chgrp the socket to 'postfix' (the postfix group) prior to doing the chmod
g+w, or the postfix daemon won't be able to write to it.
I personally solve the latter two problems by doing the following with the
current init script. It's rather crude, but it does work:
if [ $ret = 0 ] && [ "$USE_POSTFIX" = 'yes' ]; then
while [ ! -e "$SOCKET_PATH" ]; do
sleep 2
done
chgrp postfix $SOCKET_PATH
chmod g+w $SOCKET_PATH
fi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
