Mail Server won't start due to Dovecot

robotdjman

I recently installed the MailCow docker stack to my ubuntu linux server and it has been working out great until when I tried to use SoGo to show my newly created mailbox. After logging in successfully, SoGo shows an error stating that it “failed to connect to mail server” or something like that. After digging through logs I found that SoGo is throwing an error saying it could not connect to IMAP4. After looking through dovecot logs, it seems that dovecot seems to be stuck on a curl operation and is showing a “Transient problem: timeout Will retry in 4 seconds. 8 retries left.” error over and over. After attaching to the container I can see that this seems to be an issue with DNS queries not resolving because attempting to to ping google within the dovecot container fails. Attempting to ping google within the unbound container (which from my knowledge handles all DNS traffic right?) works just fine. I have seen multiple other threads showing similar issues but still haven’t found a solution yet. Also I am new to this stack so if there is any other information that I could provide that would be helpful please let me know, and any help is appreciated! Thanks!

robotdjman

Below is the log for my dovecot-mailcow container:

`The user vmail is already a member of tty.

% Total % Received % Xferd Average Speed Time Time Time Current

                             Dload  Upload   Total   Spent    Left  Speed

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– 0:00:01 –:–:– 0Warning: Transient problem: timeout Will retry in 1 seconds. 10 retries left.

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0Warning: Transient problem: timeout Will retry in 2 seconds. 9 retries left.

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0Warning: Transient problem: timeout Will retry in 4 seconds. 8 retries left.

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0Warning: Transient problem: timeout Will retry in 8 seconds. 7 retries left.

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– 0:00:01 –:–:– 0Warning: Transient problem: timeout Will retry in 16 seconds. 6 retries left.

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0Warning: Transient problem: timeout Will retry in 32 seconds. 5 retries left.

0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– –:–:– –:–:– 0
0 0 0 0 0 0 0 0 –:–:– 0:00:01 –:–:– 0
0 0 0 0 0 0 0 0 –:–:– 0:00:02 –:–:– 0
0 0 0 0 0 0 0 0 –:–:– 0:00:03 –:–:– 0Warning: Transient problem: timeout Will retry in 64 seconds. 4 retries left.

Below is the log file for my unbound container:

`Signature ok

subject=CN = unbound-control

Getting CA Private Key

removing artifacts

Setup success. Certificates created. Enable in unbound.conf file to use

[1626759680] unbound[1:0] notice: init module 0: validator

[1626759680] unbound[1:0] notice: init module 1: iterator

[1626759680] unbound[1:0] info: start of service (unbound 1.13.0).

[1626759683] unbound[1:0] info: generate keytag query _ta-4f66. NULL IN
`