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

Issue Subject Alternative Name for mail subdomain missing

nilsglow

New Pleskian
Hi!
We try to secure our mail server (IMAP) with Letsencrypt. Plesk says that 'Mail access" (IMAP, POP, SMTP) is secured. But the certificate does not contain the mail.example.tld subdomain as a Subject Alternative Name. We told our customers to access the mail server via this subdomain...

Thanks,
Nils
 
It seems like that problem only occurs when NOT using wildcard certificates... But shouldn't it work with a SAN certificate including mail.example.tld as well?
 
Back
Top