Spamassassin update is failing

Posted January 3, 2020 2.4k views
Debian 10

I am running on a fairly standard droplet (Debian 10 web+mail server). Overnight spamassassin fails to update and I get an email with this at the beginning.

run-parts: /etc/cron.daily/do-agent exited with return code 100
Jan  3 07:26:21.512 [9564] warn: config: failed to parse line, skipping, in "/etc/spamassassin/": use_dcc 0
Jan  3 07:26:22.337 [9564] warn: lint: 1 issues detected, please rerun with debug enabled for more information
Jan  3 07:26:22.554 [9567] dbg: logger: adding facilities: all
Jan  3 07:26:22.554 [9567] dbg: logger: logging level is DBG
Jan  3 07:26:22.554 [9567] dbg: generic: SpamAssassin version 3.4.2
Jan  3 07:26:22.554 [9567] dbg: generic: Perl 5.028001, PREFIX=/usr, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
Jan  3 07:26:22.554 [9567] dbg: config: timing enabled
Jan  3 07:26:22.556 [9567] dbg: config: score set 0 chosen.
Jan  3 07:26:22.559 [9567] dbg: util: running in taint mode? yes
Jan  3 07:26:22.559 [9567] dbg: util: taint mode: deleting unsafe environment variables, resetting PATH

I commented out the offending “use_dcc 0” line and uninstall/install spamassassin to get different errors

/etc/spamassassin# dpkg --configure spamassassin
Setting up spamassassin (3.4.2-1+deb10u1) ...
This account is currently not available.
dpkg: error processing package spamassassin (--configure):
 installed spamassassin package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:

Has anyone seen this before?

Note that I haven’t touched the postfix/dovecot or spamassassin configuration for a month or more.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hi @scycheng,

Please try out the following:

Uncomment loadplugin Mail::SpamAssassin::Plugin::DCC in /etc/spamassassin/v310.pre

If there is no such file, you can edit the configuration file /etc/spamassassin/, adding the following line before “use_dcc 0”:

loadplugin Mail::SpamAssassin::Plugin::DCC

Once you have added the above to the file, just test SpamAssassin again.


  • Thanks.

    I suspected corrupted spamassassin configuration back then due to alpha particles or something similar. As I didn’t customize the installlation at all, I uninstalled and purged spamassassin configuration data.

    That resolved whatever issue spamassassin was having.

    • Hi @scycheng,

      Thank you for clarifying! This does seem odd however. It’s weird SpamAssassin got corrupted without any changes from your end whatsoever.

      Anyway, I’m glad to see everything is working back as usual.