• 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.

SA fails after upgrade

Tozz

Regular Pleskian
Hello

We have updated one of our Plesk 8 machines to Plesk 8.1. After this upgrade the machine has lots of permission problems (cant write lock files, cant open directories). That was fixed after I chowned the directories and lockfiles to 'psaadm' instead of root. However, one problem still remains.

The SpamAssassin service does not work. The CP says spamassassin is disabled, but it is installed. Also, the license manager says that we are allowed to use SA. I tried reinstalling SpamAssassin but that does not work. I was hoping anyone could give some hints about how to resolve this.
 
Yes, psa-spamassassin is installed. I figured out that when I add a tupel in the MySQL table psa.sa_conf that corresponds to the e-mail account that SA is active on that domain and it works.

Now I only need to figure our why Plesk turned off SA for all accounts all of a sudden.
 
Back
Top