• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Recent content by Tomas.Michal

  1. T

    Question Reverse DNS is not a valid Hostname (crazy...)

    Hello, thanks for the quick reply. Unfortunately, my problem is probably a bit more difficult. In /etc/postfix/main.cf I had to reset the setting to original: myhostname = ip212-132-104-61.pbiaas.com The reason for this is that mails to invalid names are not returned...
  2. T

    Question Reverse DNS is not a valid Hostname (crazy...)

    Hello, i have follow error on my MailServer, but all mails can be sending to other in success. If I Check https://mxtoolbox.com/SuperTool.aspx?action=smtp%3a212.132.104.61&run=toolpage Then the SMTP Valid Hostname Fail to Reverse DNS is not a valid Hostname The PTR Check on ...
  3. T

    Resolved no search possible keyword in whitelist. (spamfilter / whitelist)

    After the Update from Plesk 18.0.56 -> 18.0.57 now all OK.. :-) I wondering.. but happy...
  4. T

    Resolved no search possible keyword in whitelist. (spamfilter / whitelist)

    am i the only one with the error ? does it work smoothly for you ?
  5. T

    Resolved no search possible keyword in whitelist. (spamfilter / whitelist)

    Hello, after Server New Install / Plesk New Instrall and rewrite my White List, I can no longer perform a search in my whitelist (or in the other lists). No matter what I search for, the answer is always the complete list, i.e. all entries. If I leave the field empty and type search or reset...
Back
Top