• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Resolved Spamc not working

fliegerhermi

Regular Pleskian
Hi. I just set up a new plesk server for migration from old onyx installation.
It seems that spamassassin isn't working.

I sent an email with the (SpamAssassin Test – netcup Wiki) test-phrase from a google-mail-address.

The score is always 0 and there is not Spam-Header in the e-mail except for the following:
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.mydomain.de

Mail.log:
Feb 19 11:32:31 mail spamassassin[1734]: Starting the spamassassin filter...
Feb 19 11:32:31 mail spamc[1735]: connect to spamd on ::1 failed, retrying (#1 of 3): Connection refused
Feb 19 11:32:31 mail spamd[1690]: spamd: connection from 127.0.0.1 [127.0.0.1]:36016 to port 783, fd 5
Feb 19 11:32:31 mail spamd[1690]: spamd: using default config for [email protected]: /var/qmail/mailnames/mydomain.de/max/.spamassassin/user_prefs
Feb 19 11:32:31 mail spamd[1690]: spamd: processing message <[email protected]> for [email protected]:30
Feb 19 11:32:31 mail spamd[1690]: spamd: clean message (0.0/4.0) for [email protected]:30 in 0.1 seconds, 5287 bytes.
Feb 19 11:32:31 mail spamd[1690]: spamd: result: . 0 - scantime=0.1,size=5287,user=[email protected],uid=30,required_score=4.0,rhost=127.0.0.1,raddr=127.0.0.1,rport=36016,mid=<[email protected]>,autolearn=ham autolearn_force=no

Any ideas?
Thanks
 
Sorry! Very dumm.

IPv6 is not running, but I had a wrong rule update script with sa_update instead of sa-update.
Running sa-update once solved the issue...
 
Back
Top