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
/etc/cron.daily/spamassassin:
Jan  3 07:26:21.512 [9564] warn: config: failed to parse line, skipping, in "/etc/spamassassin/local.cf": 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:
 spamassassin

Has anyone seen this before?

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