Spamassasin does not autostart in debian Jessie

Submitted by janderk on Fri, 12/18/2015 - 07:26

I just installed a fresh new Debian Jessie server and ran the Virtualmin install script. All fine, except for spamassasin that did not start automatically after booting.

/var/log/syslog shows:

Dec 18 11:29:25 Debian-82-jessie-64-minimal spamc[5174]: connect to spamd on ::1 failed, retrying (#1 of 3): Connection refused
Dec 18 11:29:25 Debian-82-jessie-64-minimal spamc[5174]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused

Google gave me these links: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764438 https://sowhatisthesolution.wordpress.com/2015/04/27/upgrading-spamassas...

The issue was fixed by issuing the following command:

systemctl enable spamassassin

I thought it would be nice if this command was executed in the virtualmin install script. But maybe this is just a Debian or Spamassasin bug.

Status: 
Active

Comments

Submitted by andreychek on Fri, 12/18/2015 - 08:39

Howdy -- hmm, are you using a VPS, or a dedicated server there?

It does indeed sound like a Debian bug, but we'll look deeper into that.

Thanks for letting us know!

Submitted by janderk on Fri, 12/18/2015 - 08:52

It's a dedicated server at Hetzner (EX41-SSD with Debian 8.2 minimal). After that did apt-get update and upgrade which installed a new grub version. Then I ran the virtualmin install script. Spamassasin is version 3.4.0:

>spamd -V
SpamAssassin Server version 3.4.0
  running on Perl 5.20.2
  with SSL support (IO::Socket::SSL 2.002)
  with zlib support (Compress::Zlib 2.064)

I thought I mention it in case somebody else runs into this. The weird thing in the Debian bug report is that it says that the bug was fixed more than a year ago. Is the spamassasin version in Debian older than that?

Anyway. Keep up the good work. Great to see in another post that you guys will support letsencrypt soon.