June 2025 - Mailman-users - lists.mailman3.org

redirecting -bounces replies
by Hirayama, Pat June 26, 2025

June 26, 2025

Greetings, Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? In Mailman2, I know that I could do that by modifying the aliases table. I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location. Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

4 5

Change the default value for the General Archive Policy
by Markus Grandpré June 26, 2025

June 26, 2025

Dear list, currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public archives". I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? In Debian 12 I find in </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: mlist_properties = ['archivers'] archive_policy_choices = ( ('public', _('Public archives')), ('private', _('Private archives')), ('never', _('Do not archive this list')), ) archive_rendering_mode_choices = ( ('text', _('Plain text')), ('markdown', _('Markdown text')), ) archive_policy = forms.ChoiceField( choices=archive_policy_choices, widget=forms.RadioSelect, label=_('Archive policy'), help_text=_('Policy for archiving messages for this list'), ) but have no idea how to change the settings here. Your help is very appreciated. Best regards, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

4 6

Caching problem with templates
by Mark June 26, 2025

June 26, 2025

Caching problem with templates. GNU Mailman 3.3.10 Python 3.11.2 Postorius Version 1.3.13 Venv installation per docs Hi All, A footer template is created and initially it works as expected. Editing the footer template sees the new content written to the database, In addition to viewing the edited content in the database, the new template can also be viewed in Lynx on localhost at: http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer The problem is that the original template is being cached somewhere and the old footer persists in new emails. In trying to get the edited footer to show in the emails I've restarted mailman3/mailmanweb, rebooted the server - but no joy. Any advice on how to flush the cache or hammer this gremlin greatly appreciated. Thanks, Mark

1 0

Block members from sending cc's and bcc's
by Cathryn McGuire June 23, 2025

June 23, 2025

Hi everyone, Using Mailman 3 with Affinity web interface and we want to stop our members from sending to cc: or bcc: We've found the Header Filter and cc and bcc appear in it. Tried to configure it to "hold for moderation," but it hasn't worked. Partly because we don't understand what to put in the Pattern input box. I put in cc: because it requires something. Can anyone advise? Cheers, Cathryn

2 8

Creating users via RestAPI / User-Management - a bunch of questions
by Christian Schneider June 23, 2025

June 23, 2025

Dear Mark and companions, somehow I can not cope with the user management... (I am running a venv-installation, latest stable versions) I read this manual: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… and played with the RestAPI calls... I know about the fine grained differences between user and member, admin/owner, superuser... and about the two user databases in PostgreSQL and Django-Framework. What I stumble upon is the RestAPI calls to create a "working" user (with the ability to login via WebUI). When I follow the manual (from the url above) I create a user (including password) that appears in the PostgreSQL database. (And this user is visible on the User-URL (https://example.com/mailman3/users)) Even when I (via WebUI) set the user as "approved" this user is not able to log in... I assume this restriction is in accordance to the fact that there is not equivalent Django user. (There was a mail in the archive of the MM3 user group...stating that one has to use the Django RestAPI to create the appropriate user) When I create the user using the WebUI (https://example.com/accounts/signup/?next=/mailman3/lists/) the new user is created in the right (complete) way...appearing in the PostgreSQL database and as a user in Django. How is this sync between the two databases realized? (The Django user also has the correct status (no staff status / no superuser status / just active status) how is this realized?) As I am not very familiar with python programming (I know Perl/Java/C++ and have an (maybe outdated) concept of OOP), is there a quick way to implement this kind of sync by copying the register logic from mailman's python action script for registering? Other questions: Will there be a create_admin_user-script that is callable via CLI (like createsuperuser or create_list)? (This script ought create a user in PostgreSQL and as Django user) How will a social account provider (like oidc) linkage (in Django) fit in this concept? Will oidc-accounts be copied to the Django's user database (or PostgreSQL db) or is it an on-the-fly check against the oidc-provider? (I assume second option) What are the status-flags (staff status/superuser status/active status) of the linked oidc-accounts? (Can I specify the status flags?) A conceptual thought: When "user1" (with email user1(a)example.com) is known to django via oidc linkage and I create "user1" (also with email user1(a)example.com) via RestAPI calls (following the url https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) do I have a "complete" user then? I mean a user who is able to login and who can be assigned to a list as admin (e.g.) (In this case I would not have to care about the Django user database... ;-)) Thank you for some clarifying hints... :-) Chris

3 3

two signatures on sent mail?
by STR June 20, 2025

June 20, 2025

Hi, I am a very non-savvy mailman list user. I am trying to set up a list via cPanel but when I send emails there are two signatures. One is my usual signature and the other, below, is appended by Mailman and includes an http link to a non-existent page on my website. How do I strip the auto signature, just leaving my own? I use Mailman via cPanel on two separate hosting accounts. One works fine and this new one attaches the list address. I can't see what I did differently with the first! any help gratefully received Kate

3 3

footer template priority
by Sam Darwin June 20, 2025

June 20, 2025

It seems templates can be configured in the filesystem or via postorius. When I place a footer template in the filesystem it worked fine. Then without adjusting any configuration, without removing that, I tried to use the postorius control panel to add a footer template, which ends up in the database, both the core and web databases. But emails stop getting sent out. Emails were posted into Hyperkitty, but not mailed out via postfix. Whatever system logs I have access to, I have checked. There are no apparent errors anyplace. Perhaps I didn't look in the right places. The problematic email arrives, is posted to Hyperkitty, but isn't emailed out to subscribers. As if the template broke something. I remove the template from the postorius UI. Those queued emails are instantly sent! The template said "test content". No variables. I checked on the server for "queued emails" and did not find those either, in postfix or mailman. Mysterious. The phenomenon is repeatable on this server. Add a footer template, emails stop.

2 6

Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)
by Jan Eden June 17, 2025

June 17, 2025

Hi, after installing Mailman 3 in a new virtual environment, I ran into the compatibility issues with django-allauth discussed by Andreas Vetter and Mark Sapira on this list in February[1] and in March[2] – 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*'] – and solved them with the additions to /etc/mailman3/settings.py suggested by Mark: del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} del ACCOUNT_EMAIL_REQUIRED ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] In the second list thread, Mark linked to the current (patched) version of mailman-web's mailman.py[3], which addresses the deprecation of ACCOUNT_AUTHENTICATION_METHOD, but not of ACCOUNT_EMAIL_REQUIRED. Is there any reason why the patch fixes only one of the two issues? - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [3] https://gitlab.com/mailman/mailman-web/-/blob/c8b9aef1704b75b1cb6d0c925855a…

4 5

Trouble Installing Mailman3
by Henry Hartley June 13, 2025

June 13, 2025

I'm having problems installing mailman3 following the instructions on https://docs.mailman3.org/en/latest/install/virtualenv.html Everything goes well until I get to the Installing Mailman Core<https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> step, which has me do the following in my venv environment: (venv)$ pip install wheel mailman psycopg2-binary Ubuntu 24.04.02 LTS Python 3.12.3 pip version 24.0 First, I was getting problems because my company firewall was blocking outbound traffic. I got that taken care of. Next, I was seeing certificate errors, saying there was a self-signed certificate: WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))': /simple/wheel/ Could not fetch URL https://pypi.org/simple/wheel/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/wheel/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))) - skipping When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) ERROR: No matching distribution found for wheel The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I've rerun the apt install of python3-dev and python3-venv to make sure those are present and up to date. Any help you can provide will be greatly appreciated. -- Henry Hartley Westat

5 12

mail loops back to myself
by Florian Sukup June 13, 2025

June 13, 2025

Hi, I've spent hours on finding the error but no success. I hope you can help: I am running Debian with older version of mailman3 (3.3.3) and postfix (3.5). Postfix on its own is working fine. I set up mailman, created a site/domain (lists.yyy.com) My hostname is host.xxx.com . My IP has a RDNS entry: reverse.rrr.com . When I send an email to my mailing list mylist(a)lists.yyy.com I receive an error email. The logfile says the following: ... Jun 9 00:23:38 arvak postfix/smtpd[]: connect from host.xxx.com[m.y.i.p] Jun 9 00:23:38 arvak postfix/relay/smtp[]: warning: host reverse.rrr.com[178.251.71.190]:25 greeted me with my own hostname host.xxx.com Jun 9 00:23:38 arvak postfix/relay/smtp[]: warning: host reverse.rrr.com[m.y.i.p]:25 replied to HELO/EHLO with my own hostname host.xxx.com Jun 9 00:23:38 arvak postfix/relay/smtp[]: 094895FADB: to=<mylist(a)lists.yyy.com>, relay=reverse.rrr.com[m.y.i.p]:25, delay=0.06, delays=0.03/0.01/0.02/0, dsn=5.4.6, status=bounced (mail for lists.yyy.com loops back to myself) Jun 9 00:23:38 arvak postfix/smtpd[114119]: disconnect from host.xxx.com[m.y.i.p] ehlo=1 quit=1 commands=2 ... The MX record of lists.yyy.com points to reverse.rrr.com. Not sure if this is the best idea? Can anyone give me a hint where to search for this error? Thanks a lot in advance! Florian.

2 13