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

  1. L

    Spamassassin connect to spamd on ::1 failed - doesn't scan messages

    I don't use IPv6, but I have more servers with the same configuration and SpamAssassin works fine; without ipv4 option, just default options. Any more ideas to solve it?
  2. L

    Spamassassin connect to spamd on ::1 failed - doesn't scan messages

    Maybe --ipv4-only is incorrect option? root 7878 0.5 2.9 276664 61696 ? Ss 12:47 0:01 /usr/bin/spamd --pidfile /var/run/spamd.pid --ipv4-only --nouser-config --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin...
  3. L

    Spamassassin connect to spamd on ::1 failed - doesn't scan messages

    Hello, I have: Centos 7.2.11 Plesk 12.0.8 postfix-2.10.1-6.el7.x86_64 spamassassin-3.4.0-2.el7.x86_64 I detect some messages aren't scanned by spam, I just receive <code> May 16 10:40:36 plesk135 spamc[8789]: connect to spamd on ::1 failed, retrying (#1 of 3): Connection...
  4. L

    Plesk update error

    I found the same problem. Centos 7 with plesk 12.5.30.
Back
Top