April 2025 - Mailman-users - lists.mailman3.org

Change delivery_status in bulk
by Hitashi mancho April 4, 2025

April 4, 2025

Dear All, We have a Mailman3 instance with around 500 mailing lists. Most of the mailing lists have 5000 subscribers. Because of some misconfiguration in the postfix, posting for 1000 users has been bounced. Until we realized what happened, the mailman had set delivery_status to "disabled_by_bounces." for many subscribers. Now, I am unable to locate any command or an API call through which I can change the delivery_status back to enabled for 1000+ users. Can you please guide me on how I can do this programmatically using cli (I will write a bash script) or using an API call? Regards, Hitachi.

2 2

compatibility of mailman 3.3.10 with mariadb 11.4 LTS
by Chandrakant Pandey April 2, 2025

April 2, 2025

Whether mailman 3.3.10 is compatible with mariadb 11.4 LTS

3 3

Regarding nested mailing lists in mailman 3
by Chandrakant Pandey April 2, 2025

April 2, 2025

Hi, I want to know whether we can setup nested mailing lists in mailman 3 which we used to do in mailman 2. like ep2021@iitb.ac.in,ep2022@iitb.ac.in,ep2023@iitb.ac.in mailing lists exist and we add all this mailing lists as member in ep(a)iitb.ac.in. Whether this kind of nested mailing lists work ? --chandrakant

3 2

mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3
by Philip Bondi April 1, 2025

April 1, 2025

Hello to all: Giant thank you to the community, Mark, Stephen, everyone. I have a lot of follow-up tasks in previous posts. Blazing forward on critical path flaws, first. I require a Debian 12 VM that supports: - Subversion - Let's Encrypt and required challenges - IMAP server - mailman3 - DKIM server I found this post helpful. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I think I've noticed that posters avoid less than sign and express as html. I hacked it into this, which I tried to anonymize. My alias /static/ had to point to different location for my installation. I have ssl working for Subversion and my Let's Encrypt challenges. And 6 of those ProxyPass seem to work through ssl, except for /mailman3. That fails. Surfing to example.com/mailman3 gets. Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. <IfModule mod_ssl.c> <VirtualHost *:80> ServerName example.com Redirect permanent / https://example.com/ DocumentRoot /var/www/html/example.com/ </VirtualHost> <VirtualHost *:443> SSLEngine on ServerAdmin pjbondi(a)systemdatabase.com ServerName example.com ServerAlias www.example.com DocumentRoot /var/www/html/example.com/ ErrorLog ${APACHE_LOG_DIR}/example.com_error.log CustomLog ${APACHE_LOG_DIR}/example.com_access.log combined Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/example.com-0001/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/example.com-0001/privkey.pem Alias /static/ /opt/mailman/web/static/ <Directory "/opt/mailman/web/static/"> Require all granted </Directory> <IfModule mod_headers.c> RequestHeader unset X-Forwarded-Proto <If "%{HTTPS} =~ /on/"> RequestHeader set X-Forwarded-Proto "https" </If> </IfModule> <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" # https://github.com/maxking/docker-mailman/issues/525 #ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ #ProxyPassReverse / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ #ProxyPassMatch "^/$" "http://127.0.0.1:8000/mailman3" </IfModule> </VirtualHost> </IfModule> I was noticing that there's no mailman3 sub-dir, here. I tried changing to http://127.0.0.1:8000/django-mailman3, but that didn't work. (venv) mailman@shackleton12:~$ ls -alF /opt/mailman/web/static/ total 40 drwxr-xr-x 10 mailman mailman 4096 Mar 24 16:03 ./ drwxr-xr-x 4 root root 4096 Mar 24 16:01 ../ drwxr-xr-x 3 mailman mailman 4096 Mar 24 16:03 account/ drwxr-xr-x 5 mailman mailman 4096 Mar 24 16:03 admin/ drwxr-xr-x 4 mailman mailman 4096 Mar 25 08:07 CACHE/ drwxr-xr-x 5 mailman mailman 4096 Mar 24 16:03 django_extensions/ drwxr-xr-x 5 mailman mailman 4096 Mar 24 16:03 django-mailman3/ drwxr-xr-x 6 mailman mailman 4096 Mar 24 16:03 hyperkitty/ drwxr-xr-x 6 mailman mailman 4096 Mar 24 16:03 postorius/ drwxr-xr-x 7 mailman mailman 4096 Mar 24 16:03 rest_framework/ Any ideas? What log file should I share? I've looked at apache and uwsgi logs, but I don't know what's relevant. I cannot seem to find an error in logs around mailman3 URL

4 10