Hi,
CentOS 6.7, Plesk 12.0.18, latest MU
Background: shared hosting environment, multiple domains. Courier/IMAP and Postfix as mail servers.
Was investigating to have each domain have it's own mail server security certificate.
example:
abc.com has mail.abc.com subdomain for use as mail server. Client would like his/her own cert for mail.abc.com for mail connections.
xyz.com has mail.xyz.com subdomain for use as mail server. Client would also like to have his/her own cert for mail.xyz.com for mail connections.
From what I read on forum and the KB acticles, it seems at present Plesk allows only one cert for each mail service per IP, not per domain on an IP.
Can anyone confirm? Or did I miss some stuff?
--
Reason for all the digging was the intended integration of letsencrypt; whether manually, or as build-in Plesk feature. With the added advantage of
https://community.letsencrypt.org/t/use-on-non-web-servers/425/2
statement:
"
Just in case people reading this thread aren't familiar with the key usage concept, the Let's Encrypt certs are indeed intended to be used with POP, IMAP, and SMTP servers and should work fine for these applications.
The applications that are forbidden by the EKU policies are other non-TLS uses such as code signing.
Hopefully the Let's Encrypt client will eventually even have built-in functionality to help you automatically install certs into servers for other Internet protocols, like IMAP servers.
"
CentOS 6.7, Plesk 12.0.18, latest MU
Background: shared hosting environment, multiple domains. Courier/IMAP and Postfix as mail servers.
Was investigating to have each domain have it's own mail server security certificate.
example:
abc.com has mail.abc.com subdomain for use as mail server. Client would like his/her own cert for mail.abc.com for mail connections.
xyz.com has mail.xyz.com subdomain for use as mail server. Client would also like to have his/her own cert for mail.xyz.com for mail connections.
From what I read on forum and the KB acticles, it seems at present Plesk allows only one cert for each mail service per IP, not per domain on an IP.
Can anyone confirm? Or did I miss some stuff?
--
Reason for all the digging was the intended integration of letsencrypt; whether manually, or as build-in Plesk feature. With the added advantage of
https://community.letsencrypt.org/t/use-on-non-web-servers/425/2
statement:
"
Just in case people reading this thread aren't familiar with the key usage concept, the Let's Encrypt certs are indeed intended to be used with POP, IMAP, and SMTP servers and should work fine for these applications.
The applications that are forbidden by the EKU policies are other non-TLS uses such as code signing.
Hopefully the Let's Encrypt client will eventually even have built-in functionality to help you automatically install certs into servers for other Internet protocols, like IMAP servers.
"