• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question Plesk 17.8 and domain SSL mail

sebgonzes

Silver Pleskian
Hello

Plesk 17.8 still not include this feature? It's really the thing that we need actually, to not have to explain to our client that they had to accept the "Default" SSL when they configure the mail client program...

@IgorG Can we give us some news about this?
 
If you have a dedicated IP you can manually configure postfix to use their certificate.

I wish Plesk would offer this more customer friendly
 
If you have a dedicated IP you can manually configure postfix to use their certificate.

I wish Plesk would offer this more customer friendly

Well, it's shared servers hostings, so a lot of domain in each server. Each domain can have is own let's encrypt, but for now, all have to use the same SSL mail server that not corresponding with is own domain/SSL...
 
From here (https://YOUR-PLESK-DOMAIN:8443/admin/ssl-certificate/list) you can set the certificate to use for the SMTP server, you can even set the Let's Encrypt certificate securing the plesk server if you want.

However, you will need to tell the users to use that domain and not their own.

So if you have your panel running on https://pizza.cool.host:8443/ you should tell your users to use pizza.cool.host as the SMTP server domain when setting up their email (as long as the certificate you selected is valid for that domain).

This is a limitation by the SMTP server which can only handle a single certificate per IP.
 
From here (https://YOUR-PLESK-DOMAIN:8443/admin/ssl-certificate/list) you can set the certificate to use for the SMTP server, you can even set the Let's Encrypt certificate securing the plesk server if you want.

However, you will need to tell the users to use that domain and not their own.

So if you have your panel running on https://pizza.cool.host:8443/ you should tell your users to use pizza.cool.host as the SMTP server domain when setting up their email (as long as the certificate you selected is valid for that domain).

This is a limitation by the SMTP server which can only handle a single certificate per IP.

So there will not be any other solution in the future to use each client is own pop3/smtp address and SSL?
 
As a solution you could issue a certificate with every mail domain.
mail.domain1.tld
mail.domain2.tld
etc.

Most Email clients support SNI
 
Back
Top