- Mailman-users - lists.mailman3.org

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

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

March 9, 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

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

Archiving Display Email Signature in Plain-Text
by msok＠lalawlibrary.org March 6, 2026

March 6, 2026

The Archiving is still display Email Signature in Plain-Text after I configured filter content: No and convert html to plaintext: No in Alter Messages. And Markdown text in Archiving settings. In addition to that, I also configured HYPERKITTY_RENDER_INLINE_IMAGE = True in settings.py file Where else should take a look into this? My email signature is from CodeTwo. Thanks, Marin

3 4

Can't add emails to accept_these_nonmembers
by Ibiam Chihurumnaya March 4, 2026

March 4, 2026

I need to set some nonmembers to a list as these members send message to the list, but don't need to receive any message from the list. I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save().

3 17

Debian bug report
by Paul Tomblin March 3, 2026

March 3, 2026

So I went to submit a bug report to Debian about the fact that the mailman3-web page drags in nginx for no reason. Turns out that the bug had been reported in 2021 and nobody who worked on it who understood mailman understood apache and nobody who worked on it who understood apache understood mailman[1]. So I submitted an update. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002795 [1] Literally, one of the developers said Thanks, I admit initially I had no plan on supporting apache2 as I don't use it. Jonas did that part and therefore I did not follow at all. -- Paul Tomblin

2 2

Re: Footer variables
by Stephen J. Turnbull March 3, 2026

March 3, 2026

Please keep this on list. Paul Tomblin writes: > Nope, it's still saying it depends on libapache2-mod-proxy-uwsgi | > nginx, and there's no libapache2-mod-proxy-uwsgi. It appears that > mod_proxy is in base apache now. Oddly I never enabled proxy_uwsgi > in mods-enabled but mailman works. I should probably report it to > Debian. What depends on libapache2-mod-proxy-uwsgi? Mailman core doesn't depend on that at all. It always uses gunicorn as the WSGI server for the REST API, and the Apache config uses ProxyPass on port localhost:8001. And sez who? Are you asking apt or dpkg? I thought you have installed via pip into a virtual environment -- what apt and dpkg think about Mailman dependencies is irrelevant. > > > Is it possible to upgrade to 3.10 with pip? If you installed using Debian, you can't upgrade with pip -- that's a Debian restriction. You have to remove the Debian package(s), and create a virtual environment, typically under /opt/mailman, to install the Mailman suite into. Then, if you have already working lists, you have to either (1) "very carefully" move all the /var/lib/mailman data from your working Debian install into /opt/mailman in appropriate places, or (2) configure the new Mailman to look for data where Debian put it (if you're lucky you can re-use Debian's /etc/mailman3/mailman.cfg for that, although they may have patched the source). The /var data is the queues (mostly bad and shunt, but you may have orphaned qfiles in out, and very very rarely in other queues), the logs, and any in-progress digests being accumulated. The list configurations, user profiles, and most volatile data (eg, pending confirmations) will be in your database. You can use the Debian packaged database, just point the new Mailman at that. > > Yes: see https://pypi.org/project/mailman/. > > Use python3 -m pip install --upgrade mailman. > > Nope, that doesn't work. > python3 -m pip install --upgrade mailman 2>&1 | tee bar > Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) Where is '.'? If it's under /var/lib or /var/share, you've got Debian's mailman and you can't upgrade with pip. You want it to be under /usr/local (ugh) or /opt/mailman (happy face). > Collecting mailman > Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) [...] > Requirement already satisfied: zope.schema>=4.9 in ./venv/lib/python3.13/site-packages (from zope.configuration->mailman) (8.1) Are you saying pip returns to the shell prompt without doing anything after that? > If I'm reading that right, I have to guess which requirements I > need to force an update on before it will upgrade mailman. No, that's saying all requirements are satisfied for mailman-3.3.10 as far as I can tell. Are you working as the right user? (If you've previously used Debian packages and have working lists, you probably want to continue using Debian's preferred 'list' user, otherwise you may create a 'mailman' user.) If it's not lacking write permissions to the virtual environment, I have no idea why this isn't working. The only thing I can suggest is the same as Mark, force version 3.3.10 with python3 -m pip install --upgrade mailman==3.3.10 and see what happens. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 0

config_list in Mailman3?
by John Price March 3, 2026

March 3, 2026

Is there a way to do this in Mailman3? # Mailman2 backup individual list config # $list = list name # writes config to mailman.cfg $MAILMAN_ROOT/bin/config_list -o mailman.cfg $list -- Can vegetarians eat animal crackers? Have a great day and don't forget to laugh! http://www.gcfl.net (The Good, Clean Funnies List): Good, clean daily funnies you can safely tell your Mom!

2 1

High IO for 8+ hours
by Paul Tomblin March 2, 2026

March 2, 2026

First time running runjobs monthly since I installed it a few days ago, and it's been maxing out I/O for the last 8 hours. There doesn't appear to be any logging going on. I am using Xapian, by the way. Is this normal? Is this going to happen every month, or is the first month special? -- Paul Tomblin

3 6