An error occured while communicating with the mail server

DeadMouse_btw

Hello everyone. I’ve encountered an issue where, upon trying to log into the web interface, I receive an error and cannot access it. What could be the problem? Could you please help explain?

Moreover, this issue doesn’t affect all accounts but only a few specific mailboxes.

Ganzjahresgriller

All Containers are up and running? Server OS and Mailcow is up to date? Please give us more information

DeadMouse_btw

Ganzjahresgriller Yes, all containers are running, and both the OS and Mailcow are updated to the latest version.

Ganzjahresgriller

Which web interface, Mailcow, SoGo?

DeadMouse_btw

Ganzjahresgriller SoGo

yes, error in sogo interface

Ganzjahresgriller

Can these accounts log in to the Mailcow interface?

Is this checkbox activated for the affected accounts?

DeadMouse_btw

Ganzjahresgriller Can these accounts log in to the Mailcow interface?

yes

[unknown] Is this checkbox activated

At the same time, I cannot access the second domain. All users, including myself, get similar errors. When connecting via the Outlook client, it connects to the server, but no emails appear. I believe this is due to the error mentioned.

this These are the permissions I have on the path /var/lib/docker/volumes/mailcowdockerized_sogo-web-vol-1, and I’m not sure if they are correct.

DeadMouse_btw

This is what is displayed when accessing the Sogo interface through the view source code.

Ganzjahresgriller

Is this checkbox activated for the affected accounts?

esackbauer

Please check the dovecot logs at that moment you try to access SOGo.
Do you have a reverse proxy? Make sure that all requirements are met i.e. rewrite rules etc.

DeadMouse_btw

esackbauer I figured out the problem. My chown was set to root:5000, instead of 5000:5000, which caused the mailbox to not open and the emails to not load. After changing the chown to 5000:5000 in /var/lib/docker/volumes/mailcowdockerized_vmail-vol-1/_data/domain, everything started working.