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

  1. D

    Resolved Webmail 500 error after installing Plesk Premium Email

    With the help of Plesk support both issues with webmail and IMAP were solved. Auto discovery and ActiveSync now also work very well. Plesk support can be great although slow and challenging to reach when you get your license from a reseller.
  2. D

    Resolved Issue receiving emails TLS library problem

    It's generally a bad idea to lower server-wide security for some people that still use 12+ year old software. You can't support software that's no longer supported or maintained. They can always upgrade Office, use 365, use webmail, use free Windows Mail, use Thunderbird. Just saying. :)
  3. D

    Resolved Webmail 500 error after installing Plesk Premium Email

    Hi! Because I was looking forward to using ActiveSync on my Plesk server, I purchased a license for Premium Email and installed the addon. At first I was unable to log into Horde with username/password combinations that worked perfectly well before. Because Premium Email only works with...
  4. D

    Issue Let's Encrypt and "Assign the certificate to mail domain" problems and AutoDiscovery issues caused by this

    I know I'm late to the party but this is still something I'd really like to see happen. The subdomain mail.<domain> needs to be included with the Let's Encrypt SSL-sertificate when you enable "Assign the certificate to the mail domain". That way there won't be any issues with the certificate...
See more
Back
Top