- Mailman-users - lists.mailman3.org

"Something went wrong | Mailman REST API not available. Please restart Mailman core.
by Hirayama, Pat Oct. 31, 2025

Oct. 31, 2025

Greetings, Some of my lists have started displaying this behavior — when you try to access the list page(s), you get a page with this message: Something went wrong Mailman REST API not available. Please restart Mailman core. My mailman-core docker container is running, as are mailman-django-uwsgi, mailman-nginx and mailman-postfix. Restarting the containers doesn't change this behavior. Google suggests restarting mailman core. Or that we might not be using the correct account name, password or port. The weird thing is that it is not all lists. Most of them seem to be fine. Which suggests to me that the issue is with a few lists, but not systemwide, so I think my settings in mailman.cfg, settings.py, settings_local.py are likely correct. For the problem lists, I see this in the log: ERROR 2025-10-29 18:38:56,784 7 postorius Mailman REST API not available ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ ERROR 2025-10-29 18:38:56,790 7 django.request Service Unavailable: /postorius/lists/obfuscated.name.lists.fhcrc.org/ So, Postorius can't communicate with the API, I guess? I look at settings_local.py: MAILMAN_REST_API_URL = 'http://mailman-core:8001' I believe 8001 is the default, and since I haven't specified one in the [webservice] section of mailman.cfg, I'm assuming 8001 is correct (plus, it works for other lists). There are a few messages waiting for moderator approval — otherwise, I'd probably try just deleting the list and recreating it. Anyone have any suggestions on what else I should look at? 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>

2 7

Archive not working - Reg.
by nirmal＠iitm.ac.in Oct. 29, 2025

Oct. 29, 2025

After sending mail to a list, it is not reflecting back in Hyperkitty archive. Kindly help me in this regard.

4 7

Mailman 3 MFA with django-allauth[mfa]
by Liam Reilly Oct. 29, 2025

Oct. 29, 2025

Has anyone successfully got MFA working in Mailman 3 with django-allauth[mfa]? I'm struggling to get it working with the limited documentation I could find. (https://docs.allauth.org/en/dev/mfa/index.html) If signed in as a user, I can browse to /accounts/2fa/ to activate MFA, but I was hoping to make it a mandatory part of the Sign Up process. Is there something that needs to be done with the URLs somewhere? This list site is an example of how I'd like it to work: https://mailing-lists.imperial.ac.uk/ Here is what I added to settings.py: #---------------------------------------- INSTALLED_APPS= ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.humanize', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.mfa', 'allauth.socialaccount'] # Specifies the adapter class to use, allowing you to alter certain default behaviour. MFA_ADAPTER = "allauth.mfa.adapter.DefaultMFAAdapter" # Used to override forms. Defaults to: MFA_FORMS = { 'authenticate': 'allauth.mfa.forms.AuthenticateForm', 'reauthenticate': 'allauth.mfa.forms.AuthenticateForm', 'activate_totp': 'allauth.mfa.forms.ActivateTOTPForm', 'deactivate_totp': 'allauth.mfa.forms.DeactivateTOTPForm', } MFA_RECOVERY_CODE_COUNT = 10 MFA_TOTP_PERIOD = 30 MFA_TOTP_DIGITS = 6 #---------------------------------------- Thanks.

2 1

Disable automatic bouncing globally?
by jkoral＠luc.edu Oct. 28, 2025

Oct. 28, 2025

Is there a way to disabled the automatic bouncing globally on all lists or do I have to do that on each individual list?

2 3

Password reset/confirm email page formatting
by Reilly, Liam Oct. 22, 2025

Oct. 22, 2025

Hi, Does anyone else experience this where the pages for password reset/verify email lack formatting. Not sure what the cause might be as all other pages are fine. Please see attached images. Thanks. [cid:image001.png@01DC435D.8CB42CF0] [cid:image002.png@01DC435D.8CB42CF0] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Content-Type: image/png Name: image002.png Replaced multipart/alternative part with first alternative.

5 8

Configuring Web Front End
by Dennis Putnam Oct. 21, 2025

Oct. 21, 2025

The next layer of the onion is configuring the web front end. Specifically setting up Django. The documentation seems to make a lot of assumptions about what I know about Django (which is nothing). I cannot find anything about what 'settings.py' should look like for mailman3. It is not even clear where it should go (/opt/mailman/var/etc?). The Django setup documentation is of no help for mailman3. Am I missing something in the wiki?

3 2

Migrating to Mailman3
by dap1＠bellsouth.net Oct. 20, 2025

Oct. 20, 2025

I am about to migrate from mailma2 on CentOS to mailman3 on Ubuntu. Are there any special gotchas of which I need to be aware? TIA.

4 7

Unprocessed Bounce Mails from user with e-mailadresse with a "-" in it
by Wikinaut Oct. 14, 2025

Oct. 14, 2025

The recipient address abc-given.name(a)online.de (member of list mylist(a)myserver.de) has currently an out of office responder and mails are returning to my mailman3 system as unrecognized bounce messages. I suspect the "-" in his address to be in conflict with the bounce address hyphen: <mylist-bounces+abc-given.name=online.de(a)myserver.de> Can any of you experts try on their systems, whether this a bug of mailman3 due to the "-" in the address? Systeminfo: Mailman Core-Version GNU Mailman 3.3.10 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]

5 9

default processing
by Sam Darwin Oct. 13, 2025

Oct. 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 10

Mailmanweb RAM Usage
by Odhiambo Washington Oct. 12, 2025

Oct. 12, 2025

Using the uwsgi.ini from the virtualenv method documentation, mailmanweb is constantly using 2GB RAM on my server. My database (MariaDB) size is 2GB. Is this expected? -- 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]

3 5