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

after last upgrade I've got a CSRF failed verification
by Guillermo Hernandez (Oldno7) Sept. 5, 2025

Sept. 5, 2025

I did upgrade one of my mailman3 server after Abhilasj announcement: "I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 1 <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> 2. Postorius 1.3.7 2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5]" I did it via pip and all seems to be working, but when I try to discard or accept any message via postorius it shows a Forbidden 403 error CSRF verification failed. In my settings.py I have commented out these variables: # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' I've been messing with them whith no results. It's like it lacked some value in some template... Can someone, please, point me in the right direction? Thanks in advance -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 8

mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email
by Stefan Bauer Sept. 5, 2025

Sept. 5, 2025

Dear Users, trying to update mailman3 to lastest version, we fail during mailman-web migrate with: Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower...Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", line 328, in execute return super().execute(query, params) sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email We found a workaround to fake the migration with migrate --fake Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower... FAKED Applying account.0007_emailaddress_idx_email... FAKED Applying account.0008_emailaddress_unique_primary_email_fixup... FAKED Applying account.0009_emailaddress_unique_primary_email... FAKED Applying django_q.0015_alter_schedule_schedule_type... FAKED Applying django_q.0016_schedule_intended_date_kwarg... FAKED Applying django_q.0017_task_cluster_alter... FAKED Applying django_q.0018_task_success_index... FAKED Applying postorius.0019_alter_emailtemplate_data... FAKED And mailman 3 is still processing mails. I'm unsure if i should recover from snapshot or keep it going? Could this be some duplicate users with same mail-address? I have at least spotted one user and delete him. thank you. Stefan

3 4

[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!
by Wikinaut Sept. 2, 2025

Sept. 2, 2025

[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.av-huette.de/settings/message_acceptance Full error stack (redacted) see https://dpaste.com/CEFXPNP67.txt Internal Server Error: /mailman3/lists/test2.*****/settings/message_acceptance As far as I remember, I removed every member of that test2 list. I think, my bug report could be of interest to fix a (probably) lurking bug. Everything works here, but last week I had this error

5 5

Mailing lists as the main collaboration centre at SME
by Rodrigo Camacho Aug. 31, 2025

Aug. 31, 2025

Hello all, I own and run a small company (lanao.org) I am looking for companies which have put mailing lists not only as a form of general announcement but especially as the main way to collaborate. I am thinking of moving my team to a model like that and would love to read about some best practices or strong opposition to the idea. I am hopeful that out there there are companies which have resisted the Microsoft Teams virus. If your company uses mailing lists to run, please reach out. We are currently using Gitlab issues to collaborate which has been quite successful. I would be very interested to trade tips. Best wishes, Rodrigo

3 5

Stalwart plugin
by info＠joergschulz.de Aug. 30, 2025

Aug. 30, 2025

Hi all, I'm just reviewing Stalwart as a many-in-one mailing system. Did anybody yet succeed in plugging mailman into stalwart (the incoming bit seems to be difficult)?

3 2

New subscribed (by invitation) user: no password received in invitation/welcome e-mail. Postorius sign up / password reset broken
by ^m'e Aug. 30, 2025

Aug. 30, 2025

Hi there, I migrated form MM2.1 to MM3.3.10 on Debian Trixie (mariadb backend) -- I know that's a bit unorthodox to ask here for help on a non venv-based installation, but hopefully I'll first gain a bit of insight of MM3 in order to formulate a more precise request to Debian maintainers. ## Issue #1. A newly invited (from Postorius mass subscription page) and confirmed user doesn't get any password in their invitation/welcome e-mail. I guess that's because MM3 allows a user to subscribe without having an account, right? Else, there's a problem. ## Issue #2 Anyway, if that new user asks for a password reset on Postorius they get "Server error An error occurred while processing your request." Log shows: ``` ERROR 2025-08-29 17:59:17,227 173488 django.request Internal Server Error: /accounts/password/reset/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 105, in view return self.dispatch(request, *args, **kwargs) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 46, in _wrapper return bound_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 144, in dispatch return handler( form.save(self.request) ~~~~~~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 633, in save adapter.send_password_reset_mail(user, email, context) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 577, in send_password_reset_mail return self.send_mail("account/email/password_reset_key", email, context) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 201, in send_mail msg.send() ~~~~~~~~^^ File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 299, in send return self.get_connection(fail_silently).send_messages([self]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 134, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 152, in _send self.connection.sendmail( ~~~~~~~~~~~~~~~~~~~~~~~~^ from_email, recipients, message.as_bytes(linesep="\r\n") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3.13/smtplib.py", line 861, in sendmail self.ehlo_or_helo_if_needed() ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/smtplib.py", line 611, in ehlo_or_helo_if_needed if not (200 <= self.ehlo()[0] <= 299): ~~~~~~~~~^^ File "/usr/lib/python3.13/smtplib.py", line 451, in ehlo self.putcmd(self.ehlo_msg, name or self.local_hostname) ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/smtplib.py", line 378, in putcmd self.send(f'{s}{CRLF}') ~~~~~~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3.13/smtplib.py", line 365, in send raise SMTPServerDisconnected('please run connect() first') smtplib.SMTPServerDisconnected: please run connect() first ``` The same happens if the new users tries to sign up. Any idea? Cheers -- Marco

3 3

Subscription Request asking for Confirmation instead of Moderation
by Henry Hartley Aug. 29, 2025

Aug. 29, 2025

We have a list where the Subscription Policy (Settings -> Member Policy -> Subscription Policy) is set to "Moderate" and when I send a message to LISTNAME-join(a)example.com<mailto:LISTNAME-join@example.com> (not the real domain, obviously) everything works as expected and the user shows up in the Pending Approval list. We have a Drupal website that allows users to submit a form that, among other things, sends a subscription request to our Mailman3 'join' address. When that happens, however, instead of going to the Pending Approval list, the name is shows on the Pending Confirmation page. We don't send a Welcome message so as far as I can tell, they do not get an email asking them to confirm their email address. Two questions: 1. Are there particular headers that are causing the email to go to the Confirmation page instead of the Approval page? Or are there particular headers we can add that will help with this? 2. Is there any way for us to move an address from the Confirmation Pending page to confirmed on the backend (preferably through the web interface, but on the server itself, if necessary)? Here are the headers sent with the subscriber's email address changed to FirstLast(a)SCHOOL.edu<mailto:FirstLast@SCHOOL.edu> and our BCC mailbox domain changed to COMPANY.com. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: 8Bit X-Mailer: Drupal Return-Path: FirstLast(a)SCHOOL.edu<mailto:FirstLast@SCHOOL.edu> Sender: FirstLast(a)SCHOOL.edu<mailto:FirstLast@SCHOOL.edu> From: FirstLast(a)SCHOOL.edu<mailto:FirstLast@SCHOOL.edu> Bcc: mailman-noreply(a)COMPANY.com<mailto:mailman-noreply@COMPANY.com> -- Henry Hartley Westat RB 2151

3 8

Today no question, but my toolbox: set "global" user preferences; list or delete held messages
by Wikinaut Aug. 27, 2025

Aug. 27, 2025

After some (sorry for bothering you) questions here, I was able to set up a mailman3 system which I regard as perfect for my use. Perhaps, you had similar problems with your installation, especially when coming from mailman2 and, like me, from majordomo...... I collected a lot of information which was presented in this mailling list archive here and also answers of my questions (thanks Mark and others) News: https://github.com/Wikinaut/mailman3-tools has all of these tools. README says: Scripts for maintenance or setting-up of modern mailman3 instances set preferences for all users list held messages delete held messages older n days My setting is strictly as described in the documentation: mailman3 + postorius/hyperkitty are installed via pip in an (venv) /opt/mailman/ My user scripts and a huge mailing list generator (not published here) are in a directory apart from that: user maillistgen home directory /home/maillistgen user maillistgen has some sudo rights set uo in /etc/sudoers a wrapper script is /home/maillistgen/run_mailman.sh which sets the correct path for Python, mailman3 and the (venv). I hope, you like my tiny part of contribution and attribution back to Mark.

1 0

Today no question, but my toolbox: set "global" user preferences; list or delete held messages
by Wikinaut Aug. 27, 2025

Aug. 27, 2025

After some (sorry for bothering you) questions here, I was able to set up a mailman3 system which I regard as perfect for my use. Perhaps, you had similar problems with your installation, especially when coming from mailman2 and, like me, from majordomo...... I collected a lot of information which was presented in this mailling list archive here and also answers of my questions (thanks Mark and others) News: https://github.com/Wikinaut/mailman3-tools has all of these tools. README says: Scripts for maintenance or setting-up of modern mailman3 instances set preferences for all users list held messages delete held messages older n days My setting is strictly as described in the documentation: mailman3 + postorius/hyperkitty are installed via pip in an (venv) /opt/mailman/ My user scripts and a huge mailing list generator (not published here) are in a directory apart from that: user maillistgen home directory /home/maillistgen user maillistgen has some sudo rights set uo in /etc/sudoers a wrapper script is /home/maillistgen/run_mailman.sh which sets the correct path for Python, mailman3 and the (venv). I hope, you like my tiny part of contribution and attribution back to Mark.

1 0

How can i suppress sending moderation mail to all owners?
by Markus Grandpré Aug. 25, 2025

Aug. 25, 2025

Dear list members, How can I configure the list settings the way that emails intended for moderators are delivered only to them, and not to the owners/administrators of the list? Best, Markus Grandpré -- Markus Grandpré (he/him) Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration 78457 Konstanz Tel: +49 7531 88-4342D

4 4