• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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 admin@domain.com

That should do it.
 
Back
Top