• 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.

Issue Mail servers using old certifcate

thinkingcap

Basic Pleskian
Looking at a client site in SSL iT the certificate expires in Feb 2020. If I run the following check against SMTP ports the certificate that SMTP uses expires tomorrow.
Code:
echo | openssl s_client -servername clientxxx.com.au -connect clientxxx.com.au:587 2>/dev/null -starttls smtp | openssl x509 -noout -dates

Then if I go into Mail Settings for this client and without changing anything I hit "OK" the certificate gets updated to one issued in November and expires in Feb 2020.

Anyone else seeing this behaviour?
TIA
Dave
 
I was getting unpredictable results too using openssl s_client commands on my SMTP server. However, I tried using online testers remotely and found they were reading the correct (expected) certificates. I presume the openssl commands do not read SNI correctly.
Try this tool and see if it differs from your internal results: //email/testTo:

I may be misunderstanding your problem... are you getting incorrect certificate readings, or incorrect certificate creation?
 
I don't think so as a client alerted me to it with an error on their iPhone "Can not verify server identity"
 
Back
Top