• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Plesk Onyx Windows MailEnable LetsEncrypt and SANs

Martin Baker

New Pleskian
Have a plesk managed server with several IP addresses.

With UK GDPR we have to establish secure coms by 25 May - but all efforts seem to no avail

Problem is that mailEnable will only issue mails from the default domain.

The default domain has a certificate and all works well for pop3//imap

However with the other domains they have their own IP address, rDNS etc. SO when trying eg with gmail or thundercloud to connect pop3 on port 995 you get complaint that the default domain and its certificate do not match the anticipated certificate of the domain with its own IP address.

I presume the fix is to get the main domain to have a certificate with SANS for each of the separate domains on my server. Question is how can that be done as I cannot even persuade Plesk/LetsEncrypt to do wild cards let alone SANs I see some LInux related guidance but nothing for Windows

Any way forward would be appreciated

Many thanks in advance
 
Back
Top