• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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