I've tried altering things but the best I can get is the message:
"warning: connect to Milter service unix:/var/run/spamass/spamass.sock: No such file or directory"

The folder exists with the permissions postfix:postfix 0660. I have also tried spamass-milter:postfix.

On restarting spamassassin, whether as a content filter or a milter, I get:
"spamd: server started on IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783"

In the three spamxxx files in /etc/default I now have socket and pid as...

/etc/default/spamassassin
  PIDFILE="/var/run/spamass/spamd.pid"

/etc/default/spamass-milter
OPTIONS="-u spamass-milter -i 127.0.0.1 -m -I -- --socket=/var/run/spamass/spamd.sock"
  SOCKET="/var/run/spamass/spamass.sock"
  SOCKETOWNER="postfix:postfix"
  SOCKETMODE="0660"

/etc/default/spampd
  PIDFILE=/var/run/spamass/spamd.pid

No matter how I start postfix and spamassassin, /var/run/spamass remains empty but spamassassin.pid is rewritten to /var/run.

I am restarting using:
  sudo service postfix restart
  sudo service spamassassin restart

I suspect is not spass-milter is not being started?

--
Dave Stiles


Reply via email to