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_i386.deb to make
sure that they resolve the issues for postfix users?
Don Armstrong
With the 0.3.1-3 script I get this on startup:
"Starting Sendmail milter plugin for SpamAssassin: Could not open
pidfile: Permission denied"
I believe the problem is that the postfix user has no write permissions
to /var/run and therefore can't write the .pid file (error didn't go
away after I deleted spamass.pid). Also previous versions of
spamass-milter leave the root owned .pid file in there after stopping
causing another owner/permission problem. I went in and manually changed
the owner of spamass.pid to postfix and the problem went away.
Also, another permission problem is that the /var/spool/postfix
directory is owned by root, too, causing socket write issues during startup.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
