On 6/12/25 19:48, Mark Sapiro wrote:
That is not correct. Postfix should receive the initial connect and smtp for the list and then transport_maps should tell it to relay the message via lmtp to the configured lmtp_host and lmtp_port (127.0.0.1:8024 per your previously posted mailman.cfg). You have also posted that Postfix main.cf contains
transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp
What is the content of that file? In particular does it contain
mylists@lists.yyy.com lmtp:[127.0.0.1]:8024
Yes, that's exactly the case.
and is the timestamp of /var/lib/mailman3/data/postfix_lmtp.db >= that of /var/lib/mailman3/data/postfix_lmtp, and have you restarted/reloaded Postfix since updating main.cf? And, is Mailman core running and listening on port 8024?
# ls -rtl total 296 -rw-rw---- 1 list list 270336 Jun 8 21:58 mailman.db -rw-rw---- 1 list list 1123 Jun 12 08:43 postfix_lmtp -rw-rw---- 1 list list 367 Jun 12 08:43 postfix_domains -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_lmtp.db -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_domains.db
# lsof -i :8024 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python3 1146914 list 23u IPv4 78503106 0t0 TCP localhost:8024 (LISTEN)
I always restart mailman3 after changing main.cf
if there is any interest, postfix_domains contains this line:
lists.yyy.com lists.yyy.com
Florian.