• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question Mail automatically secured by SSL/TLS?

Pleskie

Regular Pleskian
Hi, a quick question.

When I create a new mail address in Plesk, is it automatically secured by SSL/TLS?

Regards
 
A mail address can never be secured by SSL/TLS. Instead, the connection between client and server can be secured. If you have a valid certificate for your Plesk host name installed and if the client connects to POP, IMAP and SMTP using SSL/TLS and the host name (not the individual domain name of the subscription), then the connection is automatically properly secured. If the client is not connecting by using the host name of the host where the SSL certificate is installed, the connection is insecure. If the client is using the host name where the SSL certificate is installed, but is using SSL/TLS, the connection is insecure. For SSL to work you do not need to set an SSL checkbox in Plesk's mailbox configuration. If the host supports SSL, clients can use SSL when connecting to the mailbox. They must meet the conditions named in this post to properly establish a secure connection, though.
 
Thank you Peter Debik

Things are much clearer now.

>> If you have a valid certificate for your Plesk host name installed ...

Do I need to buy a valid certificate or can Plesk generate this certificate?

>> If the client is using the host name where the SSL certificate is installed, but is using SSL/TLS, the connection is insecure.

Is this sentence correct, or did you forget the word "not"?
 
Yes, I forgot the "not".

Plesk comes with a self-signed certificate, but you should use a commercial certificate to secure the host name, because you need a trust center signature to avoid browser warnings. I think there was a post on here, too, how to generate a host name certificate using Let's Encrypt, but not sure.
 
Thanks Peter Debik

>> ... to avoid browser warnings

I'm not an expert and I wonder what browser warnings have to do with a mail client? Can you explain?

So in other words I will have to buy an (expensive?) certificate to make SSL/TLS work?
 
Mail clients will display warnings, too, if the server certificate is self-signed.

From Plesk 17 on there should be an option to use a free Let's Encrypt certs to secure the host.
 
Thanks ... I don't really understand all of this and what exactly I should do right now to make my SSL/TLS work :-(
 
Back
Top