• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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