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

Issue SSL Certificate for emails

Erwan

Regular Pleskian
Hi all,

We have a certificate for domain emails on Plesk Onyx.
Everything worked until then.

Outlook:
Client IMAP : 993 and SSL/TLS
Client SMTP : 587 and SSL

We have renew the certificate and SMTP don't work after that.
In fact, it work but with 465 and SSL/TLS.

Do you know the reason for the change? How can we make it work too with 587 and SSL?
To avoid changes on all accounts.

Thanks a lot.

Erwan
 
Are the services still listening on the correct ports? You should see something like this ..

# lsof -i :587
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
master 14357 root 106u IPv4 345192 0t0 TCP *:submission (LISTEN)

# lsof -i :993
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dovecot 23375 root 39u IPv4 345372 0t0 TCP *:imaps (LISTEN)
 
Thanks for your help.

# lsof -i :587
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
xinetd 1791 root 10u IPv6 9495 0t0 TCP *:submission (LISTEN)

# lsof -i :465
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
xinetd 1791 root 9u IPv6 9494 0t0 TCP *:urd (LISTEN)

# lsof -i :993
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
couriertc 13831 root 3u IPv6 157120000 0t0 TCP *:imaps (LISTEN)
 
No solution?
The last time I renewed my certificates I had some strange behavior too.
It turned out it removed the files where the certificates should have been.

I had a new certificate without a new key and used the Plesk interface to just change the active certificate.

To repair the mess that Plesk made of it I did some "plesk repair" and re-applied the certificate in the certificate.

I did the same procedure on 5 servers and they all had different behavior afterward.

At least run a "plesk repair all -y -v" and see if it finds any error.
When afterward applying the certificate using the Plesk interface press on each apply possible. I have a feeling it is possible Plesk is skipping some procedure or it doesn't handle an existing error of the configuration well.
That's where the repair comes in.

You can use this script I wrote some time ago to check the certificate:

Check certificate of a server
 
Last edited:
Back
Top