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

    Question 60 seconds unresponding WP-Instance causes Malware warning for Admins/Resellers/Customers

    Hi everyone, just a warning, so that you can get around this silly feature / nightmare with your customers losing trust in you as a serious hoster. Tonight, we did a planned Database cluster maintenance and upgrade. Everything went well and smoothly, but as planned, the application servers were...
  2. P

    Issue Using Plesk Premium Antivirus (Dr.Web) with Premium Email and Premium Email Security

    Dear Plesk community, in order to make our Mailserver more secure and feature rich, we're using: - Plesk Premium Email (Kolab) - Plesk Email Security (Spamassassin + ClamAV) - Plesk Premium Antivirus (Dr. Web) Now since ClamAV doesn't even recognize simple Macro viruses in Word files, I had to...
  3. P

    Issue Let's encrypt renewal fails since update to Plesk 18.0.27 Update #1

    Since the update, I get the error message below, when the SSL extension tries to auto-renew a certificate: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/12345. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching...
  4. P

    Question Plesk Kolab Premium Email - 1) Configuration file 2) Sieve / Filters

    Hey everyone! 1) I'm having some trouble with my Kolab configuration. As I've tested a few things, I'm not sure anymore if a config file was set by me or the Kolab setup itself. In /etc/dovecot/conf.d, is the file "99-special-use-default.conf" meant to be there or did I include that by myself...
  5. P

    Forwarded to devs Dovecot SNI not working with Plesk Premium Email Extension (Kolab/Guam)

    TITLE: Dovecot SNI not working with Plesk Premium Email Extension (Kolab/Guam) PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Version 18.0.21 Update #5, Debian 9.11 PROBLEM DESCRIPTION: When setting up SNI in the new Plesk Obsidian, certificate also configured for each domain's email...
  6. P

    Issue Dovecot SNI doesn't seem to be working with Plesk Premium Email Extension (Kolab/Guam)

    I've been investing some serious hours to get Postfix/Dovecot working with SNI certifiactes and the Plesk Premium Email Extension (Kolab) now. However, echo | openssl s_client -connect localhost:993 -servername xyz.com will keep returning the global server's mail certificate, not dovecot's...
Back
Top