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

plesk email security

  1. M

    Question How to get Plesk to delete / kill emails containing Big5 character set?

    Sounds simple, but is - as ever with Plesk - bizarrely hard to find out how to do it -- - We have Plesk Email Security. - We have SpamAssassin and/or Amavis - We have some clients with Chinese characters in their incoming spam emails. We wish to tell Plesk to delete any emails coming in to the...
  2. J

    Question DNSBL settings in Plesk Email Security vs general mail server settings?

    In the settings of the Plesk Email Security extension, in the "Server Settings" tab under the "Advanced" section, is a setting titled "DNSBL" where I can enable various DNS block lists: How does this relate to the general "Mail Server Settings" / "Server-wide mail settings", which in the...
  3. J

    Resolved Error installing ClamAV in Plesk Email Security on AlmaLinux 10

    I installed Plesk Email Security on my AlmaLinux 10 server and activated a paid license. Then I attempted to install ClamAV, but it fails with the following error: I already found these related topics and articles about a previous similar issue on AlmaLinux 9: Resolved - Error installing...
  4. M

    Issue NetworkManager and Plesk Email Security: How to deal with conflating/ambiguous demands?

    We have Plesk Email Security, which has started to state in the Email Deliverability page: We have Bind DNS on AlmaLinux 9.7 and so am following the instructions that are set out on the link: But, our /etc/resolv.conf contains the following: I do not recognise these IP as presented so...
Back
Top