On Aug 17, 2021, at 11:37 AM, bob B <bader@cchmc.org> wrote:
I restarted the containers so the new/current ips are
core "IPAddress": "172.25.0.3", web "IPAddress": "172.25.0.4",
Here is the content of that file
docker exec -it mailman-core /bin/bash bash-5.0# cat /etc/mailman.cfg # This file is autogenerated at container startup.
<snip>
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.25.0.3 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg
Looking at your [mta] configs, it seems like incoming configs are correct, but outgoing configs aren’t. You have the Mailman Core binding to 172.25.0.3, which is the IP address allocated to it from Docker and it should be accepting connections on 172.25.0.3:8024.
The outgoing config will use the hard coded IP configs in the 0.3.11 release of the container images, but you can fix that by setting SMTP_HOST: 172.25.0.1 in both mailman-core and mailman-web container configurations in docker-compose.yaml file under “environment”. I am assuming that Postfix is listening on all interfaces (0.0.0.0, which is usually the case that I have seen, but something still that perhaps should be verified).
# mailman-extra.cfg
[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver # mailman-core hostname or IP from the Postfix server #lmtp_host: localhost lmtp_host: 127.0.0.1 lmtp_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: ########## smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: ########## bash-5.0#
This part is probably the one causing trouble, probably coming from what you added to mailman-extra.cfg. This overrides the configs above (which is right for incoming emails) ones. Mailman is binding to 127.0.0.1 inside the container, and that loopback interface isn’t accessible from anywhere outside the container itself, so you won’t be able to talk to it. It needs to listen either on 0.0.0.0 (all interfaces) or (at least, one of the) public IPs assigned to the container.
The fix is that you just want to delete the entire [mta] section of mailman-extra.cfg and restart the container. Do also setup the SMTP_HOST environment to fix that outbound email issue.
-- thanks, Abhilash Raj (maxking)