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

problems after yum update...

R

robca

Guest
Yesterday i accidently did a yum update, it was accidently in that way it updated spamassassin to 3.0.x version which is not supported by Plesk, the other thing i have done by mistake was mysql 4.0.x

The problems:

How can i downgrade spamassassin so it is back controlable by plesk?

And for mysql when i use phpmyadmin, the user can see all mysql databases... they can only adjust their mysql but get a list of all databases on the server... someone a solution to prevent this?

Thx for the help in advance!
 
As for spamassassin, I assume you're using ART's yum repository. Just do:

#yum remove spamassassin

Once that's done, go to the "Updater" icon in your control panel and have it install spamassassin, it will be the corect version.

As for mysql, it sounds as if you have phpMyAdmin configured incorrectly
 
did any one upgrade spamassassin to 3.0.2 ? (from up2date)

i had a bad experience with art's spamassassin's package (i was getting blank emails and had to downgrade too) so i'd like to know first this time :D
 
Back
Top