Applicable to:
- Plesk Onyx for Linux
Symptoms
-
Plesk Premium Email extension by Kolab is used in Plesk.
-
Non-default SSL certificate is set to secure mail traffic at Plesk > Tools & Settings > SSL Certificates > Certificate for securing mail;
-
Email traffic still uses Plesk Default certificate: How to verify that SSL for IMAP/POP3/SMTP works and a proper SSL certificate is in use;
-
/etc/dovecot/private/dovecot.pemand/etc/dovecot/private/ssl-cert-and-key.pemfiles have different content:# md5sum /etc/dovecot/private/ssl-cert-and-key.pem /etc/dovecot/private/dovecot.pem
232dd0e418d073758357452c825eafc1 /etc/dovecot/private/ssl-cert-and-key.pem
5641ddb15e79c0fda43bcd7a5d5dc307 /etc/dovecot/private/dovecot.pem
Cause
This is a Plesk bug with ID PPPM-7808 which is planned to be fixed in future product updates.
Resolution
for Kolab version 16.3.0 and earlier:
-
Connect to the server using SSH.
-
Overwrite
/etc/dovecot/private/ssl-cert-and-key.pemwith content from/etc/dovecot/private/dovecot.pem:# cp -f /etc/dovecot/private/dovecot.pem /etc/dovecot/private/ssl-cert-and-key.pem
for Kolab version 16.3.3:
-
Connect to the server via SSH.
-
Restart guam service:
# service guam stop
# service guam start
Note: as a workaround for Kolab version 16.3.2 upgrade to version 16.3.3.
Comments
4 comments
Hello,
thanks for your solutions. We have a similar problem. When we activate SNI support we get certificate errors. According to the mail client the principal name or common name does not match the certificate. For this the global hostname of the mail server is used instead of the customer domain. Is there a workarround until Kolab Premium Mail supports the SNI Support?
Hello @Yannick Nesselhauf,
I would like to clarify that Plesk Premium Mail is yet to support SNI on IMAP.
As a workaround, consider using POP3 protocol.
so there is no way to use IMAP with kolab and SNI???? i realy need that, im losting my clients please help me i tryed that and not worked, also have you a link to how update kolab from 16.12.2-3 to the last one 16.3.3???????????
Hello Felipe Martini,
Version 16.12.x is newer that 16.3.x.
Currently, no workaround available. The issue is to be resolved on the extension authors' side.
Please sign in to leave a comment.