X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=debian%2FREADME.Debian;h=34f9962fe0a069252fc979f32018444f18122df7;hb=bef116225aaf81fc42373a387d73e78eb5b6c3fb;hp=65b6a5dc3bb8711f08f481d0448c3f2c452a4a18;hpb=dda36a45dbf765a015fb962c4f03ee3cbc010229;p=deb_pkgs%2Fspamass-milter.git diff --git a/debian/README.Debian b/debian/README.Debian index 65b6a5d..34f9962 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -37,6 +37,13 @@ See http://www.sendmail.com/partner/resources/development/milter_api/installatio and http://www.sendmail.org/m4/adding_mailfilters.html#INPUT_MAIL_FILTER for more information on milters. +If you are using the alias expansion method, -x, you will need to add +spamass-milter to the smmsp group using: + + adduser spamass-milter smmsp; + +This does not need to be done unless you are using alias expansion. + -------------------------------------------------------------- Integrating spamass-milter into your postfix installation -------------------------------------------------------------- @@ -47,14 +54,25 @@ 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 + # milter macros useful for spamass-milter + milter_connect_macros = j {daemon_name} v {if_name} _ + milter_data_macros = j i {auth_type} {daemon_name} v {if_name} _ + milter_rcpt_macros = j {auth_type} {daemon_name} v {if_name} _ + +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/spamass-milter should be required. +[However, if you are not doing so, see below.] ------------------------------------------------------------- Adjusting how spamass-milter is started @@ -62,7 +80,31 @@ 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. + +If you want to use an inet socket for spamass-milter (like inet:9999 +or inet:9999@127.0.0.1), then you'll need to make the following +configuration changes in /etc/default/spamass-milter: + +SOCKET="inet:9999@127.0.0.1" +SOCKETMODE="" +SOCKETOWNER="" ------------------------------------------------------------- Debugging spamass-milter @@ -93,4 +135,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, 10 May 2018 11:15:25 -0700