• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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