- Mailman-users - lists.mailman3.org

Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?
by Flo Feb. 16, 2026

Feb. 16, 2026

Hi, I have setup in Debian Trixie mailman3-full and came that far, that I have created a mailing list. I can sent emails to the members. However when I send from an email which is non-member the message is held. If I want to accept this message as list admin, I get: `An error occurred while processing your request.` And I get an email: `Internal Server Error: /mailman3/postorius/.../held_messages TemplateSyntaxError at /postorius/lists/.../held_messages 'humanize' is not a registered tag library. Must be one of: account admin_list admin_modify admin_urls allauth bootstrap_tags cache compress d_gravatar date_helpers debugger_tags decorate gravatar highlight highlighting hk_generic hk_haystack i18n indent_text l10n log markdown membership_helpers more_like_this nav_helpers p_gravatar pagination postorius_helpers rest_framework socialaccount static syntax_color tz widont Request Method: GET Request URL: https://.../mailman3/postorius/lists/.../held_messages Django Version: 4.2.23 Python Executable: /usr/bin/uwsgi-core Python Version: 3.13.5 Python Path: ['.', '', '/usr/lib/python313.zip', '/usr/lib/python3.13', '/usr/lib/python3.13/lib-dynload', '/usr/local/lib/python3.13/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3/dist-packages/setuptools/_vendor'] . . .` humanize is in the INSTALLED_APPS section in /usr/share/mailman3-web/settings.py. In this file I I configured Django. However it's not in the Python path as written in the error email above. So maybe I have to find a different settings file. Can anyone advise me where I can find the error I have in my configuration? Thanks in advance. Flo

5 7

Inaccessible User Profile
by awingnut Feb. 14, 2026

Feb. 14, 2026

I have a long time user that cannot access their profile. When I click on users/members then that user as superuser, I get this error. Page not found This page either doesn't exist, or it moved somewhere else. When I click that uers manage button, the page comes up but it says there are no subscriptions. This user was subscribed as of couple of days ago. Can this be fixed via admin functions?

2 1

Issues with Mail delivery after Mailman 3 installation
by Ibiam Chihurumnaya Feb. 12, 2026

Feb. 12, 2026

I finished installing mailman3, setup lmtp and smtp for mail delivery and I followed the instructions on the mailman 3 installation page. Mail delivery doesn't work and the logs show this; Jan 31 12:53:53 lists postfix/lmtp[4131588]: 3B8121A89BD: to=<systems(a)lists.sugarlabs.org>, relay=127.0.0.1[127.0.0.1]:24, delay=11119, delays=11072/0.01/0.01/47, dsn=4.3.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.3.0 <systems(a)lists.sugarlabs.org> Temporary internal error (in reply to RCPT TO command)) 106029 Jan 31 12:53:53 lists postfix/lmtp[4131587]: 052BB1A8975: to=<mailman(a)lists.sugarlabs.org>, orig_to=<mailman>, relay=localhost[127.0.0.1]:24, delay=1432, delays=1385/0.02/0.01/47, dsn=4.3.0, status=deferred (host localhost[127.0.0.1] said: 451 4.3.0 <mailman(a)lists.sugarlabs.org> Temporary internal error (in reply to RCPT TO command)) Jan 31 12:53:53 lists dovecot: lmtp(4131586): Disconnect from 127.0.0.1: Logged out (state=READY) Jan 31 12:53:53 lists postfix/local[4131582]: F2DB61A8952: passing <mailman(a)lists.sugarlabs.org> to transport=lmtp Jan 31 12:53:53 lists dovecot: lmtp(4131590): Disconnect from 127.0.0.1: Logged out (state=READY) Jan 31 12:53:53 lists dovecot: lmtp(4131589): Disconnect from 127.0.0.1: Logged out (state=READY) Jan 31 12:53:53 lists postfix/local[4131584]: D172A1A8A0E: passing <mailman(a)lists.sugarlabs.org> to transport=lmtp Jan 31 12:53:53 lists dovecot: lmtp(4131586): Connect from 127.0.0.1 Jan 31 12:53:53 lists dovecot: lmtp(4131589): Connect from 127.0.0.1 Jan 31 12:53:54 lists postfix/lmtp[4128841]: connect to localhost[::1]:24: Connection refused Jan 31 12:53:54 lists postfix/lmtp[4128840]: connect to localhost[::1]:24: Connection refused Jan 31 12:53:54 lists postfix/lmtp[4128841]: 348981A8A2A: to=<mailman(a)lists.sugarlabs.org>, orig_to=<mailman>, relay=none, delay=113, delays=0.04/52/61/0, dsn=4.4.1, status=deferred (connect to localhost[::1]:24: Connection refused) Jan 31 12:53:54 lists postfix/lmtp[4128840]: 5382D1A8A27: to=<mailman(a)lists.sugarlabs.org>, orig_to=<mailman>, relay=none, delay=173, delays=0.02/111/61/0, dsn=4.4.1, status=deferred (connect to localhost[::1]:24: Connection refused) Jan 31 12:53:56 lists dovecot: lmtp(4128842): Disconnect from 127.0.0.1: Connection closed (state=READY) Jan 31 12:53:56 lists dovecot: lmtp(4127392): Disconnect from 127.0.0.1: Connection closed (state=READY) Jan 31 12:54:02 lists postfix/pickup[4131579]: 1D3E71A8A1C: uid=1005 from=<mailman> Jan 31 12:54:02 lists postfix/cleanup[4131852]: 1D3E71A8A1C: message-id=<20260131205402.1D3E71A8A1C(a)lists.sugarlabs.org> Jan 31 12:54:02 lists postfix/qmgr[4131580]: 1D3E71A8A1C: from=<mailman(a)lists.sugarlabs.org>, size=919, nrcpt=1 (queue active) Jan 31 12:54:53 lists dovecot: auth: Fatal: passdb passwd-file: Missing args Jan 31 12:54:53 lists dovecot: master: Error: service(auth): command startup failed, throttling for 60.000 secs Jan 31 12:54:53 lists dovecot: lmtp(mailman(a)lists.sugarlabs.org)<4131586><qMl1NuFrfmkCCz8AOj1W/w>: Error: auth-master: userdb lookup(mailman(a)lists.sugarlabs.org): Disconnected unexpectedly Jan 31 12:54:53 lists dovecot: lmtp(4131586): Error: lmtp-server: conn 127.0.0.1:56008 [2]: rcpt mailman(a)lists.sugarlabs.org: Failed to lookup user mailman(a)lists.sugarlabs.org: Internal error occurred. Refer to server log for more information. Jan 31 12:54:53 lists postfix/lmtp[4131585]: F2DB61A8952: host localhost[127.0.0.1] said: 451 4.3.0 <mailman(a)lists.sugarlabs.org> Temporary internal error (in reply to RCPT TO command) Jan 31 12:54:53 lists dovecot: lmtp(mailman(a)lists.sugarlabs.org)<4131589><kJd+NuFrfmkFCz8AOj1W/w>: Error: auth-master: userdb lookup(mailman(a)lists.sugarlabs.org): Disconnected unexpectedly Jan 31 12:54:53 lists dovecot: lmtp(4131589): Error: lmtp-server: conn 127.0.0.1:56014 [2]: rcpt mailman(a)lists.sugarlabs.org: Failed to lookup user mailman(a)lists.sugarlabs.org: Internal error occurred. Refer to server log for more information. Jan 31 12:54:53 lists postfix/lmtp[4131588]: D172A1A8A0E: host localhost[127.0.0.1] said: 451 4.3.0 <mailman(a)lists.sugarlabs.org> Temporary internal error (in reply to RCPT TO command) Jan 31 12:54:53 lists postfix/lmtp[4131585]: connect to localhost[::1]:24: Connection refused Jan 31 12:54:53 lists postfix/lmtp[4131588]: connect to localhost[::1]:24: Connection refused Jan 31 12:54:53 lists postfix/lmtp[4131585]: F2DB61A8952: to=<mailman(a)lists.sugarlabs.org>, orig_to=<mailman>, relay=none, delay=1492, delays=1385/47/60/0, dsn=4.4.1, status=deferred (connect to localhost[::1]:24: Connection refused) Jan 31 12:54:53 lists postfix/lmtp[4131588]: D172A1A8A0E: to=<mailman(a)lists.sugarlabs.org>, orig_to=<mailman>, relay=none, delay=591, delays=484/47/60/0, dsn=4.4.1, status=deferred (connect to localhost[::1]:24: Connection refused) Jan 31 12:54:53 lists postfix/local[4131582]: D92311A8A17: passing <mailman(a)lists.sugarlabs.org> to transport=lmtp Jan 31 12:54:53 lists postfix/local[4131584]: D52231A8A1A: passing <mailman(a)lists.sugarlabs.org> to transport=lmtp Jan 31 12:55:02 lists postfix/pickup[4131579]: 019161A8A2C: uid=1005 from=<mailman> Jan 31 12:55:02 lists postfix/cleanup[4131852]: 019161A8A2C: message-id=<20260131205502.019161A8A2C(a)lists.sugarlabs.org> Jan 31 12:55:02 lists postfix/qmgr[4131580]: 348981A8A2A: from=<mailman(a)lists.sugarlabs.org>, size=919, nrcpt=1 (queue active) Jan 31 12:55:02 lists postfix/qmgr[4131580]: 019161A8A2C: from=<mailman(a)lists.sugarlabs.org>, size=919, nrcpt=1 (queue active) Jan 31 12:55:02 lists postfix/qmgr[4131580]: 5382D1A8A27: from=<mailman(a)lists.sugarlabs.org>, size=919, nrcpt=1 (queue active) Jan 31 12:55:18 lists postfix/smtpd[4132212]: fatal: open dictionary: expecting "type:name" form instead of "dovecot" I setup lmtp with dovecot, and I have this in dovecot.conf; passdb passwd-file { driver = passwd-file } I also have these set in postfix main.cf; lmtp_sender_dependent_authentication = yes lmtp_sasl_auth_enable = yes lmtp_sasl_password_maps = hash:path_to_passwd_file I'm wondering if I need to disable sasl because I set dovecot not to use ssl because lmtp is only running internally.

4 37

Mailman and Postfix Conflicting Information
by dap1＠bellsouth.net Feb. 9, 2026

Feb. 9, 2026

I've been going in circles between mailman and postfix trying to get things working. My current condition is that either mailman is putting incoming mail in the bit bucket or postfix is not sending incoming mail to mailman. According to the postfix forum my mailman configuration is messed up but it was auto generated by the installer. Supposedly these entries should not be in /opt/mailman/mm/var/data/postfix_lmtp or rather transport_maps and/or local_recipient_maps. # Aliases which are visible only in the @gmail.com domain. lllllllllll(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-bounces(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-confirm(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-join(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-leave(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-owner(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-request(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-subscribe(a)gmail.com lmtp:[127.0.0.1]:8024 lllllllllll-unsubscribe(a)gmail.com lmtp:[127.0.0.1]:8024 And relay_domains shouldn't have this entry either in /opt/mailman/mm/var/data/postfix_domains in relay_domains: gmail.com gmail.com Clearly my postfix configuration is messed up but since this was all auto generated I don't know what to do.

4 12

Re: Expire non-members
by Mark Sapiro Feb. 9, 2026

Feb. 9, 2026

On 2/8/26 18:36, John Price wrote: > I notice that a lot of the non-members (I didn't look at all ~230) don't > seem to be in the master user list. Maybe until they confirm the user > record is not created yet? If the address was just added from a nonmember post, it won't have a user record. As I said before, there is no pending confirmation for the nonmember. The address has been added as a nonmember and that's it. They won't be added as a member unless they request subscription at which point they will have to confirm if the list's subscription policy requires it. > Anyway, I'd love a subscribe timestamp so I could calculate how long it > has been, but I can rig something up with a daily cron job and a simple > DB of emails and the date it noticed them on the non-members list and > delete them after a few days. Thanks for the info! For the nonmember, nonmember.address.registered_on is probably the timestamp you are looking for. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Re: Expire non-members
by Stephen J. Turnbull Feb. 9, 2026

Feb. 9, 2026

John Price writes: > I notice that a lot of the non-members (I didn't look at all ~230) > don't seem to be in the master user list. Maybe until they confirm > the user record is not created yet? The User object is created. User records don't get confirmed, the addresses that are attached to them get confirmed. > Anyway, I'd love a subscribe timestamp so I could calculate how > long it has been Some of the object records have creation timestamps in the SQL database, but they are not exposed in the web UI. They're not very interesting to human beings and take up a lot of UI space, even if you only display the date. Also, I'm not sure whether the core database records timestamps, although I'm pretty sure Django does for both creation and confirmation. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 0

Expire non-members
by John Price Feb. 8, 2026

Feb. 8, 2026

Is there a way to expire and delete (in mailman3 or via cron) non-members? I've been running mailman3 for a couple of weeks now on a few mailing lists, and on my big list specifically I'm seeing lots of spam to the gcfl-join(a)gcfl.net email alias, which creates these non-members, but they never confirm their subscription, so they remain in non-member limbo. Thank you, John -- Is it my imagination, or do buffalo wings taste like chicken? 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!

3 3

[Mailman-Users] VERP on Mailman 3
by Stephen J. Turnbull Feb. 8, 2026

Feb. 8, 2026

Redirecting to Mailman 3 users <mailman-users(a)mailman3.org>. John Price via Mailman-Users writes: > I attempted to setup VERP on Mailman3 and it doesn't seem to be > changing the sender address. Please explain why you think that. Note: The sender address that is changed is the envelope address. You won't see it in the message headers in most cases. There should be relevant log messages in your MTA log that have the envelope sender as "from=<...sender...>" in the case of Postfix. I forget what Exim4 and Sendmail use. > What else should I provide that will help? - Log entries from Mailman and the MTA pertaining to one or more messages that should have been VERPed. - What is your MTA? - What is the setting for recipient_delimiter (if Postfix, or the equivalent for other MTAs)? - How did you install Mailman? Note that if you installed from Debian packages, the first thing you should do is contact the Debian maintainers for their packages. The rest of this message is preserved from the original post to mailman-users(a)python.org for completeness. Steve > I don't know what the problem is. > > I am using the '_' character for my verp delimiter. This is what I > have been using with mailman2 for about 15 years. It has been > working perfectly. > > I'm using Postfix 3.10.5. > > $ mailman conf | grep verp > [mta] verp_confirm_format: ${address}_${cookie} > [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^_]+?)_(?P<cookie>[^@]+)@.*$ > [mta] verp_confirmations: yes > [mta] verp_delimiter: _ > [mta] verp_delivery_interval: 1 > [mta] verp_format: ${bounces}_${local}=${domain} > [mta] verp_personalized_deliveries: yes > [mta] verp_probe_format: ${bounces}_${token}@${domain} > [mta] verp_probe_regexp: ^(?P<bounces>[^_]+?)_(?P<token>[^@]+)@.*$ > [mta] verp_probes: yes > [mta] verp_regexp: ^(?P<bounces>[^_]+?)_(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ > > $ mailman info > GNU Mailman 3.3.10 (Tom Sawyer) > Python 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0] > config file: /etc/mailman3/mailman.cfg > db url: mysql+pymysql://mm3:blah@localhost/mailman3?charset=utf8&use_unicode=1 > devmode: DISABLED > REST root url: https://localhost:8001/3.1/ > REST credentials: admin:password > > $ cat /etc/debian_version > 13.3 > > TIA, > John -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 2

Permissions Error on /var/mail/mailman
by dap1＠bellsouth.net Feb. 5, 2026

Feb. 5, 2026

I am going in circles between postfix issues and mailman. However, before I continue with postfix debugging I want to resolve this first as it may be related for all I know. I'm getting this error in the postfix mail log: 2026-02-01T11:00:10.106626-05:00 dap002 postfix/local[113730]: 01623500076: to=<mailman(a)myhost.localdomain>, orig_to=<mailman>, relay=local, delay=0.16, de lays=0.11/0.01/0/0.04, dsn=5.2.0, status=bounced (cannot update mailbox /var/mail/mailman for user mailman. cannot open file: Permission denied) I'm not sure why mailman is trying to write to that file but it is owned by root:mail. It is obvious why permission is denied to mailman. Is that directory really part of mailman3 and if so what should ownership and permissions be? If not then why is mailman trying to write to it? That path does not appear in any of the files in /etc/mailman3.

4 8

Is there an option to "disable" a list temporarily? (feature request?!)
by Christian Schneider Feb. 4, 2026

Feb. 4, 2026

Hello dear Mailman Team, I scanned through the web interface of my mailman instance... and I did not find an option to disable a list temporarily ("sending" and "access to web interface")... This might come in handy when a list is abused for sending spams or when a list owner wants his/her list to be removed... Instead of removing the list instantly I would disable it for three months first... (You never know with users... ;-) ) Preferably I would backup the list (settings and members) and the archives, but as seen in the discussion there is actually no backup mechanism for lists... Is there an option to disable a list (except from resetting passwords and remove/disable mail aliases)? If not I'd like to hand this in as a feature request... xD Thank you very much and kind regards Christian

4 6