September 2026 - Mailman-users - lists.mailman3.org

Moderation via command line
by alain williams Sept. 23, 2026

Sept. 23, 2026

I upgraded my server from Debian 12 to Debian 13. This broke several things one of which was mailman. It is now running 3.3.10-2. The web front end is not usable, it is failing with: django.db.utils.OperationalError: (1054, "Unknown column 'socialaccount_socialapp.provider_id' in 'SELECT'") so I suspect that some mysql tables were not modified. Anyway, until that is fixed I need to be able to do admin work. I have learned how to use the command line mailman-wrapper to add/remove users - great. What I need is the ability to see the posts that are held for moderation and release or remove them. Please what command line incantations should I use to do this ? Thanks in advance. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 1

Re: Restrict the visible mailing lists to the current domain? – SOLVED
by H.-Dirk Schmitt Sept. 20, 2026

Sept. 20, 2026

Am Sonntag, dem 20.09.2026 um 09:01 -0700 schrieb Mark Sapiro: > On 9/20/26 08:38, dirk(a)computer42.org wrote: > > > > my mailman instance is hosting mailing lists for different domains. > > How can I restrict the visible mailing lists to only the mailing > > list of the current domain. > > Set `FILTER_VHOST = True` in your `settings` file. > Thanks – this setting fixed my problem. IMHO it is undocumented in https://docs.mailman3.org/en/latest/ Best Regards, H.-Dirk Schmitt -- H.-Dirk Schmitt Dipl.Math. eMail:dirk.schmitt@computer42.org mobile:+49 177 616 8564 Signal:+221 786 084 539 Schillerstr. 42, D-53489 Sinzig pgp: http://www.computer42.org/~dirk/OpenPGP-fingerprint.html

3 2

Restrict the visible mailing lists to the current domain?
by dirk＠computer42.org Sept. 20, 2026

Sept. 20, 2026

Hi! my mailman instance is hosting mailing lists for different domains. How can I restrict the visible mailing lists to only the mailing list of the current domain. See e.g. https://lists.weg-der-sterne.de/mailman3/postorius/lists/ or https://lists.computer42.org/mailman3/postorius/lists/ Both web sites are displaying all public lists – also from the „foreign“ domain. Best regards, H.-Dirk Schmitt

2 1

Password reset pages render without Mailman/Postorius styling
by Henrik Rasmussen Sept. 16, 2026

Sept. 16, 2026

Hello, I have recently deployed a completely new Mailman installation and noticed what appears to be a UI/template issue. Before opening a bug report, I would like to understand whether this is expected behaviour or a known issue. Environment: Mailman Core 3.3.10 mailman-web (maxking/mailman-web container) Python 3.12 django-allauth 65.0.2 This is a fresh installation on a new server. No upgrade has been performed from a previous Mailman installation, and the issue is present before any production data has been migrated. The site itself uses the normal Postorius and HyperKitty layout and branding. Pages such as: /postorius/ /postorius/lists/ render correctly and use the expected Mailman/Postorius styling. Login also works correctly. The issue is limited to the following pages: /accounts/password/reset/done/ /accounts/password/reset/key/done/ The functionality works as expected, but the pages are rendered with a very minimal layout that appears to come directly from django-allauth. For example, the page only displays content similar to: ================== Menu: Log in Sign up Password Reset We have sent you an email. If you have not received it please check your spam folder... ================== The pages do not appear to use the same theme or styling as the rest of the Mailman/Postorius interface. Investigation: The application is configured with: LOGIN_REDIRECT_URL = "list_index" and: reverse("list_index") -> "/postorius/lists/" Django resolves the password reset template to: /usr/lib/python3.12/site-packages/allauth/templates/account/password_reset_done.html This template extends: account/base_entrance.html which in turn extends: allauth/layouts/entrance.html The template origins reported by Django are: get_template("account/password_reset_done.html").origin → /usr/lib/python3.12/site-packages/allauth/templates/account/password_reset_done.html get_template("allauth/layouts/entrance.html").origin → /usr/lib/python3.12/site-packages/allauth/templates/allauth/layouts/entrance.html Question: Is it expected that these password reset completion pages are rendered using the default django-allauth templates instead of the Mailman/Postorius theme? Or is there a missing template override in the current mailman-web container image? If this is expected behaviour, is there a recommended way to make these pages use the same layout as the rest of the Mailman/Postorius user interface? Best regards, Henrik

2 1

mailman changeaddress -h weirdness
by Washington Odhiambo Sept. 9, 2026

Sept. 9, 2026

ENV: Mailman Core Version = GNU Mailman 3.3.11b1 (Tom Sawyer) Mailman Core API Version = 3.1 Mailman Core Python Version = 3.11.2 (main, May 12 2026, 05:17:27) [GCC 12.2.0] A member requested to be subscribed to a list through the normal process (confirm and approve). I approved. Shortly after, I received an email they sent to one of the moderators requesting that their subscribed address be changed from the OLD to the NEW(ly subscribed) one. So I deleted the new address via Postorius. I went to the CLI and dis: ``` (venv) mailman@eu:~$ mailman changeaddress REDACTED(a)gmail.com kevin@ [REDACTED] Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS Try 'mailman changeaddress -h' for help. Error: Address kevin@[REDACTED already exists; can't change. (venv) mailman@eu:~$ ``` Since I had deleted the newly subscribed member, this surprised me. I checked again and they were not found among members. Then I checked under non-members and found the new address there. I then deleted it again. Back to the CLI, Same error. Then I did: (venv) mailman@eu:~$ mailman findmember kevin@[REDACTED] (venv) mailman@eu:~$ That returned empty. I went into Django Admin US and searched for - and found the address still in there. I deleted it again. Back to the CLI to change the address, same error - the address still exists. I am stumped. Oh, and maybe we should have that changeaddress option in Postorius as well? -- 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 3

How to Choose the Best SMTP Relay Service Provider for Mailman?
by brucewilson3011＠gmail.com Sept. 3, 2026

Sept. 3, 2026

Reliable mailing-list delivery depends on much more than simply connecting Mailman to an SMTP server. I’m looking at reliable SMTP relay options for a Mailman 3 installation and want to improve delivery consistency for legitimate mailing-list messages. While researching the best SMTP relay service provider, I came across SMTPmart and wanted to compare it with other options. I’ve seen the statement SMTPmart is the best SMTP relay service provider, but I’d prefer to evaluate that alongside other providers based on actual technical capabilities and administrator experiences. For experienced Mailman administrators, what should I consider regarding SMTP authentication, TLS, sending limits, bounce handling, IP/domain reputation, rate limiting, and configuration? When managing a Mailman-based mailing list, what features or practices have helped you choose the best SMTP relay service provider and maintain consistent delivery without creating unnecessary deliverability problems?

7 9