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

Enforcing SSO and subscription options
by dlb-ml＠anl.gov July 18, 2025

July 18, 2025

Contrary to the messages I found in the archive, rather trying to delete or remove the social login portion of the sign in page, I'm looking to see if there's any way to isolate the third-party login section and prevent local account sign in and sign up. This way, we can ensure that the people within our organization are using a stronger auth method that prioritizes MFA, rather than just username/password. To do this, our plan is to block signups using "ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter'" and to remove the portions of the login template such that the username/password/forgot password fields are removed, leaving just the button to our SSO instance. I'm anticipating that this should be sufficient to block username/password sign ins, and is resistant to page manipulation due to CSRF tokens, but I wanted to ask to see if there was a better way, like an official configuration (which I have not found yet). I did see that there is the SOCALACCOUNT_ONLY option, as provided by allauth (https://docs.allauth.org/en/latest/socialaccount/configuration.html) but that broke any attempt to display the sign in page, and I'm assuming is not supported with the current version of MM3. Is my plan to modify the templates viable? Additionally, because external users would not have access to their own dashboards within the web UI, and since we are planning on disabling anonymous subscriptions with "SHOW_ANONYMOUS_SUBSCRIBE_FORM=False", the only two viable ways to subscribe to a list for them would be: 1) Send a request directly to the list owner or a superadmin to subscribe/unsubscribe the address 2) Allow email commands to subcribe/unsubscribe users (i.e. $LISTNAME-join@$DOMAIN) Given the discussions on disabling the anonymous subscription form, are the email commands a less spam-susceptible solution or are they just as vulnerable as the form? Thanks

4 5

redirecting -bounces replies
by Hirayama, Pat June 26, 2025

June 26, 2025

Greetings, Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? In Mailman2, I know that I could do that by modifying the aliases table. I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location. Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

5 14

"this held message has been lost"
by Ethan Furman June 10, 2025

June 10, 2025

I have now seen this message on two different occasions. Any ideas on what is happening? Happy to provide additional information if I am told what is needed (and how to get it -- I'm a web moderator for the list without access to the machine it runs on). :) -- ~Ethan~

3 4

Recently active discussions - Hyperkitty
by Sam Darwin June 5, 2025

June 5, 2025

Hi, Sometimes not sure if it's preferable to open a gitlab issue, or chat on the mailing list. I have run a large archive import into mailman3/hyperkitty. After that's done, waited a day, for scheduled cron jobs to complete. In "All Threads", all the email archives are present. The import worked. In "RECENTLY ACTIVE DISCUSSIONS" on the main page, it says: RECENTLY ACTIVE DISCUSSIONS No discussions this month (yet). Nothing there. That means if I direct users to visit the site, the page, it appears empty. That's too bad. :-) It should display recent emails. What would affect this feature during an archive import? Is it a problem with the import script itself, or with a scheduled cron job, or something else? Would you expect "Recently active discussions" be empty when very recent archives do exist? Thanks, Sam

3 8

Login confusion
by Markus Grandpré April 22, 2025

April 22, 2025

Dear list, We've encountered an issue with Postorius after migrating from Mailman 2.1. It appears that Postorius is treating email addresses with differing capitalization as distinct user accounts. For example, <markus.grandpre(a)uni-konstanz.de> and <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate identities. This is causing significant confusion. Users registered with one capitalization pattern are not seeing the list subscriptions and settings that were previously associated with their account (imported from Mailman v2.1) which used a different capitalization. Is there a known configuration option or method within Postorius (or Mailman 3 itself) to normalize or unify account identification, effectively treating email addresses as case-insensitive for account matching? We need a solution that ensures users see their correct list memberships regardless of the capitalization they use when logging in or that was used during the original Mailman 2.1 import. Thank you in advance Markus -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 19

Moderator e-mails only going out once a day
by jkoral＠luc.edu April 22, 2025

April 22, 2025

Hi, I have just got done migrating from MM2 to MM3 and the users are experiencing issues with their moderated messages. After the message is sent, the moderator does not know about the message until the next day. I checked the maillogs and all those messages are being sent at the same time around midnight. I also noticed the messages are being sent from user(a)example.com, which I switched in /etc/mailman3/mailman.cfg to a generic e-mail address. Is there a way to change those moderator e-mails to send right away? Does having user(a)example.com in the config affect that? Thank you in advance, Joe

6 22

Upgrade docker-mailman to v0.5.2
by Christopher April 21, 2025

April 21, 2025

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 1

makemigrations --merge error after Debian upgrade
by Chupin Maxime April 16, 2025

April 16, 2025

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

7 28

CSS Hyperkitty ERROR
by Johan Alsina April 12, 2025

April 12, 2025

Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. Here you can see what i see when loading hyperkitty https://freeimage.host/i/3n6kXKQ and mailman(postorius) https://freeimage.host/i/mailman.3n6kVix When i run my server with verbosity it shows like all is loading ok: https://freeimage.host/i/3n6SViG Any ideas? :/ My static files are loading from /static/CACHE/css/output.a0f71925131b.css and /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css It seems like the real error are in the /static/CACHE files, because hyperkitty is the only one who load files from this directory.. postorius uses /static/postorius and all the css files are working fine. I checked permissions for the directory, cleared cache, etc.. i dont know what to do. This is my config for staticfiles: STATIC_URL = 'static/' STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles') STATICFILES_DIRS = [ os.path.join(BASE_DIR, 'static'), '/opt/mailman/projectes/mailman3web/static/CACHE', Thank you so much in advance.

5 9

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