Package: clamav-milter
Version: 0.88.4-2
Severity: wishlist

I am using your clamav-milter package with Postfix 2.3 from Debian Etch. 
Postfix introduced Milter support with the 2.3 series
(see http://www.postfix.org/MILTER_README.html). 

I needed to change /etc/default/clamav-milter so that the Unix domain socket 
file is written do a different location, since 
the Postfix smtpd in Debian is running chroot'ed:

SOCKET=local:/var/spool/postfix/.../clamav-milter.sock

It would be good if this is indicated somewhere in the README file.

I also needed to change /etc/init.d/clamav-milter, so that the permissions of 
the created socket file are modified after startup.
Otherwise, the Postfix smtpd daemon has not the right permissions to read it. 
It would be good if there is a (described) solution 
which does not demand change of package executables. 

One idea might be to make the socket file group-readable / writeable on 
creation, which would allow to add the postfix user to the 
according group.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages clamav-milter depends on:
ii  clamav-base                  0.88.4-2    base package for clamav, an anti-v
ii  clamav-freshclam [clamav-dat 0.88.4-2    downloads clamav virus databases f
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libclamav1                   0.88.4-2    virus scanner library
ii  libmilter0                   8.13.8-2    Sendmail Mail Filter API (Milter)
ii  libwrap0                     7.6.dbs-11  Wietse Venema's TCP wrappers libra
ii  lsb-base                     3.1-15      Linux Standard Base 3.1 init scrip

Versions of packages clamav-milter recommends:
pn  clamav-daemon                 <none>     (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to