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

Search results

  1. F

    Issue 2 "To:" fields in email header - After upgrade to 18.0.37

    I got the issue, that there are 2 similar "To:" fields in my Email headers in outgoing mail. So the mails are marked as spam or are unable to deliver. Does anyone know anything about that behavior? To: mail@example.com To: mail@example.com From: "mail@example.com2" <mail@example.com2> Subject...
  2. F

    Issue new created mail account, with full password length (255), not automatically inserted into authentication database

    Whenever I create a new mailaccount via GUI, with full password length (255 upper, lower, digits, specials !@#$%^&*?~ ) on my Plesk Obsidian (18.0.36) !OR! Plesk Onyx (17.8.11) the account is created without adding it automatically to the authentication database...
Back
Top