On 2024/08/02 19:02, Mark Sapiro wrote:
On 8/2/24 09:43, Roland Giesler via Mailman-users wrote:
Ah, so I just have to figure out why the LMTP runner is not running.
Stop Mailman core and then start it. You must stop and then start as opposed to restart.
If lmtp runner is not running after that check /var/log/mailman3/mailman.log for possible reasons. You can also check that log for reasons why it isn't currently running.
You can also check /var/log/syslog* for events like out_of_memory that might have killed it.
I do now have the lmtp runner on port 8024.
# netstat -tunap | grep 8024 tcp 0 0 192.168.161.103:8024 0.0.0.0:* LISTEN 46730/python3
In mailman.cfg I set it to listen on the LAN address instead of 172.0.0.1, since I'm expecting mails from my external MTA server.
In the logs of the MTA I see this however: warning: do not list domain fast.za.net in BOTH virtual_mailbox_domains and relay_domains
Mailman creates these entries, but postfix doesn't like it. I don't see any mail delivered to the mailman yet. Is this the problem?
In the MTA postfix main.cf:
relay_domains = hash:/etc/mailman3/data/postfix_domains
cat /etc/mailman3/data/postfix_domains # AUTOMATICALLY GENERATED BY MAILMAN ON 2024-08-05 07:20:17 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own.
fast.za.net fast.za.net
and also
local_recipient_maps=$virtual_mailbox_maps, hash:/etc/mailman3/data/postfix_lmtp
cat /etc/mailman3/data/postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2024-08-05 07:20:17 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own.
# Aliases which are visible only in the @fast.za.net domain. test@fast.za.net lmtp:[192.168.161.103]:8024 test-bounces@fast.za.net lmtp:[192.168.161.103]:8024 test-confirm@fast.za.net lmtp:[192.168.161.103]:8024 test-join@fast.za.net lmtp:[192.168.161.103]:8024 test-leave@fast.za.net lmtp:[192.168.161.103]:8024 test-owner@fast.za.net lmtp:[192.168.161.103]:8024 test-request@fast.za.net lmtp:[192.168.161.103]:8024 test-subscribe@fast.za.net lmtp:[192.168.161.103]:8024 test-unsubscribe@fast.za.net lmtp:[192.168.161.103]:8024
Then there's: virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf
cat /etc/postfix/virtual-mailbox-domains.cf dbpath=/home/user-data/mail/users.sqlite query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 FROM aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM auto_aliases WHERE source LIKE '%%@%s'
When I run that query in sqlite3, it returns no records, so I'm not sure how this is supposed to work. %s to me means that first argument, so is this used in python and then %s is the argument sent to this query?
The bottom line of this all is that a new signup message that I reply to is being received by box2.gtahardware,co.za, but not by mailman3 and I cannot find the point where it fails in the logs.