From 0dd84c497b7ea9253bd1ff7f82bc328bbbf001bc Mon Sep 17 00:00:00 2001 From: don Date: Thu, 21 Aug 2008 23:40:05 +0000 Subject: [PATCH] * NOT RELEASED YET * Update the documentation in README.Debian to indicate that a different path to the postfix socket may be required in chrooted postfix installs (closes: #496003) --- debian/README.Debian | 35 +++++++++++++++++++++++++++++------ debian/changelog | 9 +++++++++ 2 files changed, 38 insertions(+), 6 deletions(-) diff --git a/debian/README.Debian b/debian/README.Debian index 65b6a5d..c141cd8 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -47,14 +47,21 @@ that postfix connects to the spamass-milter socket. Something like: # spamass-milter configuration smtpd_milters = unix:/var/spool/postfix/spamass/spamass.sock -should work. See http://www.postfix.org/MILTER_README.html or +should work. Note, however, if you're using a chrooted version of +postfix, you'll need the local path to the socket inside of the +chroot. In recent versions of Debian the following should work: + + # spamass-milter configuration + smtpd_milters = unix:/spamass/spamass.sock + +See http://www.postfix.org/MILTER_README.html or /usr/share/doc/postfix/MILTER_README.gz (in postfix-doc) for information on how to set tempfail and the various timeouts that the sendmail configuration above uses. -You'll also want to change /etc/default/spamass-milter to use the -SOCKET above, and also enable RUNAS so that it runs as the same user -that will be connecting to the socket. +The defaults for spamass-milter adjust themselves so that no +configuration in /etc/default/milter should be required. [However, if +you are not doing so, see below.] ------------------------------------------------------------- Adjusting how spamass-milter is started @@ -62,7 +69,23 @@ that will be connecting to the socket. You can adjust how spamass-milter starts, and the options it calls spamc with by adjusting /etc/default/spamass-milter. OPTIONS is passed -directly to spamass-milter by /etc/init.d/spamass-milter. +directly to spamass-milter by /etc/init.d/spamass-milter. [Refer to +spamass-milter(1) for details.] + +Other settings which may be of use: + +SOCKET sets the location of the socket; defaults to +/var/run/spamass/spamass.sock unless you are running postfix, where it +is set to /var/spool/postfix/spamass/spamass.sock. + +SOCKETOWNER is the owner of the socket, which defaults to root:root or +postfix:postfix if you're running postfix. + +SOCKETMODE is the mode of the socket, which defaults to 0600 or 0660 +if you're running postfix. + +RUNAS controls the user which spamass-milter runs as; defaults to +spamass-milter. ------------------------------------------------------------- Debugging spamass-milter @@ -93,4 +116,4 @@ q and send the results along with your bug report using reportbug. - -- Don Armstrong , Tue, 2 Jan 2007 08:22:46 -0800 + -- Don Armstrong , Thu, 21 Aug 2008 16:52:22 -0700 diff --git a/debian/changelog b/debian/changelog index 8147ea8..1a2b935 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +spamass-milter (0.3.1-8) UNRELEASED; urgency=low + + * NOT RELEASED YET + * Update the documentation in README.Debian to indicate that a different + path to the postfix socket may be required in chrooted postfix + installs (closes: #496003) + + -- Don Armstrong Thu, 21 Aug 2008 16:54:35 -0700 + spamass-milter (0.3.1-7) unstable; urgency=low * Add LSB options to init script (closes: #467145) -- 2.39.2