After installing or updating cPanel, SpamAssassin is unable to start. During sa-update, the below errors can be identified.
- /usr/local/cpanel/3rdparty/perl/530/bin/sa-update -v
no 'mirrors.updates.spamassassin.org' record found, channel failed
- /usr/local/cpanel/3rdparty/perl/530/bin/sa-update -D -vvv
Feb 20 07:39:01.888  dbg: dns: query failed: 4.4.3.updates.spamassassin.org => REFUSED
DNS TXT query 4.4.3.updates.spamassassin.org failed: REFUSED
Feb 20 07:39:01.907  dbg: dns: query failed: mirrors.updates.spamassassin.org => REFUSED
DNS TXT query mirrors.updates.spamassassin.org failed: REFUSED
channel 'updates.spamassassin.org': no 'mirrors.updates.spamassassin.org' record found, channel failed
Feb 20 07:39:01.908  dbg: diag: updates complete, exiting with code 4
Update failed, exiting with code 4
SpamAssassin probes for DNS TXT records when attempting to install or stage the rule updates. If the TXT record can't be received, this kind of failure will occur, which causes the service to fail during restarts. SpamAssassin can't start without rules being installed.
Update the resolver if the resolver prevents the DNS type TXT record from being received. The resolvers are stored in the below file:
Contact the server's network provider to determine further why this type of DNS record can't be received back to the server.
After the DNS issue has been resolved, update the rules and restart SpamAssassin.