- Mailman-users - lists.mailman3.org

Where to start looking?
by Paul Tomblin March 12, 2026

March 12, 2026

So I imported all our mailman2 lists into mailman3, and it appears it didn't preserve passwords. So my wife (who administers 3 lists of her own) tried to use the reset password link (multiple times) but she never gets the email. I don't see any outgoing email to her in mail.log, or any of the mailman logs. I do the exact same thing as her and I get the email. Any suggestions on what I should be looking for? -- Paul Tomblin

2 1

Accept these non-members
by Lars Bjørndal March 10, 2026

March 10, 2026

Hi, list! I have an announce only Mailman3 list. When I log into the web interface as an admin user, and go to the specified list, and choose Settings, I find the Message Acceptance tab. There, I find the edit field Accept these non-members. But this field is empty, although I know that some people have permissions and are able to post to this list. How can I find the list of these non-members and add more people or delete someone? I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. Any hints? Thanks, Lars

3 10

Reset bounce count in MM3
by iMark March 10, 2026

March 10, 2026

Hi, Is there an equivalent of Mailman 2's "bin/reset_bounce.py" in Mailman 3 ? Thanks, Mark

3 7

Additional info/tags on Members
by mkoerber＠akamai.com March 9, 2026

March 9, 2026

I am managing a few mailing lists which are hosted on a mailman3 instance. None of these are allowing self-subscription, but I have a need to be able to search the membership by association, ie whether they belong to any of a number of named groups Currently there does not seem to be any means for attaching a comment field, tag or such to group members, which would allow keeping such metadata and using it for searching members. (and no, the email addresses of members of one or more groups may not be similar, hence searching by @domain or such will not work) Also, the group-association info should *not* be exposed externally (ie to the member in question or any others), which makes adding the tag/group info as part of the full name impossible. Is there any way to do this in mailman3? If not can this be counted as a feature request: - in mailman3 itself: + add a facility that allows storing additional info to each member , either as a (largish) comment field or an array of tags ++ if tags, it should support managing thousands of them (but each member is likely to only need a few associated) + if tags are used, each list should have its own set of tags (though a means to designate a list to participate in a global tag collection might be useful). - in postorious: + allow modifying the comment field, or adding/removing/modifying one or more tags to each list-member + allow searching a group's membership by tags (or substring in the comment field), ++ following which mass-operations (deletion, setting moderation flags etc) should be possible based on individual selection of the found fields mailman3 really only would need to support storing the additional data for each member, as (at least in my use case) that data is not actually required for mail forwarding. However, it seems to be desirable to store the info in the mailman3 database rather than an external system (to reduce chances that these might get out of sync).

2 1

Opinions wanted.
by Mark Sapiro March 9, 2026

March 9, 2026

There is currently a merge request at <https://gitlab.com/mailman/django-mailman3/-/merge_requests/345> to hide the "Results per page:" dropdown from some Postorius and HyperKitty pages when the full list of items (lists) is on the page. I.e. when the number of items is <=10 and the "Results per page:" is the default 10, don't display the dropdown. However there is some controversy over whether this should also apply say when the number of items is > 10 but still is on one page. So the question is if we are going to hide the dropdown when "Results per page:" is the default 10 and there are <= 10 items so all are on the page, should we also hide it when say "Results per page:" is 25 and there are 22 items all on the page. Your opinion on this is requested via a reply in this thread. See the merge request (link above) for arguments pro and con. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 8

Fwd: Re: Re: How to upgrade to 3.10
by Paul Tomblin March 9, 2026

March 9, 2026

On Sun, Mar 8, 2026, at 10:56 PM, Mark Sapiro wrote: > > Actually I think the issue is because of the version not being bumped When I did pip with a file path, it looks like it did uninstall and reinstall Building wheels for collected packages: postorius Building wheel for postorius (pyproject.toml) ... done Created wheel for postorius: filename=postorius-1.3.13-py3-none-any.whl size=3844417 sha256=b0ca99e0c77a2fd3a7460a38d5e917855170432610e123f6cbe03f1ab054888d Stored in directory: /tmp/pip-ephem-wheel-cache-nz_847ds/wheels/58/f2/fa/13dfd8d8589c1b34506c170121d1cc3ab9245e2a684d0be026 Successfully built postorius Installing collected packages: postorius Attempting uninstall: postorius Found existing installation: postorius 1.3.13 Uninstalling postorius-1.3.13: Successfully uninstalled postorius-1.3.13 Successfully installed postorius-1.3.13 Looks like I've got base_url working! Thanks very much. As a feature request, could we get the unsubscribe email address as a template variable? Maybe I should dust off my python skills and submit a pull request. Do I need a gitlab account to do that? -- Paul Tomblin

2 1

Re: How to upgrade to 3.10
by Paul Tomblin March 9, 2026

March 9, 2026

On Sat, Mar 7, 2026, at 11:08 PM, Mark Sapiro wrote: > On 3/7/26 17:14, Paul Tomblin via Mailman-users wrote: >> >> I’m not seeing it. > > Are you looking at <https://your.domain/mailman3/domains/> > > Do you have the latest Postorius from GitLab? I missed that step at first, but now I've done it, I see no change. It still says version 1.3.13, and the Edit Domain page still just has Description, Alias Domain, and Web Host. When I was installing it, it said it was this commit: Resolved https://gitlab.com/mailman/postorius to commit 2c0c3aeb905c82ee4d6724897b89def71c02c1ef which does appear to be the latest. Sorry to be taking so much of your time, but I really want to make the footer for my neighborhood association lists as much like the old ones as possible. -- Paul Tomblin

2 3

How to upgrade to 3.10
by Paul Tomblin March 8, 2026

March 8, 2026

I installed 3.9 with pip last week, but i want to upgrade to 3.10. But pip install -U mailman postorius django-mailman3 hyperkitty mailman-web doesn't upgrade it. Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) Collecting mailman Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) ... a bunch of these ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) ...a bunch more... -- Paul Tomblin

2 10

alembic version
by Thomas Krichel March 7, 2026

March 7, 2026

On my fresh install I am running into problems with the alembic number. root@darni ~ # systemctl restart mailman3 ; systemctl restart mailmanwebq Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details. Failed to restart mailmanwebq.service: Unit mailmanwebq.service not found. root@darni ~ # systemctl status mailman3.service × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2026-03-07 07:01:03 UTC; 2s ago Duration: 23h 33min 7.258s Invocation: dde1db5581914d96b1da564d537df84a Process: 1209747 ExecStart=/usr/local/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) Mem peak: 64.8M CPU: 681ms Mar 07 07:01:03 darni mailman[1209747]: File "/usr/lib/python3.13/contextlib.py", line 162, in __exit__ Mar 07 07:01:03 darni mailman[1209747]: self.gen.throw(value) Mar 07 07:01:03 darni mailman[1209747]: ~~~~~~~~~~~~~~^^^^^^^ Mar 07 07:01:03 darni mailman[1209747]: File "/usr/local/mailman/venv/lib/python3.13/site-packages/alembic/script/base.py", line 245, in _catch_revision_errors Mar 07 07:01:03 darni mailman[1209747]: raise util.CommandError(resolution) from re Mar 07 07:01:03 darni mailman[1209747]: alembic.util.exc.CommandError: Can't locate revision identified by '8cc1f79f4459' Mar 07 07:01:03 darni systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Mar 07 07:01:03 darni systemd[1]: mailman3.service: Failed with result 'exit-code'. Mar 07 07:01:03 darni systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Mar 07 07:01:03 darni systemd[1]: mailman3.service: Consumed 681ms CPU time over 727ms wall clock time, 64.8M memory peak. Indeed: root@darni ~ # sudo -u postgres psql -d mailman3 psql (18.2 (Debian 18.2-1)) Type "help" for help. mailman3=# SELECT version_num FROM alembic_version; version_num -------------- 8cc1f79f4459 (1 row) Setting the number to say 0 mailman3=# update alembic_version set version_num=0; UPDATE 1 and repeating the restart yields the same problem. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22191st day.

3 2

Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated
by Thomas Krichel March 7, 2026

March 7, 2026

This issue is still there for me. I am starting a new installation from scratch, with the venv method in 3.13. (venv) root@darni ~ # mailman-web migrate System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. I have root@darni /etc/mailman3 # head -15 /etc/mailman3/settings.py # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * # Settings below supplement or override the defaults. # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Which is what I believe Wikinaut suggested works for her/him. But the warning is still there. I added Marks suggestions to add verbiage in the actual codebase root@darni /etc/mailman3 # tail -17 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/settings/mailman.py ### added by ToK #: Django Allauth #ACCOUNT_AUTHENTICATION_METHOD = "username_email" #ACCOUNT_EMAIL_REQUIRED = True #ACCOUNT_EMAIL_VERIFICATION = "mandatory" #ACCOUNT_UNIQUE_EMAIL = True ACCOUNT_LOGIN_METHODS = {'email', 'username'} ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] ACCOUNT_EMAIL_VERIFICATION = "mandatory" ACCOUNT_UNIQUE_EMAIL = True ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] Restarted root@darni /etc/mailman3 # systemctl restart mailman3 ; systemctl restart mailmanweb Same old. (venv) root@darni ~ # mailman-web migrate System check identified some issues: WARNINGS: ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Maybe I missunderstood something. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22190th day.

3 6