• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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.
See more
Back
Top