bob B writes:
Anyone have any ideas?
First, what docker configuration are you using? One supplied by the Mailman project? If not, you need to tell us more about what's going on. If so, are there any containers other than those running the Mailman suite (Mailman 3 core, Postorius, HyperKitty)?
In mydestination you have mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com I do not understand the "localhost.$mydomain" entry. I guess that's a Postfix-ism, but I can't find any documentation about it. You could try taking it out (this is a very random suggestion).
You say you have no /etc/postfix-mailman.cfg. Where are you looking
for it? That file will only exist in the container, not in the host
OS. (If it were in the host OS, it would be located somewhere like
/opt/mailman/core/postfix-mailman.cfg.) Try find /opt/mailman/core -name postfix-mailman.cfg, although "automatically" might mean it's
generated in the container when it starts. Abhilash would know, but
he doesn't seem to be available. I really don't think it's the issue
because I assume "bmimailmandr1" is the Docker container running
Mailman core. If so Postfix is connecting to the configured LMTP port
on localhost which is what it's supposed to do from the configuration.
Since the container's Postfix appears to be connecting to the right place but the connection is refused, that Mailman core may not be running.
For more help you'll have to wait for Abhilash.
Steve