• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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 kicked the bucket.. HELP!

T

tutt

Guest
No erros in any logs, no nothing. The other day, one domain stopped accepting POP and IMAP passwords for all email users. I removed and re-added the domain, and set everything back up. From that point forward, spamassassin is no longer tagging any mail passing through the system for that domain and all other domains on the system.

The mail log shows when I restart spamassassin and gives no errors, but there is no evidence that mail is being passed through spamassassin at all. What else can I do?
 
You could try the bash tool /usr/local/psa/admin/sbin/mchk --with-spam to reconfigure all domains.
 
Back
Top