- Mailman-users - lists.mailman3.org

Congrats on the instructions for installation on ubuntu, what about migration?
by Bill Oliver 09 Oct '24

09 Oct '24

So I went ahead and tried to install mailman3 on ubuntu 24.04 using the virtual environment approach. It worked like a charm. There were a very few glitches, all from me not reading the instructions closely (e.g. not replacing MY_SERVER with my server name, Doh). The whole thing, from start to finish was about two hours. I appreciate all y'alls efforts in this. The reason I'm doing this is that I'm having to migrate from a server that's going to be defunct soon. I've been running a mailman3 mailing list on that for a few years. Is there a tutorial/instructions on migrating data from an old system to a new one? It's actually not the end of the world if I don't get all the old emails transferred, but I'd like to get the email addresses of the participants moved over easily... I believe that I set it up in 2020, but did not do any version upgrades since then... Thanks! billo

3 3

Upgrade docker-mailman to v0.5.2
by Christopher 08 Oct '24

08 Oct '24

Hi Abhilash, I checkout the v0.5.2 for testing my upgrade from 0.4.6 and noticed, that the docker-image-version is still set to 0.4 in docker-compose.yaml. Is there any reason for it or should it be set to 0.5? I´m still using my good old mariadb. I did not find any upgrade-informations about breaking-changes. Do you have any experience with migrating from 0.4.6 to 0.5.2 on mariadb? Best regards Chrclaus

1 0

anomalous behavior
by donato＠molino.it 05 Oct '24

05 Oct '24

Hi, I installed mailman-full on debian 12. Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. I have three MLs: 1) example(a)example.com 2) test(a)example.com 3) hello(a)example.com For the n. 2 and 3 are fine, but 1 doesn't deliver. The configurations are identical for all 3: smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' I also enabled all debugging in mailman.cfg. But everything is fine Thanks Donato

3 5

Should I try to install mailman3 on Kubuntu 20.04?
by Bill Oliver 05 Oct '24

05 Oct '24

I have been a happy camper running mailman3 on a vps I rent from a vendor, running CentOS 7. CentOS 7 is past end of life, so I moving over to a new machine running Kubuntu 20.04 LTS. I have been searching the intertubes and have seen a bunch of people having headaches trying it. So... Is Ubuntu 20.04 cool with mailman3? Should I go ahead and give it a shot or use a different distro? Should I do the apt install, the virtualenv install, or try the docker install? thanks billo

4 5

reset bounce-scores?
by IEM Network Operation Center (IOhannes m zmölnig) 04 Oct '24

04 Oct '24

i'm running a mailman-3.3.8 instance, and would like to reset the bounce-score for a (number of) user(s). i searched the internet and this list's archives, but haven't found anything useful so far. due to a misconfiguration of our universities reverse DNS lookup, the bounce score of some users has rocketed in the last days - some users have already been unsubscribed because of that. could anybody please share how i can reset the bounce score? gfmasdr IOhannes ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

2 1

makemigrations --merge error after Debian upgrade
by Chupin Maxime 03 Oct '24

03 Oct '24

Hi, I upgraded my debian version, and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: ``` CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). To fix them run 'python manage.py makemigrations --merge' ``` So I tried `mailman-web makemigrations --merge` that ended with ``` PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' ``` There is no such a file in the migration directory. Any idea ? Thanks in advance, All the best Maxime Chupin

4 19

Confusing order of checkboxes in Postorius
by Markus Grandpré 02 Oct '24

02 Oct '24

Dear list, dear Mailman3 developers, dear Mark Sapiro, in Postorius under "Mass operations / Mass subscribe" we find the order of the checkboxes confusing: 1. Pre confirm 2. Pre approved 3. Pre Verified 4. Invitation We think it would be easier for us and our mailing list administrators to understand the interaction of these settings if they were displayed in the following order: 1. Pre confirm 2. Pre Verified 3. Pre approved 4. Invitation as in our opinion "Pre confirm" and "Pre Verified" belong together more than "Pre confirm" and "Pre approved". Incidentally, a typing error has crept into the term "Pre Verified". It should read "Pre verified". Yours sincerely, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 0

Mailman Core release
by Abhilash Raj 02 Oct '24

02 Oct '24

Hey Everyone! I am pleased to announce new release of Mailman Core 3.3.10. This includes both bug fixes and new features. A full list of changes can be found at the usual location[1]. This release includes a Breaking change and nntp runner no longer starts automatically in the default release. You can easily enable the runner by updating your `mailman.cfg`. See the release notes[1] for details on how. This release can be downloaded from PyPI[2] or using `pip install mailman==3.3.10`. For those interested in package signatures, both the source tarball and built wheel are available in Gitlab releases[3] along with their signatures. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://pypi.org/project/mailman/ [3]: https://gitlab.com/mailman/mailman/-/releases/v3.3.10 -- thanks, Abhilash Raj (maxking)

1 0

Default values for lists in Mailman 3
by Markus Grandpré 30 Sep '24

30 Sep '24

Dear list, I would like to activate the invitation setting for all lists as default. In Mailman 2.1 I have done this in the file </etc/mailman/mm_cfg.py>: DEFAULT_SUBSCRIBE_OR_INVITE = Yes How can I do this in Mailman 3? Can I also transfer other default values like: ... DEFAULT_SERVER_LANGUAGE = 'en' DEFAULT_SEND_REMINDERS = 1 DEFAULT_SUBSCRIBE_OR_INVITE = Yes DEFAULT_PRIVATE_ROSTER = 2 DEFAULT_ARCHIVE = Off DEFAULT_ARCHIVE_PRIVATE = 1 ... from the very same configuration file to Mailman 3? Is there a documentation of the default values for lists in Mailman 3? Best regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

2 4

Clearing webserver cache - Nginx
by Odhiambo Washington 29 Sep '24

29 Sep '24

I am having an ugly-looking https://mm3-lists.kictanet.or.ke/archives/ page because of cached content: ``` 2024/08/05 17:00:31 [error] 694#694: *9562 open() "/opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No such file or directory), client: 172.70.111.39, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.6dab123e4897.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" 2024/08/05 17:00:31 [error] 694#694: *9564 open() "/opt/mailman/mm/static/CACHE/css/output.158acc288604.css" failed (2: No such file or directory), client: 162.158.159.31, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.158acc288604.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" 2024/08/05 17:00:31 [error] 705#705: *9566 open() "/opt/mailman/mm/static/CACHE/js/output.3aaa7705d68a.js" failed (2: No such file or directory), client: 162.158.63.166, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/js/output.3aaa7705d68a.js HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" ``` That IP address appearing there is not my actual IP, but Cloudflare's, which is acting as proxy for the site. Having cleared MM3-web cache, is there anything else I can easily do (apart from disabling CF proxying) to help deal with the above issue? Or am I barking the wrong tree? -- 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 14