- Mailman-users - lists.mailman3.org

Missing Base64 encoding from control message reply
by lists-mailman3＠janaberger.de Aug. 15, 2025

Aug. 15, 2025

Dear all, I have a setup with GNU Mailman 3.3.8 where a user tried to subscribe. When replying to the "confirm" message, the user received a completely garbled response, like so: N�z˥��ʋ�zf��&��j��u�[zZ0:��v��,j�z֢��k�e�0 4Dҹ��r�^b��r�ߊ��*'��yם��{ax�L�X��0:��v��,j�z֢��k�d�m�-��zz�rn��l]y+��-E�( �^N��'��M��tۯ��Mz��^i��׮��}�o�\ӷ��6sN�zf��ݮ��r��z˥��b�{h��݉��f�r�ne== (The line above contains numerous unprintable characters, etc.) The user then forwarded the .eml file to me, which clearly shows the contents of the mail as plain text while being announced as base64 (Content-Transfer-Encoding: base64): START OF EML Return-Path: <LISTNAME-bounces(a)lists.DOMAIN.COM> Received: from DOMAIN.COM ([144.76.173.241]) by mx-ha.USERDOMAIN.NET (mx06 [IP]) with ESMTPS (Nemesis) id 1M27WV-1qhRFk39Sr-00AQcR for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:37 +0200 Received: from localhost (localhost.localdomain [127.0.0.1]) by DOMAIN.COM (Postfix) with ESMTP id 4058B3BD5EEF for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:37 +0200 (CEST) Received: from DOMAIN.COM ([127.0.0.1]) by localhost (DOMAIN.COM [127.0.0.1]) (amavis, port 10024) with ESMTP id x0ngnlRnGraH for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:37 +0200 (CEST) Received: from [IP] (unknown [IP]) by DOMAIN.COM (Postfix) with ESMTP id DC8603BD5EEE for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:36 +0200 (CEST) Subject: =?utf-8?q?The_results_of_your_email_commands?= From: LISTNAME-bounces(a)lists.DOMAIN.COM To: USER(a)USERDOMAIN.NET Content-Transfer-Encoding: base64 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-ID: <169531623416.29.5762261018677554285@mailman-core> Date: Thu, 21 Sep 2023 17:10:34 +0000 Precedence: bulk X-Mailman-Version: 3.3.8 List-Id: <LISTNAME.lists.DOMAIN.COM> List-Help: <mailto:LISTNAME-request@lists.DOMAIN.COM?subject=help> List-Owner: <mailto:LISTNAME-owner@lists.DOMAIN.COM> List-Subscribe: <mailto:LISTNAME-join@lists.DOMAIN.COM> List-Unsubscribe: <mailto:LISTNAME-leave@lists.DOMAIN.COM> Envelope-To: <USER(a)USERDOMAIN.NET> X-Spam-Flag: NO The results of your email command are provided below. - Original message details: From: USER <USER(a)USERDOMAIN.NET> Subject: Re: Your confirmation is needed to join the LISTNAME(a)lists.DOMAIN.COM mailing list. Date: Thu, 21 Sep 2023 19:10:26 +0200 Message-ID: <3c1eaaf8-1677-432f-b9dc-07f18902c06c(a)email.android.com> - Results: Confirmation token did not match - Done. END OF EML Is this possibly a bug in Mailman? Any ideas on what else could be causing this?

5 13

help with startup scripts
by Piet Barber Aug. 15, 2025

Aug. 15, 2025

Hello, I'm trying to get mailman3 working on Ubuntu. I'm following these instructions: https://docs.list.org/en/latest/install/virtualenv.html#setup-virtualenv I've gotten to the point where I can successfully su - to the mailman3 user, and manually start the mailman3 process with the startup command. However, when I follow the systemctl startup scripts as per the instructions at the URL above, it get stuck in the startup ... forever Starting from the command line works great! (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman start Starting Mailman's master runner Generating MTA alias maps (venv) mailman@arcus:~$ (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman status GNU Mailman is running (master pid: 47815) But when I try to start it from systemctl, it just hangs forever... root@arcus:/etc/nginx# systemctl start mailman3 If I background it, and check it out from systemctl status, I get that It's stuck in the startup mode. root@arcus:/etc/nginx# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: activating (start) since Wed 2025-08-13 23:12:05 UTC; 29s ago Process: 49024 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Tasks: 17 (limit: 4605) Memory: 878.0M (peak: 878.5M) CPU: 11.030s I've tried this with and without the forking entry in the systemctl configuration. No matter what I do, it's stuck in the ... Active: activating (start) since Wed 2025-08-13 23:13:37 UTC; 27s ago What am I missing? root@arcus:/etc/nginx# cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=syslog.target network.target postgresql.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid User=mailman Group=mailman Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop Restart=on-failure RestartSec=15 [Install] WantedBy=multi-user.target root@arcus:/# -- Piet Barber http://www.pietbarber.com/ http://blog.pietbarber.com/

4 6

db migration from mailman3.2.2 to mailman3.3.9 (sqlite3 to postgres16)
by Peter Thornton Aug. 13, 2025

Aug. 13, 2025

Hello, I know this question comes up here periodically, but I am having some trouble performing a data migration from an older version of mailman3 to a more recent one. We have a legacy environment with: mailman3.2.2 postorius 1.2.4 hyperkitty 1.2.2 there are two sqlite3 dbs for mailman core and mailman web. I've staged a new environment using the docker-mailman project with the following: mailman3.3.9 postorius 1.3.10 hyperkitty 1.3.8 there is a single postgres db here for both core and web. I've tried migration a few different ways, using pgloader, and also with some manual python scripts. Data is definitely not my forte, but I am struggling to get a working instance. I am running into several issues such as foreignkeyviolations, datatype mismatches, unique PK errors, etc.. Does anyone out there have a prescriptive process for this migration, or a suggestion for workflow/tooling that has worked in a similar upgrade process? Thanks! -Peter

2 1

default processing
by Sam Darwin Aug. 13, 2025

Aug. 13, 2025

Notice the repeated use of the word "default" (which is a great word, by the way). This creates confusion: Default action to take when this member posts to the list. List default -- follow the list's default member action. Default Processing -- run additional checks and accept the message. Due to backwards compatibility it may be difficult to change. But if it could be modified, how about: Action to take when this member posts to the list. List default -- follow the list's default member action. Standard Processing -- run additional checks and accept the message. In other words, in the context of message acceptance, the word "default" should have a certain selected meaning. Then make extra effort to choose other words for other actions, as proposed here, "Standard Processing", or something similar.

3 8

Website 404 error
by peter＠pi4cc.nl Aug. 11, 2025

Aug. 11, 2025

Hello I'm running Debian 12 with the latest version and installed mailman3 via apt install-mailman3-full. Everything works, I'm using MySQL as the database. There's something strange, and I can't find a source/solution. When I first access the website domain.nl/mailman3, it's redirected to domain.nl/mailman/postorius/lists/, resulting in a 404 error (3 after mailman is missing). When I accessed it a second time with the same link (domain.nl/mailman3), I was redirected to domain.nl/mailman3/postorius/lists and the welcome page appeared. This is strange... I tested it on a mobile device with Chrome and Firefox, and on a desktop with Chrome and Edge. All the results were the same. Is there a specific file to look add? Regards, Peter

3 2

How can i suppress sending moderation mail to all owners?
by Markus Grandpré Aug. 11, 2025

Aug. 11, 2025

Dear list members, How can I configure the list settings the way that emails intended for moderators are delivered only to them, and not to the owners/administrators of the list? Best, Markus Grandpré -- Markus Grandpré (he/him) Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration 78457 Konstanz Tel: +49 7531 88-4342D

3 3

Migration of archives mailman2 to mailman3: python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory
by Wikinaut Aug. 10, 2025

Aug. 10, 2025

Your current *) documentation says Migrate the list archives from Mailman 2 to Mailman 3 by running the following command: $ python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox (venv) /opt/mailman $ python manage.py python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory What did I wrong or what is that part of your documentation missing? *) https://docs.mailman3.org/en/latest/migration.html

3 6

I wanted to upgrade the mailman3 documentation, but cannot see the promised link "edit on github"
by Wikinaut Aug. 10, 2025

Aug. 10, 2025

https://docs.mailman3.org/en/latest/documentation.html#edit-on-gitlab Please can you fix that?

1 0

Vote irregularities
by Ron Aug. 10, 2025

Aug. 10, 2025

I've been playing with the voting system on a couple of lists (this one included). There are some weird behaviours I've noticed: * votes are frequently not immediately reflected - a page reload is required * some votes display as: 0 0 You dislike it (cancel) Here we see I've voted on a message, but the counts are still zero up and zero down. I just down-voted one of my posts as a test, and nothing changed in the page to reflect the vote. Often it takes multiple clicks, sometimes a page reload. Browser console shows voting generates a 200 response to a POST method, but the JSON confuses me: like 0 dislike 0 html '\n\n <form method="post" class="likeform"\n action="/archives/list/talk(a)lists.domain.tld/message/IK6WH4IQPZXOG3CIFV4CJGOKVFARGXA5/vote">\n <input type="hidden" name="csrfmiddlewaretoken" value="***">\n \n\t\t\n\t\t\t<a class="youlike vote "\n\t\t\thref="#like" data-vote="1" aria-label="Like thread">\n\t\t\t\t\t<i class="fa fa-thumbs-o-up"></i> 0\n\t\t\t</a>\n\t\t\t<a class="youdislike vote"\n\t\t\thref="#dislike" data-vote="-1" aria-label="Dislike thread">\n\t\t\t\t<i class="fa fa-thumbs-o-down"></i> 0\n\t\t\t</a>\n\t\t\n \n\n </form>\n' The uwsgi.log file entry for that vote is: [pid: 4010303|app: 0|req: 552908/575956] 127.0.0.1 () {66 vars in 1374 bytes} [Sun Aug 10 02:28:21 2025] POST /archives/list/talk(a)lists.domain.tld/message/IK6WH4IQPZXOG3CIFV4CJGOKVFARGXA5/vote => generated 696 bytes in 376 msecs (HTTP/1.1 200) 9 headers in 394 bytes (1 switches on core 1) Following the Permalink beside the voting options loads the specific message with no votes showing. Ctrl+F5 shows no votes. Re-casting vote and reloading shows no votes. Clicking "Back to thread" shows my message and: > 0 0 You dislike it (cancel) I don't think I've ever seen reliable voting on any MM3 site, including this one (I don't think I've seen zero / zero You {like|dislike} it (cancel) here, but multiple vote attempts to see the results is not unusual). Searching the archive shows something from ~6-7 years ago where caching was modified, seems relevant but nothing since. Am I alone in this, or is the feature so unused that nobody else noticed this?

2 1

Problem upgrading from 2.1 to 3, dockerized
by jesper.holck＠ibsgaarden.dk Aug. 9, 2025

Aug. 9, 2025

I recently followed the instructions here https://github.com/g4rf/dockerized-mailcow-mailman, and was able to create a new Mailman 3, Debian-based installation. I then followed the instructions here https://docs.mailman3.org/en/latest/migration.html in order to migrate from my old, Centos-based installation, to the new, Debian-based installation. It seemed to work well, but unfortunately a problem showed up. Whenever someone posted to one of the lists on the new installation, the messages were rejected by Postfix: postfix-mailcow-1 | Aug 5 20:55:48 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> postfix-mailcow-1 | Aug 5 20:55:49 ef2b760c2e61 postfix/cleanup[8681]: B7B856099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser1(a)gmail.com> proto=ESMTP helo=<[172.19.199.4]> postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: message-id=<A8946B8E-2A47-4701-9548-4544981FAC5E(a)gmail.com> postfix-mailcow-1 | Aug 5 20:55:50 ef2b760c2e61 postfix/cleanup[8681]: 216D36099EC: milter-reject: END-OF-MESSAGE from unknown[172.22.1.1]: 5.7.1 This message does not meet our delivery requirements; from=<mylist-bounces(a)myserver.dk> to=<mylistuser2(a)mail.dk> proto=ESMTP helo=<[172.19.199.4]> So, for each of the existing lists, I had to delete the old list and create a new one - with the same name and the same users. After this, everything seems to work as expected. Thanks for all the work you all has put into this, Jesper

2 1