• 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 Update Let's Encrypt not working with mailserver SSL

ahbirkner

New Pleskian
Hi,
if i update SSL manuallly in plesk everything works fine. using: Tools -> SSL/TLS -> Secure Plesk and Mailserver
When I check Plesk new certificate the new time period (new SSL-Certificate) will show up in the browser
But if I try to connect via Outlook, I get an error, saying the certificate time is up...

So I used: //email/testTo:
an got:
STARTTLS command works on this server
[000.801]Connection converted to SSL
SSLVersion in use: TLSv1_2
Cipher in use: ECDHE-RSA-AES128-GCM-SHA256
Perfect Forward Secrecy: yes
Certificate #1 of 4 (sent by MX): EXPIRED
Cert VALIDATION ERROR(S): certificate has expired
So email is encrypted but the recipient domain is not verified
Cert Hostname VERIFIED (...)
Not Valid Before: Dec 12 08:28:06 2021 GMT
Not Valid After: Mar 12 08:28:05 2022 GMT

which is the old (SSL-Certificate) one...

I have to admit that I first used the certificate from one domain and did not use "Secure Plesk...", which I use now...

Any ideas how to fix that.

I disabled postfix, dovecot and tried again. Maybe something locked the files... but I could not supply the new certificate...
 
Back
Top