Control: severity -1 important

> $ systemctl status spamassassin.service
> ● spamassassin.service - Perl-based spam filter using text analysis
>    Loaded: loaded (/lib/systemd/system/spamassassin.service; disabled; vendor 
> preset: enabled)
>    Active: inactive (dead)

Please run:
systemctl enable spamassassin.service
systemctl start spamassassin.service

> Before the upgrade, it was working fine, and I haven't changed
> anything in the configuration.

Believe it or not, it's a bug that you were running spamd in the first
place, as you had not enabled it. spamd is an optional feature of the
spamassassin package. Therefor, unlike most daemons shipped with Debian,
it is disabled by default and only enabled at the explicit request of
the admin. In the sysvinit days, that was accomplished with a setting in
/etc/default/spamassassin, but that mechanism has changed with systemd.
The systemd method was not working correctly until recently...

While I believe that the current behavior is the least buggy, honestly I
wonder if the final fix for this might be to introduce a new "spamd"
package, recommended by spamassassin, that just installs a unit file.
Would be a lot easier to reason about.

noah

Attachment: signature.asc
Description: PGP signature

Reply via email to