* J4 <ju...@klunky.co.uk>:
> > I'm on Debian Squeeze.
> Right folks! I did all of this:
>
> # spamass-milter -m -u nobody -f -p /var/run/spamass.sock
> # chown postfix.postfix /var/run/spamass.sock
> # spamass-milter -m -u nobody -f -p /var/spool/postfix/var/run/spamass.sock
> # chown postfix.postfix /var/spool/postfix/var/run/spamass.sock
> # ls -l /var/spool/postfix/var/run/spamass.sock
> srwxr-x--- 1 postfix postfix 0 Jan 18 20:13
> /var/spool/postfix/var/run/spamass.sock
> 2 sockets are used above because someone else (thanks Google) wrote that
Even a search engine as powerful as Google should not keep one from
questioning what it returns.
> that postfix chroots. Also, I added the above into an init.d script to
I can't see why someone would need two sockets for that. You place one socket
into the Postfix chroot. This is where Postfix connects.
Please edit /etc/default/spamass-milter and make the config this:
OPTIONS="-u spamass-milter -r 6"
SOCKET="/var/spool/postfix/spamass/spamass.sock"
SOCKETOWNER="postfix:postfix"
SOCKETMODE="0660"
You might want to modify "-r 6" to set a different REJECT threshold
later.
The restart the milter and verify it has created the socket and set
permissions and ownership correctly.
> be run at a reboot as the sockets might get lost.
>
> Added this into /etc/postfix/main.cf:-
> ### spamassassin-milter
> milter_default_action = accept # accept is for testing
I disagree. accept is bad for testing because you won't notice if your milter
fails. The default setting "tempfail" is better. If something goes wrong you
will notice immediately.
Modify /etc/postfix/main.cf like this:
milter_default_action = tempfail
smtpd_milters = unix:/spamass/spamass.sock
p@rick
--
state of mind
Digitale Kommunikation
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht München Partnerschaftsregister PR 563
