Henrik Rasmussen wrote:
Abhilash Raj wrote:
On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: each other, but Postfix is trying to deliver mail via lmtp to [172.19.199.2]:8024. Mailman's lmtp runner should be running and listening on port 8024. Either that is not the case or that port is not exposed to Postfix on IP 172.19.199.2. Right, that is what I was wondering, you verify that by using telnet on the specified IP and Port (172.19.199.2:8024). Yes, the postfix container listens on 172.19.199.2:8024 [root@postfix /]# nc -v 172.19.199.2 8024 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.19.199.2:8024. 220 mailman-core GNU Mailman LMTP runner 2.0
docker-compose ps lists all the running containers, do you see all the containers running? That also seem to be okay [root@lstapp01pl ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS
NAMES bddc80799b8c maxking/mailman-web:0.2 "docker-entrypoint.sh" 16 hours ago
Up 16 hours 8000/tcp, 8080/tcp
mailman-web be098b18aeca maxking/mailman-core:0.2 "docker-entrypoint.sh" 16 hours ago
Up 16 hours 8001/tcp, 8024/tcp
mailman-core c47fd8ccf19d postgres:9.6 "docker-entrypoint.sh" 16 hours ago
Up 16 hours 5432/tcp
mailman_database_1 699264501acd mailman3-mime_htmlizer "container-entrypoint" 16 hours ago
Up 16 hours 8080/tcp
postmime 90f381a74709 mailman3-postfix:v1.1 "./entrypoint.sh" 16 hours ago
Up 16 hours 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, 0.0.0.0:26->25/tcp postfixAnd netstat in the mailman-core container shows: Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 172.19.199.2:8024 0.0.0.0:* LISTEN`
You mentioned that Mailman is not receiving enough emails, do you get any emails from Mailman? I am trying to see if this is a perf problem or if Mailman's LMTP isn't reachable at all. Mailman do send out mails like when someone signs up for an account. Thanks to both.
And the runner is running: Sep 19 06:55:06 2019 (36) b'220 mailman-core GNU Mailman LMTP runner 2.0