- Mailman-users - lists.mailman3.org

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

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

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

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.

2 1

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

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

2 3

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

Footer variables
by Washington Odhiambo March 3, 2026

March 3, 2026

In my /opt/mailman/mm/var/templates/lists/ kictanet.lists.kictanet.or.ke/en/list:member:regular:footer.txt, I have: Archived at: ${hyperkitty_url I was hoping that variable would be replaced with what I see in this list, i.e. - Archived at: https://lists.mailman3.org/archives/list/mailman-users @mailman3.org/message/HX6NZKICL7V2QWE2V4YNKIMSMQHARPUV/ However, in my posts, it's blank. What am I missing? -- 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 11

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