blup@fortytwo.ch writes:
I installed mailman3 on a server where mailman21 was installed before. Newly created mailinglists work fine. But if I create mailinglists with a name that was previously used on mailman21 nothing works
Your logs below show that *something* is working because Mailman 3 is logging the incoming message.
(same behaviour with and without import of old configs and archives; no logs).
Archives should have nothing to do with it (except that if there are no members with delivery enabled, you might see posts delivered to the archives, but nothing in outgoing SMTP logs).
I don't understand what you mean by "without import of old configs". Do you mean you just create the list with the old name? Did you do any further configuration and set up of that list?
I purged all old mailman21 config and data
This should not be necessary. Mailman 2 and Mailman 3 can even happily coexist on the same host as long as you don't try to reuse /etc/mailman, /usr/lib/mailman and /var/lib/mailman (or whatever they happen to be) from Mailman 2 for Mailman 3.
and also old postfix aliases (or at least I do think so).
Since Mailman 3's SMTP logs below show incoming LMTP for both lists, I don't think there's a problem with Postfix.
If I send a mail to old list list1@a.b and new list list2@a.b I get the following logs
Logs edited for brevity:
/var/log/mail.log 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2@c.a.b>, status=sent (250 Ok) 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1@c.a.b>, status=sent (250 Ok)
So this is one message with two lists as addressees.
/var/log/mailman3/smtp.log Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list2@c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list1@c.a.b>'
Postfix has the right alias, since it's sending messages for list1 to Mailman's LMTP port. It also appears list1 was accepted here.
Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() Aug 21 22:17:46 2022 (936) smtp to list2@a.b for 1 recips, completed in 3.14 seconds
I don't see any good reason to believe either Postfix or Mailman 3 is misbehaving from the above.
How can I get more info on why the mail for list1 isn't processed?
First check the queues (normally /var/lib/mailman/qfiles/*/* where the first * is a wildcard for list names and the second is a wildcard for message objects, the '/var/lib' part may be different in your installation) for a "stuck" message. Second, have you checked the other Mailman logs for information? Third, are both lists visible in the message header as addressees?
Is the 'outgoing' qrunner still running? (ps ax | grep outgoing) Are there any subscribers with delivery enabled on 'list1'? Is list1 configured to accept only member posts? If so, is the sender a member whose posts are accepted?
Is there a sibling list setting that would prevent the message from being sent to the same address if it is on both lists? Are the spam filter settings the same?
How can I diff the config between list1 and list2 from the command line?
This doesn't seem to be implemented. I need to prep for some meetings, but here's the basic strategy I'd follow:
- Use "mailman withlist -i -l list1". This puts you in a Python interpreter command line.
- Next "attrs = dir(m)" to get the list attributes as a list.
- Check "attrs" for things like the roster of subscribers that you're not interested in printing out, and delete them.
- Open a file as 'f', then loop over attr in attrs using "print(f'{attr}: {getattr(m, attr)}', file=f)".
Then do the same for list2 (sorry, I don't know if there's a way to change lists in the middle of withlist), and diff the two files. No promises that will work exactly as written above, but it should be close. If you don't get it quickly, feel free to come back and ask for more help, I just am out of time and wanted to at least give you the basics.
Steve