Spam Assassin Error - Spamassassin is not running ([Errno 111] Connection refused; port 10025)

Maintenance
1

My initial installation was flawless after I redirected the Name Server records and added the SSL certificates.

The most recent change i have made was implementing DNSSEC but I have no errors on those from the status check.

The only error that has come up is: Spamassassin is not running ([Errno 111] Connection refused; port 10025).

I do have UFW running but port 10025 is not listed as permitted. By default, I deny all incoming and allow outgoing connections.

Do I need a UFW rule for that? If so is it inbound our outbound or bi-directional?

Thank you in advance!

2

No UFW needed, spamassassin is local only:

~ bronson@int $ sudo netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
…
tcp 0 0 127.0.0.1:10023 0.0.0.0:* LISTEN 1207/postgrey.pid -
tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN 1251/perl

3

Guessing that spamassassin got shut down somehow… does rebooting your box fix it?

4

The spamassassin Bayesian DB disk directory path and files ownership gets changed to root:root after updates. Look in your logs for complaints. You will need to chown -R spamd:spamd /<Bayesian DB path>/ if you see the path and files are owned by root.

5

Thank you all for the responses. Interestingly enough, the error seemed to have gone away. The permission looked correct in the as well.