• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Spamassassin complaining about report_contact

J

JohnD@

Guest
Have been running spamassassin for some time along with RulesDuJour and it have more or less worked perfect. But a week back ago a lot of SPAM started to coming trouh and I run a "spamssassin --lint" to see if anything was wrong:
spamassassin --lint
[19135] warn: config: SpamAssassin failed to parse line, no value provided for "report_contact", skipping: report_contact
[19135] warn: lint: 1 issues detected, please rerun with debug enabled for more information

After some digging on Google I found that this cound be due to auto-updated rulesets (using RulesDuJour) and that some rules need the report_contact variable to be set, so I added the followin into local.cf:
But the problem still is there. Have also bee trying to add the variable into /var/spool/qscan/.spamassassin/user_prefs with the same error coming up.

Running spamassassin version 3.1.3-1.rhel4.art and qmail-scanner 2.01-9.rhel4.art on CentOS 4.3
 
In case you still haven't solved this - I was getting the same error. Check in /usr/share/spamassassin and see if you have a file named 10_misc.cf. Around line 45 add a value after report__contact like:

report_contact [email protected]

That should do it.
 
Back
Top