can't get mail into mailman3 in docker

bob B

2 Aug 2021 2 Aug '21

7:16 p.m.

I am trying to get mail into mailman in docker, I can send a test messages out from the container. But can't get mail in.

Any idea what I am missing?

mydomain.mydomain.com is substituted for the actual domain in the below output

My /etc/postfix/main.cf has

mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com

transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains

# Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no

my /opt/mailman/core/mailman-extra.cfg has

# 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_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: outbound-mail.mydomain.mydomain.com 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: admin@mydomain.mydomain.com

The instructions say "The configuration file /etc/postfix-mailman.cfg is generated automatically."

But I do not have that file is this the issue??

                       cat: /etc/postfix-mailman.cfg: No such file or directory

When I send mail to my domain to a list i created called 'test' I get

2021-08-02T13:33:08.666502-04:00 bmimailmandr1 postfix/cleanup[113557]: A068930294D8: message-id=<7C8556BA-156D-4A31-A64E-428C62D31AA1@mac.com> 2021-08-02T13:33:08.680953-04:00 bmimailmandr1 postfix/qmgr[113209]: A068930294D8: from=<testuser @bmail.com>, size=8275, nrcpt=1 (queue active) 2021-08-02T13:33:08.713683-04:00 bmimailmandr1 postfix/lmtp[113559]: A068930294D8: lost connection with localhost[127.0.0.1] while receiving the initial server greeting 2021-08-02T13:33:08.725326-04:00 bmimailmandr1 postfix/lmtp[113559]: connect to localhost[::1]:8024: Connection refused 2021-08-02T13:33:08.735727-04:00 bmimailmandr1 postfix/lmtp[113559]: A068930294D8: to=<test-join@mydomain.mydomain.com>, relay=none, delay=0.07, delays=0.03/0.01/0.03/0, dsn=4.4.1, status=deferred (connect to localhost[::1]:8024: Connection refused)

Show replies by thread

bob B

4 Aug 4 Aug

6:51 p.m.

Anyone have any ideas?

Stephen J. Turnbull

5 Aug 5 Aug

4:33 p.m.

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

bob B

6 Aug 6 Aug

1:26 p.m.

Thanks for the help, I do appreciate it.

I am using the docker images provided by the mailman project.

The containers are up and running

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9dbad91fe50b maxking/mailman-web:0.3 "docker-entrypoint.s…" 6 seconds ago Up 5 seconds 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web 7005bf66498e maxking/mailman-core:0.3 "docker-entrypoint.s…" 7 seconds ago Up 6 seconds 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core b5336023fa94 postgres:9.6-alpine "docker-entrypoint.s…" 7 seconds ago Up 7 seconds 5432/tcp dockermailman_database_1

I was looking on the docker host for "/etc/postfix-mailman.cfg." so that explains why it is not there.

I have been digging in more and it looks like the mailman-core is not processing or accepting mail or/and the connection gets lost. But I can send mail from mailman in docker.

On the docker host my /etc/postfix/main.cf has

transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains

My docker yaml has

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

But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024

2021-08-06T09:08:41.885213-04:00 dockerhost postfix/cleanup[109782]: D630B3083ED0: message-id=<4805A7DC-E100-4851-B1BB-E6C1806568A1@sender.com> 2021-08-06T09:08:41.896943-04:00 dockerhost postfix/qmgr[105559]: D630B3083ED0: from=<USER@sender.com>, size=8308, nrcpt=1 (queue active) 2021-08-06T09:08:41.949022-04:00 dockerhost postfix/lmtp[109783]: connect to localhost[::1]:8024: Connection refused 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test@mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting)

The /opt/mailman/core/mailman-extra.cfg files has

# 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_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: outbound-mail-server.######.### smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman]

bob B

2:38 p.m.

So doing some more digging it looks like the mailman-core is not listing on 8024 docker logs mailman-core shows

srv: AsyncServer = self.loop.run_until_complete(srv_coro)

File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete return future.result() File "/usr/lib/python3.8/asyncio/base_events.py", line 1463, in create_server raise OSError(err.errno, 'error while attempting ' OSError: [Errno 99] error while attempting to bind on address ('::1', 8024, 0, 0): address not available [root@bmimailmandr1 docker-mailman]# netstat | grep 1024

I also see nothing on port 8024 on the docker host (just incase that causes a conflict)

if I get into the mailman-core image I so not see anything listing on port 8024

bash-5.0# netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 mailman-core:8001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.11:34093 0.0.0.0:* LISTEN
udp 0 0 127.0.0.11:59940 0.0.0.0:*
Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node Path bash-5.0#

Stephen J. Turnbull

3:16 p.m.

bob B writes:

...

I am using the docker images provided by the mailman project.

OK.

...

The containers are up and running

CONTAINER ID PORTS NAMES 9dbad91fe50b 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web 7005bf66498e 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core b5336023fa94 5432/tcp dockermailman_database_1

That all appears correct. Most important, dockerhost says it is forwarding port 8024 to port 8024 on the mailman-core container.

...

I have been digging in more and it looks like the mailman-core is not processing or accepting mail or/and the connection gets lost.

Yes. It's possible the LMTP module is somehow broken in Mailman core but I can't imagine why that would be.

...

But I can send mail from mailman in docker.

Containers are much more strict about incoming connections than they are about outgoing connections to the dockerhost. Since Postfix handles outgoing mail for Mailman, but Mailman handles incoming LMTP itself, this is not particularly surprising.

...

On the docker host my /etc/postfix/main.cf has

transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains

These appear to be working correctly.

...

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

This is obviously the configuration that results in the container status output above. So that's working correctly.

...

But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024

Either for some reason the container is blocking this port or Mailman's LMTP server is AWOL. Aside from bugs, the only thing I can think of is that there's a configuration of LMTP to listen on a different port. This would either be in mailman.cfg, or in schema.cfg. But normally the default in schema.cfg is 8024, and there is no configuration of lmtp_port in mailman.cfg.

However, this below would indicate that it's set explicitly to 8024.

...

# 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_port: 8024 # Postfix server's hostname or IP from mailman-core smtp_host: outbound-mail-server.######.### smtp_port: 25 configuration: /etc/postfix-mailman.cfg [mailman]

So I'm stumped. As far as I can tell you have everything right, and mailman-extra.cfg should be included in such a way that it overrides settings in mailman.cfg and schema.cfg.

I guess you'll have to wait for Abhilash, or maybe Mark but I don't think Mark is much more familiar with the containers than I am.

Steve

Mark Sapiro

4:11 p.m.

On 8/6/21 6:26 AM, bob B wrote:

...

But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024

2021-08-06T09:08:41.885213-04:00 dockerhost postfix/cleanup[109782]: D630B3083ED0: message-id=<4805A7DC-E100-4851-B1BB-E6C1806568A1@sender.com> 2021-08-06T09:08:41.896943-04:00 dockerhost postfix/qmgr[105559]: D630B3083ED0: from=<USER@sender.com>, size=8308, nrcpt=1 (queue active) 2021-08-06T09:08:41.949022-04:00 dockerhost postfix/lmtp[109783]: connect to localhost[::1]:8024: Connection refused 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test@mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting)

The Connection refused is from trying to connect to localhost at IPv6 ::1. Then Postfix tries 127.0.0.1, gets connected and then Mailman's LMTP runner closes the connection. There may be more info from aiosmtpd in Mailman's smtp.log.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

bob B

6:28 p.m.

I see nothing for today when the error happens in /opt/mailman/var/logs/smtp.log

But the log has a bunch of these, but these stopped around the 4th

Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) connection lost

Mark Sapiro

8:03 p.m.

On 8/6/21 11:28 AM, bob B wrote:

...

I see nothing for today when the error happens in /opt/mailman/var/logs/smtp.log

But the log has a bunch of these, but these stopped around the 4th

Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) connection lost

These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times.

The fact that there is nothing in this log correlating with the Postfix message

2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test@mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting)

seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024.

I note you have

lmtp_host: localhost

in the [mta] section in mailman-extra.cfg. Try changing that to

lmtp_host: 127.0.0.1

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

matthew＠alberti.us

7 Aug 7 Aug

2:21 p.m.

I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core...

# EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg

This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation.

Matt Alberti

-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker

On 8/6/21 11:28 AM, bob B wrote:

...

I see nothing for today when the error happens in /opt/mailman/var/logs/smtp.log

But the log has a bunch of these, but these stopped around the 4th

Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) connection lost

These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times.

The fact that there is nothing in this log correlating with the Postfix message

seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024.

I note you have

lmtp_host: localhost

in the [mta] section in mailman-extra.cfg. Try changing that to

lmtp_host: 127.0.0.1

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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/

matthew＠alberti.us

2:27 p.m.

Sorry for the double-tap. Apparently https://github.com/maxking/docker-mailman/pull/441 changed the behavior that I said was the default.

We might need to see your docker-compose.yaml, with sensitive info removed, to know more about your setup.

Matt Alberti

-----Original Message----- From: matthew@alberti.us <matthew@alberti.us> Sent: Saturday, August 7, 2021 8:21 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker

This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation.

Matt Alberti

-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker

On 8/6/21 11:28 AM, bob B wrote:

...

I see nothing for today when the error happens in /opt/mailman/var/logs/smtp.log

But the log has a bunch of these, but these stopped around the 4th

Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) connection lost

These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times.

The fact that there is nothing in this log correlating with the Postfix message

seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024.

I note you have

lmtp_host: localhost

in the [mta] section in mailman-extra.cfg. Try changing that to

lmtp_host: 127.0.0.1

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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/

bob B

10 Aug 10 Aug

6:29 p.m.

/opt/mailman/core/mailman-extra.cfg. now has #lmtp_host: localhost lmtp_host: 127.0.0.1 lmtp_port: 8024 But but mail log shows 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user@user.com>, size=8181, nrcpt=1 (queue active) 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting) Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? ----------------------------- lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 ----------------------------- here is my docker-compose.yaml strip out -------------------------------- version: '2' services: mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core volumes: - /opt/mailman/core:/opt/mailman/ stop_grace_period: 30s links: - database:database depends_on: - database environment: - DATABASE_URL=postgres://@@@######$:@@@######$@database/mailmandb - DATABASE_TYPE=postgres - DATABASE_CLASS=@@@######$.database.postgresql.PostgreSQLDatabase - HYPERKITTY_API_KEY=@@@######$ ports: - "127.0.0.1:8001:8001" # API - "127.0.0.1:8024:8024" # LMTP - incoming emails networks: mailman: mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - MAILMAN_ADMIN_USER=@@@######$ - MAILMAN_ADMIN_EMAIL=@@@######$@@@@######$ - SERVE-FROM_DOMAIN=@@@######$.@@@######$.org - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - DATABASE_TYPE=postgres - DATABASE_URL=postgres://@@@######$:@@@######$@database/mailmandb - SECRET_KEY=@@@######$ - HYPERKITTY_API_KEY=@@@######$ ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: database: environment: - POSTGRES_DB=@@@######$ - POSTGRES_USER=@@@######$ - POSTGRES_PASSWORD=@@@######$ image: postgres:9.6-alpine volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: networks: -------------------------------- So not sure where to go next?

Mark Sapiro

7:24 p.m.

On 8/10/21 11:29 AM, bob B wrote:

...

/opt/mailman/core/mailman-extra.cfg. now has #lmtp_host: localhost lmtp_host: 127.0.0.1 lmtp_port: 8024

But but mail log shows 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user@user.com>, size=8181, nrcpt=1 (queue active) 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting)

Also to clarify the images no longer have hard coded ips so I should NOT DO this correct?

lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25

I think that's correct, but I'm at a loss for helping further.

Hopefully @maxking will be able to help.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

bob B

11 Aug 11 Aug

4:52 p.m.

I wonder is there is some issue or compatible setting with SMTp on my host and lmtp in the docker image?

I am running cent os 7 with -bash-4.2$ postconf mail_version mail_version = 2.10.1 -bash-4.2$

maxking, any ideas?

matthew＠alberti.us

5:10 p.m.

Bob, Can you run the command "sudo docker logs mailman-core" and see what the end of that says? Another good command to run is "sudo docker ps" and make sure the mailman-core container is actually running.

-----Original Message----- From: Mark Sapiro <mark@msapiro.net> Sent: Wednesday, August 11, 2021 1:25 AM To: mailman-users@mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker

On 8/10/21 11:29 AM, bob B wrote:

...

/opt/mailman/core/mailman-extra.cfg. now has #lmtp_host: localhost lmtp_host: 127.0.0.1 lmtp_port: 8024

But but mail log shows 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user@user.com>, size=8181, nrcpt=1 (queue active) 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting)

Also to clarify the images no longer have hard coded ips so I should NOT DO this correct?

lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25

I think that's correct, but I'm at a loss for helping further.

Hopefully @maxking will be able to help.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

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/

bob B

12 Aug 12 Aug

2:30 p.m.

so I added "- MTA=postfix" to the yaml file

services: mailman-core: . environment: - MTA=postfix ..

docker loks do not shoe a postscript error now

Postgres is up - continuing Using Postfix configuration Found configuration file at /opt/mailman/mailman-extra.cfg

BUT I still get this on the hosts mail log

[127.0.0.1]:8024, delay=0.16, delays=0.08/0.04/0.04/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting)

I thought that setting would fixed it (thanks Matthew) but apparently not

Not sure what do do next? should I blow it all away and re install? What is that procedure?

bob B

13 Aug 13 Aug

8:20 p.m.

I tried the rolling release of docker mailman containers, still had same issue
I upgrade postfix on the host from 2.10.X to 3.6?, still had same issue

I love vmware so i could roll back the host vm to undo those tests :)

But I am still stuck. Anyone have any ideas? Anyone else running this on Centos 7 with Docker

bob B

8:22 p.m.

Sorry, i meant I upgraded smtp on the host from 2.10 to 3.something

1010

Age (days ago)

1021

Last active (days ago)

List overview

Download

17 comments

4 participants

participants (4)

bob B
Mark Sapiro
matthew＠alberti.us
Stephen J. Turnbull