• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Thawte SSL cert for courier-imap

F

faris

Guest
Can anybody give me some instructions please?

There are a few threads here that talk about generating your own SSL certs for use with courier-imap for allow clients to get their email over an SSL link. But these seem to involve requiring the clients to download the generated cert and install it on their machines.

But I have a lovely Thawte SSL cert for our main website. Can I use this cert instead of generating my own (and presumably this won't require users to download anything)? Or will the fact that the FQDN has a www in front of it make a difference? This particular domain is the default domain in Plesk for the 1st IP address in my server.

And if I can use it, what exactly do I need to do? What bits should I copy?

Any help on this would be appreciated!

Faris.
 
Back
Top