Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Zach Sadecki
Thanks, Don. It works pretty good now. But... restart in the init script doesn't work properly. it still has the old code in it. Which also leads to a question I had when I first peeked at it to debug the socket problem, why not just call $0 stop and $0 start, instead of having repeated co

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Don Armstrong
On Fri, 13 Oct 2006, Zach Sadecki wrote: > hmm... now I'm confused. The latest .deb on your site doesn't have > any /usr/sbin/posfix (or /usr/sbin/postfix) reference in the init > script... Hrm... well, the version there now should have it. [It's possible that an old one leaked out.] Don Armstro

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Zach Sadecki
hmm... now I'm confused. The latest .deb on your site doesn't have any /usr/sbin/posfix (or /usr/sbin/postfix) reference in the init script... Don Armstrong wrote: On Fri, 13 Oct 2006, Zach Sadecki wrote: Uhh... It works fine if I use the PIDFILE entry in the defaults file like you had in th

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Don Armstrong
On Fri, 13 Oct 2006, Zach Sadecki wrote: > Uhh... It works fine if I use the PIDFILE entry in the defaults file > like you had in the last attempt, but if I comment it out (since you > removed that line in the latest defaults from the .deb) it gives the > "Starting Sendmail milter plugin for Sp

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Zach Sadecki
Uhh... It works fine if I use the PIDFILE entry in the defaults file like you had in the last attempt, but if I comment it out (since you removed that line in the latest defaults from the .deb) it gives the "Starting Sendmail milter plugin for SpamAssassin: Could not open pidfile: Permission d

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Don Armstrong
On Fri, 13 Oct 2006, Zach Sadecki wrote: > >I've changed the way that this is done now; you can easily set SOCKET > >in /etc/default/spamass-milter, and I've added an RUNAS option there > >as well, which you can use to change the user that spamass-milter is > >running as. > > > >Can you check the

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Zach Sadecki
Works fine now. Thanks. Don Armstrong wrote: On Fri, 13 Oct 2006, Zach Sadecki wrote: I've changed the way that this is done now; you can easily set SOCKET in /etc/default/spamass-milter, and I've added an RUNAS option there as well, which you can use to change the user that spamass-milter is

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Don Armstrong
On Fri, 13 Oct 2006, Zach Sadecki wrote: > Works fine now. Thanks. Ok; I've got one last iteration which should obviate the need to even edit the defaults file. Can you see if it works for you? Don Armstrong -- "There are two major products that come out of Berkeley: LSD and UNIX. We don't be

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Zach Sadecki
I've changed the way that this is done now; you can easily set SOCKET in /etc/default/spamass-milter, and I've added an RUNAS option there as well, which you can use to change the user that spamass-milter is running as. Can you check the debs on http://archimedes.ucr.edu/ss/spamass-milter_0.3.1-3

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-13 Thread Don Armstrong
On Sun, 08 Oct 2006, Zach Sadecki wrote: > There are some basic incompatibility problems between the socket that > the spamass-milter startup script creates and what is needed for use > with Postfix. First of all, Postfix runs chrooted, so the socket must > be under its queue directory (/var/sp

Bug#391789: Spamass-milter socket problems with Postfix

2006-10-08 Thread Zach Sadecki
Package: spamass-milter Version: 0.3.1-2 There are some basic incompatibility problems between the socket that the spamass-milter startup script creates and what is needed for use with Postfix. First of all, Postfix runs chrooted, so the socket must be under its queue directory (/var/spool/po