- Mailman-users - lists.mailman3.org

share directories between postfix and mailman 3
by Thomas Schachtner 24 Jan '24

24 Jan '24

Hi there, I think I have (finally) set up a working instance of mailman 3 on a host separate from the companion postfix mail server actually sending out the mails. One server (postfix) is directly in the internet and the other one is in an internal network not directly reachable from the internet (but connected using a reverse proxy). The services on the hosts are available to one another (i. e. the postfix server is reachable using 127.0.0.1:25 from mailman and mailman is reachable using 127.0.0.1:8024 from postfix using a permanent ssh tunnel betwenn the two hosts). I think that this solution could work quite reliably... (at least I hope so.) But that's not the full deal. Postfix needs access to some hashed configuration files containing the transport maps and the domains of the mailman installation, and mailman needs the contents of the postfix configuration file. As a quick and dirty solution, I've established a process which periodically copies the /var/lib/mailman3 directory from the mailman box to the postfix box using rsync. But I would like to have a more professional solution, like a directly shared directory between both. I did not yet find any suggestions on how to achieve this. Are there any best practices recommendations? I already tried sharing the directories using sshfs, but that did not work. I connected the remote directory postfix.example.com:/var/lib/mailman3 to my local directory /var/lib/mailman3 using sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 This seemed to work pretty fine, as all files and directories seemed to be available, but when starting mailman 3, the following error message was shown: FileExistsError: A race condition might have happened. /var/lib/mailman3 actually exists and is not a directory. Any idea why this message is shown? So, is it a bad idea to use sshfs? Do I have to install an NFS server? But I am not sure if sharing directories using NFS across the Internet is a good idea... Any suggestions? Best regards Tom

3 6

Re: Process on migrating mailman
by Odhiambo Washington 24 Jan '24

24 Jan '24

On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > About 500 list. Not sure how to check size of the archives. > > On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > >> >> >> On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> >> wrote: >> >>> Any suggestion on how to migrate mailing list and archirve with >>> diffirent server and domain. For the mailing list from >>> sample.domain1.example.com to sample.domain2.example.com >>> >>> Old Mailing list >>> Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) >>> [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] >>> Domain Domain1.example.com >>> >>> New Mailing list >>> Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) >>> [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] >>> Domain domain2.example.com >> >> >> >> How many lists? How big are the archives? >> >> Looking at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, >> it seems like it's not a trivial exercise. >> >> However, I am wondering about the consequences of: >> 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then >> re-importing >> 2. editing settings.py and webserver config to reflect the DOMAIN2 >> 3. reconfiguring your MTA to handle list mails using the DOMAIN2 >> >> I am imagining a virtualenv type of installation. >> > The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… . -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 3

log rotation for bounce.log
by Quanah Gibson-Mount 22 Jan '24

22 Jan '24

I noticed that our smtp.log and bounce.log files haven't been rotated in years. I see the reason for smtp.log not being rotated is due to <https://gitlab.com/mailman/mailman/-/issues/931>. Does this same issue affect bounce.log or is it safe to rotate similar to mailman.log?

2 1

Extract a list of the lists and the administrators who manage it
by pau.baiges＠csuc.cat 22 Jan '24

22 Jan '24

Hello, Is there a way to extract all the lists and show the administrators who manage those lists? Thanks!

3 2

emails to list missing from archive after upgrade
by Quanah Gibson-Mount 19 Jan '24

19 Jan '24

So next issue post upgrade: I sent three emails to one of the lists today. All of them went to the list, as I got copies of each one, and the headers clearly show them coming from the list. However, when I go look at the archives for the list, they don't show up at all. And it's been over 8 hours since I sent them. --Quanah

2 3

Delivery to mail@domain.tld failed with code 444, [Errno 111] Connection refused
by christopher.claus＠tgcamberg1848.de 19 Jan '24

19 Jan '24

Hi together, I´m using Mailman3.3.9 and postfix in docker containers seperatly. Everything worked fine since this afternoon. The error occurs, after postfix transports an incoming mail to mailman. After processing the mail, sending to all recepients failed >> Delivery to mail(a)domain.tld failed with code 444, [Errno 111] Connection refused I checked the configuration of postfix and added a wide IP-range to mynetworks: postfix-main.cf mynetworks = mailman-core tgc_mailman_core t 127.0.0.0/8 [::1]/128 [fe80::]/64 172.18.0.0/16 172.21.0.0/16 [2001:8d8:1800:283]/64 172.0.0.0/24 relay_domains = $mydestination #smtpd_sender_restrictions = reject_unknown_sender_domain,reject_unknown_reverse_client_hostname smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_relay_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination smtpd_recipient_restrictions = permit_sasl_authenticated check_recipient_access hash:/etc/postfix/filtered_domains permit_mynetworks reject_unauth_destination smtpd_data_restrictions = reject_unauth_pipelining Does anyone have a clue for me as to why delivery to Postfix is failing? My last change a couple of days ago was adding an public ipv6-address to the host. But docker still works without IPv6. I thought about client-identification issues between maiolman-core and postfix but did noch find anything to fix ... Best regards, Christopher

2 2

moving list from mm3 -> mm3
by Jens Günther 19 Jan '24

19 Jan '24

Hey there, I'm still trying to figure out, how to move a bunch of lists from one mm3-instance to another. If somebody has a working solution, I would be really glad to hear from it. I came across this thread, but I don't think it tackles my question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (or maybe I missed the right parts) We have equal setups and versions: - maxxking docker install 0.4.5 - Core 3.3.8 - API 3.1 - Postorius 1.3.8 ## Config So I found the possibility to get the config of a list via REST-API: curl -u restadmin:restpass localhost:8001/3.1/lists/$short.$domain/config | jq > short.domain This is a nice collection of the configuration of a certain list. Does anybody know how I would get this data back to the newly created list in the second working mm3-instance? Shouldn't it be possible via POST command? I thought of something like: curl -u restadmin:restpass -d @short.domain -H "Content-Type: application/json" localhost:8001/3.1/lists/&short.&domain/config But it returns {"title": "405 Method Not Allowed"} and I don't know where to look in the docs, since it shows almost always a way through mailman shell. Here I found something about POST: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but how would it work exactly? ## Members, moderators, owners To export all members I normally run within mm-core-container as user mailman the following command: mailman members &short.&domain > &short.txt To fill them back in, it can be done in Postorius (or is there a way through API?). What I would love to know is how to get out Owners of the corresponding lists and reimport them in the new one (which will be the same at the end :-D but different instance). ## registered users This part is somehow tricky, since I have no clue how to do it. Some of the mailinglist-admins don't want to bother their list-owners again with registering newly on the other system. Is there a way to export all users (I think I found them in the DB in the table auth_users, somehow in combination with account_emailaddress) and get them over to the new instance (actually I just need part of them, but that's another question that I might solve lateron on my own). Maybe the answer is already here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)? Thank you in advance, I hope it's not too much or too nooby :-) Jens.

3 10

All users getting disabled after upgrade of mailman3
by Quanah Gibson-Mount 19 Jan '24

19 Jan '24

Hello, We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method). Now everyone's having their addresses disabled due to "bounce" errors. This is odd, because I'm disabled, even though I received the 2 emails I sent to the list today (and that's the only list traffic today). I used the mailman shell command from <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> to see who has been disabled. I had to make one fix to it, it should be m.list_name not mlist.list_name. Confirmed that dozens of valid users have had their sub disabled. In the logs I see: Jan 18 19:25:17 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score = 1. Jan 18 19:37:11 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score = 2. Jan 18 19:37:11 2024 (952) Disabling delivery for quanah(a)fast-mail.org on list openldap-technical.openldap.org by bounce Jan 18 19:37:11 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score 2 >= threshold 2, disabling delivery. Jan 18 10:05:42 2024 (938) Peer: ('127.0.0.1', 36100) Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) handling connection Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'LHLO hypatia.openldap.org' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'MAIL FROM:<openldap-commit-bounces(a)openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) sender: openldap-commit-bounces(a)openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'RCPT TO:<openldap-commit-owner(a)openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) recip: openldap-commit-owner(a)openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'DATA' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'QUIT' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) connection lost Jan 18 10:05:42 2024 (938) Connection lost during _handle_client() Jan 18 10:05:45 2024 (940) <170557233590.937.7274928299237969540(a)hypatia.openldap.org> post to openldap-commit(a)openldap.org from openldap-commit-owner(a)openldap.org, 20265 bytes Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376(a)hypatia.openldap.org> low level smtp error: [Errno 111] Connection refused Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376(a)hypatia.openldap.org> delivery to quanah(a)openldap.org failed with code 444, [Errno 111] Connection refused But... postfix is working fine, and I've had hundreds of emails generated *by* mailman about it disabling people due to bounces. Thoughts on how to proceed appreciated. Regards, Quanah

2 4

Splitting hosts: mta&core vs postorius
by Ruth Ivimey-Cook 18 Jan '24

18 Jan '24

I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. I've checked the settings and I don't think I have misconfigured postorius. Is it possible that the bad url is being passed from core to postorius in some way and reused without changing the host? In the config at present, both hosts are visible to the browser, and each host can communicate with the other. Any ideas on how to pin down the problem better? Ruth

6 31

Process on migrating mailman
by Mark Labeste 18 Jan '24

18 Jan '24

Any suggestion on how to migrate mailing list and archirve with diffirent server and domain. For the mailing list from sample.domain1.example.com to sample.domain2.example.com Old Mailing list Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] Domain Domain1.example.com New Mailing list Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] Domain domain2.example.com

3 3