Meet ONLYOFFICE Docs Cloud, complete office software as a service
Meet ONLYOFFICE Docs Cloud

Connection problem via mail client like Mozilla Thunderbird

On a Linux Ubuntu 20.04 LTS VM I installed Onlyoffice Workspace Community Ver. 12.1.0.1760 executed via script to which at runtime I answered with Y (Docker).
I have correctly configured the mail serverver and all the necessary parameters such as SPF, MX, DKIM.
I can successfully send and receive mail messages through the Onlyoffice mail client, but I cannot set up mail accounts on third party email clients such as Mozilla Thunderbird.
I am sure that the parameters entered are correct, and Thunderbird also detects them automatically, but as soon as I try to save I am returned a security message regarding the SSL certificate and does not allow me to continue.
The SSL certificate that I generated through the Control Panel with Let’s Encrypt exists and works regularly if I access Onlyoffice from the Browser.
It is as if the same certificate is not used for Dovecot and Postifix or similar services.
Ports 143, 993, 465 and 587 are regularly open on both the Linux VM and the corporate Firewall.
Any suggestions?

Hello @maxbon

I can successfully send and receive mail messages through the Onlyoffice mail client, but I cannot set up mail accounts on third party email clients such as Mozilla Thunderbird.

Please reproduce the issue and make screenshot of an error entry. After that please provide us with whole Community server logs folder. It’s located here: /app/onlyoffice/CommunityServer/logs/
Do I understand it right that Mail server installed on the same server as other Workspace components?

Post from Alexandre

Hello, sorry for the late reply.

Please follow my steps. You have to copy Community server certificates to Mail server container and restart it.
Files (onlyoffice.crt and onlyoffice.key) are located on the host here: /app/onlyoffice/CommunityServer/data/certs

Please copy them to this folder: /app/onlyoffice/MailServer/data/certs/
And change their names to mail.onlyoffice.crt and mail.onlyoffice.key
After that, restart the Mail server container.

NB! We recommend to prepare whole server backup before any server-side actions

The issue is solved.