Problem with dial: dial tcp 172.22.0.2:11334: getsockopt: connection refused. about docker-mailserver

[jeboehm]

Hey @ictinc ,
hard to say what's wrong here. It seems that not all containers are started.
Please give the output of bin/production.sh ps. If there is a container that is exited or aborted, you can gather its logs by executing bin/production.sh logs SERVICENAME. SERVICENAME is something like mda, mta or filter.

[infostreams]

I'm fairly sure that this is because you have other containers or processes running that are already bound to one of the ports that the mailserver is trying to bind to. In my case, I already had a webserver open on port 80. Once I shut that process down, and waited a bit, this error disappeared.

[infostreams]

Ok, I got the error again (and again), and by looking at the logs it turned out that it was caused by the virus container that somehow refused to start correctly. It complained that it was out of date. That then lead to a cascade of log entries from other containers that depend on the virus scanner. So, I disabled the virus scanner. For my (very specific) purposes I don't need it anyway. After that all is fine and dandy.