Sorry for stepping in this very late.
The problems here are possibly due to the recent changes in the docker-mailman related to removal of static IPs in the container images. The changes have been reported working by some folks, but i know that they aren’t really using the docker-compose.yaml provided in the repo or have highly customized versions of those so the combination of both might be broken.
It is also a problem that the documentation isn’t versioned properly to signify the difference that has been made in the repo since the last released version of the container image :(
Either way, can you share the contents of /etc/mailman.cfg from inside the mailman-core container? That is most definitive source of truth for what actually configuration is being passed to Mailman Core to infer which actual host:port is the LMTP runner listening to and if the configuration being passed to it are what we expect.
Abhilash
On Aug 17, 2021, at 7:17 AM, bob B <bader@cchmc.org> wrote:
Ok, I took a step back and started fresh... So the issue appears to be that mailman-core docker image is not replying on port 8024.
I did a packet capture and it shows (172.23.01 is the gateway for the docker network on the host, 172.23.03 is the IP of mailman-core when I did the capture)
1 2021-08-16 14:15:14.865053 172.23.0.1 172.23.0.3 TCP 74 34066 → 8024 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=985607751 TSecr=0 WS=128 2 2021-08-16 14:15:14.865084 172.23.0.3 172.23.0.1 TCP 54 8024 → 34066 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
The above show the docker host sending/relaying mail to mailman-core, but mailman-core does not acknowledge on port 8024.
The images are up i.e
58923db6fb9f maxking/mailman-core:0.3 "docker-entrypoint.s…" 26 minutes ago Up 25 minutes 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core
Docker yamel has the port setup (8024)
services: mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core . . ports:
- "127.0.0.1:8001:8001" # API
- "127.0.0.1:8024:8024" # LMTP - incoming emails networks: mailman:
I can nc to the ports for docker web & 8001 on core and they are listening
But 8024 is not responding
#>docker-mailman-host]# nc -v 172.23.0.4 8000 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.4:8000. ^C #>docker-mailman-host]# nc -v 172.23.0.4 8080 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.4:8080. ^C #>docker-mailman-host]# nc -v 172.23.0.3 8001 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.3:8001. ^C
#>docker-mailman-host]# nc -v 172.23.0.3 8024 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connection refused
Docker logs show postfix is up on mailman-core
sudo docker logs mailman-core List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+---------+----------+------------+------------+--------------------- mailmandb | mailman | UTF8 | en_US.utf8 | en_US.utf8 | postgres | mailman | UTF8 | en_US.utf8 | en_US.utf8 | template0 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + | | | | | mailman=CTc/mailman template1 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + | | | | | mailman=CTc/mailman (4 rows)Postgres is up - continuing Using Postfix configuration Found configuration file at /opt/mailman/mailman-extra.cfg HYPERKITTY_URL not set, using the default value of http://mailman-web:8000/hyperkitty
Any ideas is there anything else I can do to troubleshoot? Is the issue with the mailman-core image?
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)