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

  1. SysInt

    Resolved Firewall blocks entire server

    SOLVED: my provider (OVH) supplied an resceu mode. After started disabled the firewall and started the server again. Help!!! I removed the blocked IP-address in a firewall rule. But i didn't remove the firewall rule itself. An empty rule translates apparantly as "DENY FROM ALL FROM ALL PORTS"...
  2. SysInt

    Resolved Horde stopped sending mail after upgrade 12.5.30

    Yes!!! that did the trick. With Postfix MTA everything works again. But, i remenber that a few years back i had to change to qmail because Postfix didn't work. There is a cat and mouse play going on :-) Thank you so much.
  3. SysInt

    Resolved Horde stopped sending mail after upgrade 12.5.30

    Hé IgorG Didn't make a difference. It keeps saying relaylock on 0000::0001 in the maillog
  4. SysInt

    Resolved Horde stopped sending mail after upgrade 12.5.30

    Yes, but empty
  5. SysInt

    Resolved Horde stopped sending mail after upgrade 12.5.30

    Thanks IgorG, done that makes no difference. BTW: my white-list is correct 127.0.0.1 and ::1 is present
  6. SysInt

    Resolved Horde stopped sending mail after upgrade 12.5.30

    Since the update of plesk 12.5.30 all my customers can't send mail any more from the mailclient horde (2.6). The error they get is "There was an error sending your message <domain> ESMTP" Mail from site-forms are still working. I am using qmail. In the maillog i found a statement...
See more
Back
Top