Facebook
Twitter-
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 Secure mail part of domain with Lets Encrypt
- Thread starter psxeu
- Start date
ChristophRo
Regular Pleskian
There is currently no nice way to do that and while some workarounds* should be possible, they are limited in their use.
So in general you're best of using "your.plesk-server.name" as mailserver for your customers and not mail.domain.tld
* such a workaround would be to create a normal domain, name it "mail.xxxx.com" and use LetsEncrypt on that. (dns and mail service should be disabled for that)
For every further domain on your server, you can then add "mail.xxxx.com" as an alias domain and make sure it's also covered by the LetsEncrypt Certificate.
Under "Tools & Settings" -> "SSL/TLS Certificates" -> "Certificate for securing mail" you then choose the "mail.xxxx.com"s domain LetsEncrypt certicate from the server pool
So in general you're best of using "your.plesk-server.name" as mailserver for your customers and not mail.domain.tld
* such a workaround would be to create a normal domain, name it "mail.xxxx.com" and use LetsEncrypt on that. (dns and mail service should be disabled for that)
For every further domain on your server, you can then add "mail.xxxx.com" as an alias domain and make sure it's also covered by the LetsEncrypt Certificate.
Under "Tools & Settings" -> "SSL/TLS Certificates" -> "Certificate for securing mail" you then choose the "mail.xxxx.com"s domain LetsEncrypt certicate from the server pool
Similar threads
