- Mailman-users - lists.mailman3.org

How to remove Held Unsubscriptions
by Mark 06 Jan '25

06 Jan '25

Hi As a moderator I receive an email each day for "Held Unsubscriptions" for a subscriber that was unsubscribed by the Owner sometime ago (using "Mass operations"). +++++++++++++++++++++++++++++++ The listname(a)domain.com list has 1 moderation requests waiting. Held Unsubscriptions: User: bart(a)example.com Please attend to this at your earliest convenience. +++++++++++++++++++++++++++++++ There is nothing showing under "Subscription requests > Pending approval". Could anyone tell me how I can stop these email notifications? I have access to the mailman shell and the databases. Thanks, Mark

4 7

possible backscatter attack using Mailman3 servers
by David Newman 05 Jan '25

05 Jan '25

Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing about 20-30 entries per day in the Postfix queue where it appears a Gmail user signs up for a mailing list that requires confirmation, and Gmail responds that the user is too busy to handle requests. There are no publicly advertised email lists on this server, and I don't ever see anything in the Mailman logs indicating the user ever tried signing up. I've pasted the mail.log transaction below, with only slight obfuscation: - "mail10.example1.com" is this server's canonical hostname - lists are hosted on "lists.example2.com" and "mail.example3.com" - "someuser9413(a)gmail.com" is the user supposedly signing up Thanks in advance for clues on determining where these requests are coming from, and how I might block them. I have a strong interest in having my server not amplifying backscatter traffic like this. Alternatively, if this is a Postfix problem, please let me know that too. dn Jan 3 10:29:22 mail10 postfix/postscreen[4052406]: CONNECT from [::1]:55274 to [::1]:25 Jan 3 10:29:22 mail10 postfix/postscreen[4052406]: WHITELISTED [::1]:55274 Jan 3 10:29:22 mail10 postfix/postscreen[4052406]: using backwards-compatible default setting respectful_logging=no for client [::1]:55274 Jan 3 10:29:22 mail10 postfix/smtpd[4052407]: connect from localhost[::1] Jan 3 10:29:22 mail10 postfix/smtpd[4052407]: discarding EHLO keywords: CHUNKING Jan 3 10:29:22 mail10 postfix/smtpd[4052407]: 4YPsYG1X2xzHQfw: client=localhost[::1] Jan 3 10:29:22 mail10 postfix/cleanup[4052628]: 4YPsYG1X2xzHQfw: message-id=<173592896219.2314.15515568084960961396(a)mail10.example1.com> Jan 3 10:29:22 mail10 postfix/smtpd[4052407]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Jan 3 10:29:22 mail10 postfix/qmgr[3635053]: 4YPsYG1X2xzHQfw: from=<postmaster(a)example2.com>, size=901, nrcpt=1 (queue active) Jan 3 10:29:22 mail10 postfix/10025/smtpd[4052639]: connect from localhost[127.0.0.1] Jan 3 10:29:22 mail10 postfix/10025/smtpd[4052639]: discarding EHLO keywords: CHUNKING Jan 3 10:29:22 mail10 postfix/10025/smtpd[4052639]: 4YPsYG33SkzHSdN: client=localhost[127.0.0.1] Jan 3 10:29:22 mail10 postfix/cleanup[4052628]: 4YPsYG33SkzHSdN: message-id=<173592896219.2314.15515568084960961396(a)mail10.example1.com> Jan 3 10:29:22 mail10 postfix/10025/smtpd[4052639]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Jan 3 10:29:22 mail10 postfix/qmgr[3635053]: 4YPsYG33SkzHSdN: from=<postmaster(a)example2.com>, size=1939, nrcpt=1 (queue active) Jan 3 10:29:22 mail10 amavis[4017234]: (4017234-09) Passed CLEAN {RelayedInternal}, MYNETS/MYUSERS LOCAL [::1]:55274 ESMTP/ESMTP <postmaster(a)example2.com> -> <someuser9413(a)gmail.com>, (), Queue-ID: 4YPsYG1X2xzHQfw, Message-ID: <173592896219.2314.15515568084960961396(a)mail10.example1.com>, mail_id: P9P7GnranpAW, b: Zp0DirpBL, Hits: -, size: 900, queued_as: 4YPsYG33SkzHSdN, Subject: "[mail.example3.com] Please Confirm Your Email Address", From: <postmaster(a)example2.com>, helo=mail10.example1.com, dkim_new=dkim:example1.com, 217 ms Jan 3 10:29:22 mail10 postfix/amavis/smtp[4052633]: 4YPsYG1X2xzHQfw: to=<someuser9413(a)gmail.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.24, delays=0.02/0/0.01/0.21, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4YPsYG33SkzHSdN) Jan 3 10:29:22 mail10 postfix/qmgr[3635053]: 4YPsYG1X2xzHQfw: removed Jan 3 10:29:22 mail10 postfix/smtp[4052642]: Trusted TLS connection established to gmail-smtp-in.l.google.com[2607:f8b0:4023:c0d::1b]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256 Jan 3 10:29:22 mail10 postfix/smtp[4052642]: 4YPsYG33SkzHSdN: host gmail-smtp-in.l.google.com[2607:f8b0:4023:c0d::1b] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, go to 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate 98e67ed59e1d1-2f2ed632fdfsi39876934a91.55 - gsmtp (in reply to RCPT TO command) Jan 3 10:29:22 mail10 postfix/smtp[4052642]: Trusted TLS connection established to gmail-smtp-in.l.google.com[142.251.2.27]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256 Jan 3 10:29:22 mail10 postfix/smtp[4052642]: 4YPsYG33SkzHSdN: to=<someuser9413(a)gmail.com>, relay=gmail-smtp-in.l.google.com[142.251.2.27]:25, delay=0.46, delays=0.01/0/0.4/0.04, dsn=4.2.1, status=deferred (host gmail-smtp-in.l.google.com[142.251.2.27] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, go to 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate d2e1a72fcca58-72aad8fd529si37008995b3a.196 - gsmtp (in reply to RCPT TO command))

3 4

Random lmtp Timeout and Long Message Processing times
by Taber, Douglas R 02 Jan '25

02 Jan '25

Hello- We’re seeing a seemingly random issue with message acceptance on our mailman instance where some messages sent from postfix to the lmtp listener timeout. It’s not consistent to any specific list or time of day, and messages are accepted on the next attempt by postfix to deliver the message to the lmtp. Additionally, there seems to be a similarly random delay in accepting and processing messages before they are sent to the list moderators or list members. The mailman smtp log snippet shows it stop receiving data prior to the DATA portion of the message after a 15min timeout: Jan 02 07:56:36 2025 (3601529) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jan 02 07:56:36 2025 (3601529) Peer: ('127.0.0.1', 45574) Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) handling connection Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) << b'220 lists.renci.org GNU Mailman LMTP runner 2.0' Jan 02 07:56:36 2025 (3601529) _handle_client readline: b'LHLO lists.renci.org\r\n' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) >> b'LHLO lists.renci.org' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) << b'250-lists.renci.org' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) << b'250-SIZE 33554432' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) << b'250-8BITMIME' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) << b'250 HELP' Jan 02 07:56:36 2025 (3601529) _handle_client readline: b'MAIL FROM:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws<mailto:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws> SIZE=20254\r\n' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) >> b'MAIL FROM:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws<mailto:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws> SIZE=20254' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) sender: 010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000(a)mail.verify.signin.aws<mailto:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws> Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) << b'250 OK' Jan 02 07:56:36 2025 (3601529) _handle_client readline: b'RCPT TO:adcircaws@lists.RENCI.org<mailto:adcircaws@lists.RENCI.org>\r\n' Jan 02 07:56:36 2025 (3601529) ('127.0.0.1', 45574) >> b'RCPT TO:adcircaws@lists.RENCI.org<mailto:adcircaws@lists.RENCI.org>' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 45574) recip: adcircaws(a)lists.RENCI.org<mailto:adcircaws@lists.RENCI.org> Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 45574) << b'250 Ok' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 45574) EOF received Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 45574) connection timeout Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 45574) Connection lost during _handle_client() Jan 02 08:12:26 2025 (3601529) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 45574) connection lost Jan 02 08:12:26 2025 (3601529) Peer: ('127.0.0.1', 33138) Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) handling connection Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'220 lists.renci.org GNU Mailman LMTP runner 2.0' Jan 02 08:12:26 2025 (3601529) _handle_client readline: b'LHLO lists.renci.org\r\n' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) >> b'LHLO lists.renci.org' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'250-lists.renci.org' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'250-SIZE 33554432' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'250-8BITMIME' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'250 HELP' Jan 02 08:12:26 2025 (3601529) _handle_client readline: b'MAIL FROM:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws<mailto:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws> SIZE=20254\r\n' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) >> b'MAIL FROM:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws<mailto:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws> SIZE=20254' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) sender: 010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000(a)mail.verify.signin.aws<mailto:010001942716aa05-637d21f8-9794-473f-9e8b-06ca08025ef1-000000@mail.verify.signin.aws> Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'250 OK' Jan 02 08:12:26 2025 (3601529) _handle_client readline: b'RCPT TO:adcircaws@lists.RENCI.org<mailto:adcircaws@lists.RENCI.org>\r\n' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) >> b'RCPT TO:adcircaws@lists.RENCI.org<mailto:adcircaws@lists.RENCI.org>' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) recip: adcircaws(a)lists.RENCI.org<mailto:adcircaws@lists.RENCI.org> Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'250 Ok' Jan 02 08:12:26 2025 (3601529) _handle_client readline: b'DATA\r\n' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) >> b'DATA' Jan 02 08:12:26 2025 (3601529) ('127.0.0.1', 33138) << b'354 End data with <CR><LF>.<CR><LF>' Anyone have any thoughts on next troubleshooting steps on this one? Thanks

1 0

Hyperkitty performance problem
by Tobias Diekershoff 01 Jan '25

01 Jan '25

Hey all, last week we caught some AI bots causing high LOAD on our mailman3 servers archive, that we blocked with nginx rules. I'm not sure if it is related to this incident, but we noticed this when analyzing the log files at the time. In the mailman.log hyperkitty is listed 10k times and more to archive a single mail over the time of 2h, seemingly all with the same process ID > (1186) HyperKitty archived message [...] The mailman3-web.log has matching log entries that the mail was archived > hyperkitty.views.mailman Archived message every 0.5 seconds. In the web interface to the archive, the mail is only listed once though. My suspicion is, that these archiving processes are now overloading the system, preventing a timely catching up work of the queued messages. I could not find anything in the Mailman3 nor Hyperkitty documentation to better distribute the system resources to the Mailman runner or prevent Hyperkitty to restart archiving a mail over and over again. Any hint about where to look for the reason of this is highly appreciated. Best, Tobias -- Tobias Diekershoff >>> System Hacker Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | fsfe.org/support OpenPGP-Key ID ... 0x25FE376FF17694A1 Fingerprint ...... 23EE F484 FDF8 291C BA09 A406 25FE 376F F176 94A1

5 13

mailman transfer from 2to3
by Daniel Germer 28 Dec '24

28 Dec '24

Hello all, I am new to mailman3, once upon a time I had mailman installed on my server, but had trouble with many things, especially virtual hosts not possible in mailman2... However on https://docs.mailman3.org/en/latest/pre-installation-guide.html#what-do-i-n… are no system requirements for the installation. I assume, that I cannot just install mailman3 on a regular webhoster, but there is no section: You need to have root access to a Linux system with at least 8/16/31/64GB RAM and at least 1/2/5/7 GB of free diskspace (ssl or hard-disk?) You need so and so much for 100/1000 Lists with 10/100/1000 Users each and 5/50/500 Mailings per day... where do I find that information? what is the smallest possible machine to run mailman3 on? Can I run it on a raspberry pi? regards, Daniel

1 0

Clean-up of non-members
by Torge Riedel 26 Dec '24

26 Dec '24

Dears, I am currently cleaning up a huge list of non-members. In contrast to the members list where I can select multiple entries and delete them at once, this is not possible in the list of non-members? Can this be enabled in a future release? Thank you and kind regards Torge

3 14

MTA setup
by Arte Chambers 24 Dec '24

24 Dec '24

I've got a new installation of Mailman 3 setup, however I am having some issues I'm not sure how to troubleshoot. Mailman is successfully sending invite emails however user messages sent to the list are not being sent to subscribers. Also in Hyperkitty none of my test messages to the list are showing up in the archive. I am using Postfix with an SMTP relay hosted at Brevo.com (formally sendinblue). Brevo's logs show the message getting rejected Log from brevo.com (SMPT Relay) Sent on 17-11-2024 21:49:16 From listmember(a)gmail.com To listmember(a)gmail.com Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= BJ7Q(a)mail.gmail.com> 17-11-2024 21:49:16 Sending has been rejected because the sender you used listmember(a)gmail.com is not valid. Validate your sender or authenticate your domain >>>Postfix main.cf # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 3.6 on # fresh installs. compatibility_level = 3.6 # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level=may smtp_tls_CApath=/etc/ssl/certs smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = list.louisvillecommunitygrocery.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = $myhostname mydestination = $myhostname, list.louisvillecommunitygrocery.com, localhost.louisvillecommunitygrocery.com, , localhost mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all # Mailman3 configs # Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains #SMPT Relay Brevo relayhost = [smtp-relay.sendinblue.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_tls_security_level = encrypt smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt *In closing*, can anyone point me in the right direction for further troubleshooting on this issue? Thank you, Paul 'Arte Chambers' Robey

2 12

Suggestion on Mailing Lists page
by Alain D D Williams 24 Dec '24

24 Dec '24

This is the page that lists the mailing lists that I have. It would be really useful if there was an indication next to each list if that list required attention, eg an email awaiting moderation. Have a good Xmas everyone. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 1

MM2 to MM3 Archives Loading
by Joshua Bushe 22 Dec '24

22 Dec '24

Hi everyone, I’ve successfully converted a list from Mailman 2 to Mailman 3, and most things are working smoothly. However, I’m encountering an issue with the archives in the GUI: Problem: The archives don’t load on the overview page. Odd Behavior: If I use the search function, the archives appear as expected, but they remain invisible on the main overview. Has anyone encountered this issue or have suggestions for troubleshooting? Thanks in advance for your help!

5 15

Flooded non-members with "prvs=<number>=<mail>"
by Torge Riedel 22 Dec '24

22 Dec '24

Dears, I checked the non-members list of all my mailman3 lists and found a lot entries like "prvs=<number>=<mail>", the <mail> is always an address from @freenet.de A quick research mentions something related to bouncing and that such mails should be blocked/filtered. But no further details. Can you give a hint where I need to change what to block such mails and avoid that such entries floods the non-members list? Thank you and kind regards Torge

2 1

Poor rendering of disabled registration page
by Torge Riedel 22 Dec '24

22 Dec '24

Dears, I have set ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in my settings.py, so clicking on the "Registration+" button shows a page that registration is disabled: 1. The page has a poor rendering, as far as I can see not css is referenced 2. A would prefer that I am able to hide the registration button Is either of this possible to be fixed in the future? Thank you and kind regards Torge

2 1

Cache mailman3
by pau.baiges＠csuc.cat 22 Dec '24

22 Dec '24

Is there a way to delete the mailman3 cache? It's because it gives us this error and we think it's because of the cache. Internal Server Error: /mailman3/accounts/login/ TemplateDoesNotExist at /accounts/login/ django_saml2_auth/error.html Request Method: GET Request URL: http://llistes.csuc.cat/mailman3/accounts/login/?next=/mailman3/postorius/l… Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: dv., 15 Març 2024 10:33:00 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Template loader postmortem Django tried loading these templates, in this order: Using engine django: This engine did not provide a list of tried templates. Traceback: File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 179. result = function(request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/views.py" in signin 271. saml_client = get_saml_client(get_assertion_url(request), acs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_saml_client 169. metadata = get_metadata(user_id) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_metadata 131. raise SAMLAuthError("Invalid metadata URL.", extra={ During handling of the above exception (Invalid metadata URL.), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 181. result = handle_exception(exc, request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in handle_exception 162. return render(request, File "/usr/lib/python3/dist-packages/django/shortcuts.py" in render 36. content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in render_to_string 61. template = get_template(template_name, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in get_template 19. raise TemplateDoesNotExist(template_name, chain=chain) Exception Type: TemplateDoesNotExist at /accounts/login/ Exception Value: django_saml2_auth/error.html Request information: USER: AnonymousUser

3 2

Error: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class
by Torge Riedel 22 Dec '24

22 Dec '24

Dears, I just upgraded my Server from Ubuntu 22.04 to 24.04 and I get the following error when accessing the web page. Django is 5.0.10 Postorius is 1.3.13 Any help is welcome. Thank you and kind regards Torge Internal Server Error:/mailman3/lists/ ImportError at/mailman3/lists/ Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Request Method: GET Request URL:https://lists.lsv-pinneberg.de/mailman3/lists/ Django Version: 5.0.10 Python Executable: /usr/bin/uwsgi-core Python Version: 3.12.3 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/opt/mailman/web/venv/lib/python3.12/site-packages'] Server time: Sun, 22 Dec 2024 11:05:00 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', 'allauth.account.middleware.AccountMiddleware') Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 30, in import_string return cached_import(module_path, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 16, in cached_import return getattr(module, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ The above exception (module 'django.contrib.sessions.serializers' has no attribute 'PickleSerializer') was the direct cause of the following exception: File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/deprecation.py", line 133, in __call__ response = self.process_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/middleware.py", line 20, in process_request request.session = self.SessionStore(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/db.py", line 16, in __init__ super().__init__(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/base.py", line 47, in __init__ self.serializer = import_string(settings.SESSION_SERIALIZER) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 32, in import_string raise ImportError( ^^^^^^^^^^ Exception Type: ImportError at/mailman3/lists/ Exception Value: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Raised during: postorius.views.list.list_index

1 1

Subscription requires confirmation when list is set as Open
by Mark 21 Dec '24

21 Dec '24

Hi All, I have a list set with the following ... List Settings > Member Policy # Subscription Policy = "Open" When I subscribe with an email address that has been used (subscribed/unsubscribed) on any other list (on that server), the address is subscribed automatically. However, if I subscribe with an address that has never been used before, I receive an email that requires me to confirm the subscription. The subscription is also held in the administrator's "Subscription requests: Pending confirmation". This happens when subscribing by both email and the web UI. Ideally, as the Policy is set as "Open", the subscription of any new email address should be added automatically. Have I missed a configuration setting somewhere? Any advice really appreciated. Regards, Mark $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Venv installation on Debian

3 7

Re: mail stuck in "out" queue
by Dmitry Makovey 18 Dec '24

18 Dec '24

So our mailman got stuck again, but I did follow your advise. Here's what I've found: On 3/29/19 2:58 PM, Mark Sapiro wrote: > On 3/29/19 2:28 PM, Dmitry Makovey wrote: >> I've had encountered this situation now twice: mail is being stuck in >> "out" queue and nothing in the logs indicates the issue. Is there a way >> to ask mailman-core politely to attempt delivery (perhaps with increased >> debugging in the logs) *without* restarting the core (which does solve >> *this* problem but creates other problems, like availability of the >> mailman as a whole) > > > Is the "out" runner running? yes: # docker top mailman-core | grep -F out: 100 21681 13215 0 Mar28 ? 01:14:16 /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg > ps -fwwA |grep runner=out > > If not, you should be able to start it as the Mailman user with a > command like > > /path/to/python3 /path/to/mailman/bin/runner -C /path/to/mailman.cfg > --runner=out:0:1 > > See 'ps -fwwA|grep runner' for examples > > If the out runner is running, is there a file named *.bak along with all > the *.pck files in queue/out/ there is one, yes: # ls -l /srv/mail/mailman/core/var/queue/out/*.bak -rw-rw---- 1 100 65533 21512 Apr 14 19:45 /srv/mail/mailman/core/var/queue/out/1555296331.8386078+2c905825b82708e5a682b872b0aff320c9dd0b2e.bak what does it indicate and what should my steps be to resolve this (other than restarting queues)? > And if it's not, is there anything in Mailman's logs to indicate why it > died? > > Also, 'mailman restart' should only take a matter of seconds, but if the > out runner is running but not processing its queue, I think sending it a > SIGINT should restart it. SIGINT killed the process allright, but it didn't auto-respawn. I ended up spawning it with: /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg but soon realized it doesn't go to background nicely so I've nohup'ed it in the end. but it did solve my problem. -- Sr System and DevOps Engineer SoM IRT

6 17

Upgrading other python packages than the mailman ones in a venv results in dependency conflicts
by Ulf R. 17 Dec '24

17 Dec '24

Hello, I know this should be the way to upgrade: https://docs.mailman3.org/en/latest/upgrade-guide.html I have 3.3.10 installed. I saw that some python packages are outdated an tried this which install all outdated packages in a row: pip list --outdated --format=json | jq '.[].name' | xargs -n1 pip install -U One outdated package was django and this part happened: ------------------------------- vDownloading Django-5.1.4-py3-none-any.whl (8.3 MB) Installing collected packages: Django Attempting uninstall: Django Found existing installation: Django 4.2.16 Uninstalling Django-4.2.16: Successfully uninstalled Django-4.2.16 ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. hyperkitty 1.3.12 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. mailman-web 0.0.9 requires django<4.3,>=4.0, but you have django 5.1.4 which is incompatible. postorius 1.3.13 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. django-mailman3 1.3.15 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. Successfully installed Django-5.1.4 ------------------------------- So I made a roll back. Is this really the only secure way to update the venv?: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web May be yes and I have to ignore the rest? ;-) Thank you und regards

4 3

Easy way to integrate captcha/reduce subscription spam?
by Johannes Rohr 16 Dec '24

16 Dec '24

Dear all, my mailman3 instance is flooded with subscription spam, yet I haven't found any canonical method of integrating a captcha in to the subscription form. Is there really none at all? Perplexity.ai says I should install the python package django-simple-captcha but is unclear about the steps needed to actually make the captcha appear. Are there other ways? Is there any method that is robust and survives upgrades? Also, would there be a way of batch-deleting all those thousands of spam registrations that have accumulated (what they have in common is that their email is unconfirmed) Thanks in advance for any suggestion! Johannes

1 0

MM2 to MM3 on different server. Process to move everything at once.
by jkoral＠luc.edu 12 Dec '24

12 Dec '24

Is there a way to move everything from an MM2 server to a new MM3 server (on separate servers)? I have been migrating individual lists, which seems to work OK, but there are so many lists that it would have to be done over a longer period of time. I was hoping I can just migrate a database or something and have it all done in an hour or so. Thoughts?

3 2

Blocking / throttling unwanted signup attempts
by David Newman 12 Dec '24

12 Dec '24

Greetings. On a server running Postfix and Mailman 3.3.9, the Postfix queue shows 20-30 entries/day like this mildly obfuscated example: 4Y8M1n5v5VzHSpQ 2023 Thu Dec 12 10:48:45 postmaster(a)example.com (host gmail-smtp-in.l.google.com[142.250.101.26] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, go to 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate 41be03b00d2f7-7fd409820c4si13081249a12.439 - gsmtp (in reply to RCPT TO command)) baduser2000(a)gmail.com From the Mailman logs it appears these are responses to signup attempts to a publicly advertised list hosted on this server. The signups come from many different Gmail addresses. I'm concerned about being part of a botnet. Other than taking the list private, is there some other means I can use to block/throttle these signup attempts? Thanks dn

1 0

hyperkitty threads by month list UI?
by Bryan Fields 11 Dec '24

11 Dec '24

Does anyone have a better way to display the threads by month in hyperkitty? I'm thinking like a selector that could show year and then you click on year and it gives months. As of now it expands the months out and there's over 300 lines to scroll down on for threads. Example: https://keekles.org/~bryan/longlisthyperkitty.png Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 0

Enable delivery
by Hirayama, Pat 10 Dec '24

10 Dec '24

Greetings, I'm finding something a bit odd with our listserv. Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If I select Enabled and Save, then delivery starts working for that user. There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: mailman members --nomail any listname@listserv Nothing is returned. If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. 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>

2 4

How to Increase outgoing mail volume for Mailman 3
by Brian Carpenter 09 Dec '24

09 Dec '24

Hello everyone, We had a new client come on board that brought a list that had the largest out-going mail volume that I have ever dealt with. So I did what any sane server administrator would do that is running Mailman 3: I ran to Mark Sapiro for help! Here is what the Sage of all things Mailman counseled me to do: 1. Disabled VERP delivery. VERP can help improve mail delivery by delivering 1 message per SMTP transaction (I think I got that right). Using VERP is counter-productive as it can seriously delay outgoing mail delivery for a high-volume list. So you can use something like the following in the MTA section of your mailman.cfg: [mta] verp_confirmations: no verp_personalized_deliveries: no verp_delivery_interval: 0 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. This action was the game changer. It allows Mailman to handle 4 incoming messages at a time instead of 1. My client's incoming list volume was high enough where it was overwhelming the single outgoing runner. Here is what I added to the mailman.cfg file: [runner.out] instances: 4 Doing this step immediately solved the backlog in var/queue/out. 3. If you start up with a new server for a list that is high volume then keep an eye out for Proofpoint and Vade Security as they will block your new IP address quicker than Mark Sapiro can say "This is a bug. See <some Gitlab.com url>" Mark, thank you! -- Brian Carpenter Harmonylists.com Emwd.com

5 10

Hyperkitty search on Message-ID?
by Bryan Fields 06 Dec '24

06 Dec '24

I've been working with a rather large import and am finding that I can't seem to get the search on a Message-ID: to return anything. I can do this via the DB, and then look at the message, but this is less than ideal, and requires DB access. > mailmanweb=> select message_id_hash from hyperkitty_email where message_id = '19991231211903.C2870(a)abq-mail-01.ihighway.net'; > message_id_hash > ---------------------------------- > IWKEJSPTJODEHARQ2VI6BEFQKNEJYM22 Any ideas how to get it indexing the ID so a layperson can search on it? -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

2 3

Aborted connection message in log in every 5 minutes
by zoltan＠circle-interactive.co.uk 03 Dec '24

03 Dec '24

Hi Everyone, we have mailman 3.3.8 venv test installation which in general works fine however our mysql error log is filled up with messages below because they are so frequent. 2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) As suggested here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I tried to correlate with error logs and /opt/mailman/web/logs/mailmanweb.log shows some hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)" /opt/mailman/web/logs/uwsgi-error.log Message: OperationalError(2013, "Lost connection to MySQL server at 'handshake: reading initial communication packet', sy stem error: 104") but they have not such frequency so unsure if they are related. Thanks for the suggestions

6 16

Recaptcha for subscription requests?
by Jered Floyd 03 Dec '24

03 Dec '24

Hello Mailman3 users, I've seen a massive uptick in bogus subscription requests with real addresses, either being used to DDoS outside mailboxes or just for intrusion/scanning. (It looks like a lot of fake random strings for name and then valid addresses like scanning/scamming tools like Acunetix generate.) When these hit thousands of gmail addresses they get classified as spam and hurt our overall deliverability. Has anyone yet built a CAPTCHA integration for the Subscription/Sign Up path? Regards, --Jered

3 2

Deleting moderation requests in database
by Joachim Schrod 03 Dec '24

03 Dec '24

OK; so I have an old mailman instance where I can't confirm unsubscribe moderation requests. mailman3 core is still sending me daily notices about that moderation requests; I want to get rid of them. (By now, I unsubscribed this test subscriber, so these messages are garbage anyhow.) First: I assume that all information about moderation is in the database mailman3. If that's not the case, please tell me. Second: I tried to determine what DB records are involved in a moderation, so I can delete them. I found the following records: -- workflowstate: records about pending confirmations; with a token as primary key. -- pended: records that references that key, with an id. -- pendedkeyvalue: records with additional information about the request, referenced by the id of table record `pended'. In addition, there is a record in table `member' for that mailing list, with an UUID in `_member_id' that isn't stored in any other record in the database elsewhere. (This is a test mailing list that currently has *no* members; thus this record might be relevant.) Where is this `_member_id' UUID used? My question is: Which records do I have to delete to get rid of the daily pending unsubscribe moderation notices? Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

2 2

Internal Server Error: /mailman3/accounts/fedora/login/
by Alain D D Williams 03 Dec '24

03 Dec '24

Twice today I have received many (50+) emails like the one below. Many at about 1pm, then it stopped now I am getting them again. An Internet search does not bring up anything useful. The domain at the start of 'Request URL' varies as does the name of the list (in this example 'announce(a)leavesden.org') The domain of the list is not necessarily the same as the domain at the start of the URL. I can receive several in a minute. Anyone any idea ? ----- Forwarded message from root(a)bf2024.phcomp.co.uk ----- Date: Mon, 02 Dec 2024 22:19:12 -0000 From: root(a)bf2024.phcomp.co.uk To: root@localhost Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/fedora/login/ Internal Server Error: /mailman3/accounts/fedora/login/ TypeError at /accounts/fedora/login/ OpenIDProvider.get_server_settings() missing 1 required positional argument: 'endpoint' Request Method: GET Request URL: https://www.leavesden.org.uk/mailman3/accounts/fedora/login/?next=%2Fmailma… Django Version: 3.2.19 Python Executable: /usr/bin/uwsgi-core Python Version: 3.11.2 Python Path: ['.', '', '/usr/lib/python311.zip', '/usr/lib/python3.11', '/usr/lib/python3.11/lib-dynload', '/usr/local/lib/python3.11/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.11/dist-packages'] Server time: Mon, 02 Dec 2024 22:19:07 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 56, in get return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 67, in post client = _openid_consumer( File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/openid/views.py", line 27, in _openid_consumer server_settings = provider.get_server_settings(endpoint) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: OpenIDProvider.get_server_settings() missing 1 required positional argument: 'endpoint' Request information: USER: AnonymousUser GET: next = '/mailman3/hyperkitty/list/announce(a)leavesden.org.uk/2020/12/' process = 'login' POST: No POST data FILES: No FILES data COOKIES: No cookie data META: CONTEXT_DOCUMENT_ROOT = '/var/www/leavesden/html' CONTEXT_PREFIX = '' DOCUMENT_ROOT = '/var/www/leavesden/html' GATEWAY_INTERFACE = 'CGI/1.1' HTTPS = 'on' HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' HTTP_ACCEPT_ENCODING = 'gzip' HTTP_ACCEPT_LANGUAGE = 'en-us,en-gb,en;q=0.7,*;q=0.3' HTTP_CONNECTION = 'Keep-Alive' HTTP_HOST = 'www.leavesden.org.uk' HTTP_USER_AGENT = 'serpstatbot/2.1 (advanced backlink tracking bot; https://serpstatbot.com/; abuse(a)serpstatbot.com)' PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' PATH_INFO = '/accounts/fedora/login/' QUERY_STRING = 'next=%2Fmailman3%2Fhyperkitty%2Flist%2Fannounce%40leavesden.org.uk%2F2020%2F12%2F&process=login' REMOTE_ADDR = '144.76.69.39' REMOTE_PORT = '33902' REQUEST_METHOD = 'GET' REQUEST_SCHEME = 'https' REQUEST_URI = '/mailman3/accounts/fedora/login/?next=%2Fmailman3%2Fhyperkitty%2Flist%2Fannounce%40leavesden.org.uk%2F2020%2F12%2F&process=login' SCRIPT_FILENAME = 'proxy:uwsgi://localhost//accounts/fedora/login/' SCRIPT_NAME = '/mailman3' SCRIPT_URI = 'https://www.leavesden.org.uk/mailman3/accounts/fedora/login/' SCRIPT_URL = '/mailman3/accounts/fedora/login/' SERVER_ADDR = '85.119.82.114' SERVER_ADMIN = 'addw(a)phcomp.co.uk' SERVER_NAME = 'www.leavesden.org.uk' SERVER_PORT = '443' SERVER_PROTOCOL = 'HTTP/1.1' SERVER_SIGNATURE = '********************' SERVER_SOFTWARE = 'Apache/2.4.62 (Debian)' SSL_TLS_SNI = 'www.leavesden.org.uk' uwsgi.core = 1 uwsgi.node = b'bf2024.phcomp.co.uk' uwsgi.version = b'2.0.21-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = <built-in function uwsgi_sendfile> wsgi.input = <uwsgi._Input object at 0x7f42defc8b50> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'root@localhost'),)" ALLOWED_HOSTS = ['*'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = '/usr/share/mailman3-web' CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f42e6122700> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = '()' COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/var/lib/mailman3/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_URL = '/mailman3/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': {'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4'}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'MIGRATE': True, 'MIRROR': None, 'NAME': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATA_UPLOAD_MAX_NUMBER_FILES = 100 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' DEFAULT_CHARSET = 'utf-8' DEFAULT_EXCEPTION_REPORTER = 'django.views.debug.ExceptionReporter' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'mailman3(a)bf2024.phcomp.co.uk' DEFAULT_HASHING_ALGORITHM = 'sha256' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAILNAME = 'bf2024.phcomp.co.uk' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = 420 FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/var/lib/mailman3/web/fulltext_index'}} HOSTNAME = 'localhost' IGNORABLE_404_URLS = [] INSTALLED_APPS = "('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora')" INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ar-dz', 'Algerian Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('ig', 'Igbo'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('ky', 'Kyrgyz'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('tg', 'Tajik'), ('th', 'Thai'), ('tk', 'Turkmen'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'ar-dz', 'fa', 'ur'] LANGUAGE_CODE = 'en-gb' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_HTTPONLY = False LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LANGUAGE_COOKIE_SAMESITE = None LANGUAGE_COOKIE_SECURE = False LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '/mailman3/' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' PREPEND_WWW = False Q_CLUSTER = {'timeout': 300, 'retry': 400, 'save_limit': 100, 'orm': 'default', 'poll': 5} ROOT_URLCONF = 'urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_REFERRER_POLICY = 'same-origin' SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)bf2024.phcomp.co.uk' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/var/lib/mailman3/web/static' STATIC_URL = '/mailman3/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = True USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'wsgi.application' X_FRAME_OPTIONS = 'DENY' YEAR_MONTH_FORMAT = 'F Y' ----- End forwarded message ----- -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 1

Problem with importing lists
by Alain D D Williams 01 Dec '24

01 Dec '24

This is a problem that I had before. Creating a new email list, adding members - all goes well the members can send email to the list and it is sent out. Create an email list and import configuration data from mailman 2.1.20 *sometimes* has problems - mail is received, archived but not sent out. This is only sometimes. One list that I had the problem with I eventually got it to send out email, but I cannot remember exactly what I did. The lists that get stuck go into an infinite look trying to deal with a file in /var/lib/mailman3/queue/shunt/ -- the files being worked on in /var/lib/mailman3/queue/out/ where they appear temporarily. # mailman --run-as-root import21 arm-netbook(a)lists.phcomp.co.uk /home/tmp/lists/arm-netbook/config.pck Importing members [####################################] 100% Importing owners [####################################] 100%addw(a)phcomp.co.uk is already imported with role MemberRole.owner Importing moderators [####################################] 100% Importing defers [####################################] 100% Importing holds [####################################] 100% Importing rejects [####################################] 100% Importing discards [####################################] 100% The archive with a message from me at 6.18pm can be seen here (with one at 5.28 from when it was on the old machine) https://mm-test.phcomp.co.uk/mailman3/hyperkitty/list/arm-netbook@lists.phc… The file in /var/lib/mailman3/queue/shunt/ has been decoded below with "mailman --run-as-root qfile" -- some 305 email addresses have been redacted for privacy: [----- start pickle -----] <----- start object 1 -----> Received: from freshmint.phcomp.co.uk ([2001:4d48:ad51:2f00::2:2] helo=mint.phcomp.co.uk) by bf2024.phcomp.co.uk with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <addw(a)phcomp.co.uk>) id 1tHoWI-006ljH-04 for arm-netbook(a)lists.phcomp.co.uk; Sun, 01 Dec 2024 18:18:10 +0000 Received: from addw by mint.phcomp.co.uk with local (Exim 4.96) (envelope-from <addw(a)phcomp.co.uk>) id 1tHoWC-00CAqy-27 for arm-netbook(a)lists.phcomp.co.uk; Sun, 01 Dec 2024 18:18:04 +0000 Date: Sun, 1 Dec 2024 18:18:04 +0000 From: Alain D D Williams <addw(a)phcomp.co.uk> To: Eco-Conscious Computing <arm-netbook(a)lists.phcomp.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: base64 Organization: Parliament Hill Computers Ltd X-Spam-Score: 0.0 (/) Message-ID: <Z0yoXLgAmLN2FkGg(a)phcomp.co.uk> Message-ID-Hash: XJ5VNDGSXYMG2XZRY2ATQUBWF555ERTT X-Message-ID-Hash: XJ5VNDGSXYMG2XZRY2ATQUBWF555ERTT X-MailFrom: addw(a)phcomp.co.uk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list Reply-To: Eco-Conscious Computing <arm-netbook(a)lists.phcomp.co.uk> Subject: [Arm-netbook] Potential trouble on this mail list - did this work ? List-Id: Eco-Conscious Computing <arm-netbook.lists.phcomp.co.uk> Archived-At: <https://lists.phcomp.co.uk/mailman3/hyperkitty/list/arm-netbook@lists.phcom…> List-Archive: <https://lists.phcomp.co.uk/mailman3/hyperkitty/list/arm-netbook@lists.phcom…> List-Help: <mailto:arm-netbook-request@lists.phcomp.co.uk?subject=help> List-Owner: <mailto:arm-netbook-owner@lists.phcomp.co.uk> List-Post: <mailto:arm-netbook@lists.phcomp.co.uk> List-Subscribe: <mailto:arm-netbook-join@lists.phcomp.co.uk> List-Unsubscribe: <mailto:arm-netbook-leave@lists.phcomp.co.uk> SSBoYXZlIG5vdyBtb3ZlZCBpdCBvdmVyLiBQb3RlbnRpYWwgaXNzdWVzOg0KDQrigKIgVGhlIG5l dyBJUCBhZGRyZXNzZXMgYXJlIDg1LjExOS44Mi4xMTQgMmEwYToxMTAwOjEwMTI6OjExNA0KICBZ b3UgbWlnaHQgc2VlIHRoZSBvbGQgb25lcyBmb3IgdGhlIG5leHQgwr0gaG91ci4NCg0K4oCiIFlv dSBtaWdodCBub3Qgc2VlIHRoaXMgZW1haWwgYXQgYWxsLg0KICBUaGlzIGlzIG9uZSBwcm9ibGVt IEkgaGF2ZSBoYWQgb24gY29udmVyc2lvbiAtLSBzb21ldGltZXMuDQoNClJlZ2FyZHMNCg0KLS0g DQpBbGFpbiBXaWxsaWFtcw0KTGludXgvR05VIENvbnN1bHRhbnQgLSBNYWlsIHN5c3RlbXMsIFdl YiBzaXRlcywgTmV0d29ya2luZywgUHJvZ3JhbW1lciwgSVQgTGVjdHVyZXIuDQorNDQgKDApIDc4 NyA2NjggMDI1NiAgaHR0cHM6Ly93d3cucGhjb21wLmNvLnVrLw0KUGFybGlhbWVudCBIaWxsIENv bXB1dGVycy4gUmVnaXN0cmF0aW9uIEluZm9ybWF0aW9uOiBodHRwczovL3d3dy5waGNvbXAuY28u dWsvQ29udGFjdC5odG1sDQojaW5jbHVkZSA8c3RkX2Rpc2NsYWltZXIuaD4NCg== <----- start object 2 -----> { '_parsemsg': False, 'envsender': 'noreply(a)lists.phcomp.co.uk', 'lang': 'en', 'listid': 'arm-netbook.lists.phcomp.co.uk', 'original_sender': 'addw(a)phcomp.co.uk', 'original_size': 1529, 'original_subject': 'Potential trouble on this mail list - did this work ?', 'received_time': datetime.datetime(2024, 12, 1, 18, 18, 10, 551642), 'recipients': { --- 305 lines removed here 'SOME-USER(a)gmail.com'}, 'rule_hits': [], 'rule_misses': [ 'dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation', 'nonmember-moderation', 'administrivia', 'implicit-dest', 'max-recipients', 'max-size', 'news-moderation', 'no-subject', 'digests', 'suspicious-header'], 'stripped_subject': 'Potential trouble on this mail list - did this work ?', 'to_list': True, 'verp': False, 'version': 3, 'whichq': 'out'} [----- end pickle -----] -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 2

Suggeested change to the venv installation instructions
by Bill Oliver 30 Nov '24

30 Nov '24

Well, I'm now on my third installation of mailman3. I ran into a problem I had forgotten about but once I figured it out, *then* I remembered running into it last time. Configuration: Ubuntu 24.04 ib a vos, It's this. I'm a mysql person, not a postgres person, but I installed postgres for this installation just so I could follow the instructions directly. Whenever I tried to start the mailman service, I got the error that mailman didn't have permission to do whatever needed to be done. The error was: psycopg2.errors.InsufficientPrivilege: permission denied for schema public After a little searching, I found out that mailman needs to be made the OWNER of the database, not just granted all privileges. After adding the commands: ALTER DATABASE mailman OWNER TO mailman; ALTER DATABASE mailmanweb OWNER TO mailman; I suggest adding those two lines to the instructions for "Setup Database" at https://docs.mailman3.org/en/latest/install/virtualenv.html billo

2 2

Moderated unsub requests are not provided by mailman3 service
by Joachim Schrod 30 Nov '24

30 Nov '24

Hello, I'm new to Mailman3; being in the process of moving some mailing lists from an ancient Mailman2 installation to a new host. (These lists are not big; they are used to organize a yearly holiday of roughly 50 persons.) As part of the migration; I'm testing out actions that were done on the previous Mailman2 instance. Currently, I stumble over confirmation of unsubscribe requests. Unsubscribe policy of the list is "Moderate". I subscribed an email address and used "Mass operations - Mass removal" in Postorius to unsubscribe it. (Actually, since it didn't work at first, I used that dialog twice.) Now I, as the mailing list owner, get a daily email vom Mailman3 that there are pending unsubscription requests that I shall approve. (Both unsubscription requests for the same email requests are listed in that email; doublettes are not handled properly.) The unsubscriptions requests are not shown in the web interface. I suppose they should appear in the UI section "Subscription requests", either as "Pending Approval" or "Pending Confirmation". (Frankly, I don't understand the difference between these two options at all.) Tracing the communication between Postorius and mailman3 service, I see that Postorius asks mailman3 about pending unsubscriptions with the following requests: 1) GET /3.1/lists/MBOX@DOMAIN This returns list information. 2) GET /3.1/lists/MBOX@DOMAIN/requests?token_owner=moderator This returns a JSON structure with properties "start" 0 and "total_size" 0. 3) GET /3.1/lists/MBOX@DOMAIN/requests/count?token_owner=moderator This returns a JSON structure with count 0. 4) GET /3.1/lists/MBOX@DOMAIN/held/count This also returns a JSON structure with count 0. When one wants to see the "Subscriptions pending user confirmation", there is also a GET to get the requests of token_owner=subscriber; returning the same result as the request for token_owner=moderator above. Looking at the mailman3 database, there are 2 records in table `workflowstate' that are in step `unsubscribe_from_restore' who describe the open unsubscribe requests. I could not identify any other database records that are obviously relevant to that issue. (Since this is a fresh test setup, the database is small enough that I can still look at any record in the database.) Why does Mailman3 have no info in its JSON responses about the unsubscription requests that I get informed about daily? Any hints where I could look further are dearly accepted. System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; both on Debian 11 (bullseye). I know that this is out of date; thus a definitive info "this is fixed by now" is quite OK for me. (Debian upgrade is planned as the next action after getting Mailman3 to work for that use case.) Hope that someone can guide me towards a solution, Joachim PS: The list configuration that I actually want is something completely different: mass unsubscription by the mailing list owner without moderation; but moderation for individual unsubscription requests. This is a mailing list where every year all subscribers are setup anew. Subscribers are email-illiterate users who may know WhatsApp at best, which brings its own problems. No person (un)subscribes herself or himself; all is done by the list owner. Unsubscription would mean cancelling the holiday participation -- the list owner must then ask if that's really wanted... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

3 3

Member name management by list owner
by mark＠suburbia.org.au 30 Nov '24

30 Nov '24

Bottom line up front: site admins can do some of the things below via https://example.com/mailman3/postorius/users thanks to https://gitlab.com/mailman/postorius/-/issues/403 - I am going to include my original post, in case it helps for visibility should others come up against this in future: -- Continuing in my initiation in the MM2.1 -> MM3 migration. I will say that while the software overall seems good, and the support in here has been excellent. I don't recall a more frustrating experience migrating a service in a long time. One of my list moderators runs a closed list for their non-profit organisation, whose demographic is on the more 'wise' side of life. As such, the organisation's committee pretty much handles all the list management for members, who receive a distribution list newsletter. They don't promote the ability to subscribe/unsubscribe/manage list settings to their membership as for some, replying to emails can seem complicated. It's been seen, (and based on the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… appears to be expected) that once an email address is first associated with mailman3, that whatever that member's name is sticks, including if the name wasn't initially used. And, that if you want to change it, you need to have the member login to/created an account at https://example.com/mailman3/user-profile/. E.g. if I as list owner/admin: 1) Add via mass subscription a new member whose email has never been seen by Mailman3 before `Wrong Name <specificemail(a)example.com>` 2) Search members and see it listed as `"Wrong Name" <email(a)example.com>` 3) Unsubscribe the member from the list 4) Add via mass subscription a same member with a new name `Correct Name <specificemail(a)example.com>` When I look at the members list it still shows `"Wrong Name" <email(a)example.com>` If I'm mistaken about any of the above or that does seem like a bug, feel free to let me know. Otherwise, is there any way, without expecting the members themselves to do it, for a site admin or list admin to change the name associated with an email address? I guess in order of preference, I'd like 1) list owner/admin to be able to modify list member name through web UI 2) site owner/admin to be able to modify list member name through web UI 3) list or site admin to be able to modify list member name through command line 4) direct editing of the mariaDB database. (And if this is the best option for now, if you can tell me the name of the db/table to look at it would be appreciated) -- Back to post BLUF solution - I guess my next ask, since the site admin can modify any user's name - would it be possible for me to grant a list owner/admin the ability to change names of any user without giving them full site admin access, and perhaps add the `Manage` button to the list's members list for them?

1 0

Internal Server Error: /archives/
by Christian 29 Nov '24

29 Nov '24

What is this error and how can I fix it please? Running Debian 4.19.316-1 -----Original Message----- From: noreply(a)lists.domedoman.ie <noreply(a)lists.domedoman.ie> Sent: Friday, November 29, 2024 5:08 AM To: csa(a)web-analysts.net Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/ Internal Server Error: /archives/ Report at /archives/ Internal Server Error: /archives/ Request Method: GET Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! Django Version: 3.2.15 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.7.3 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/opt/mailman/mm/venv/lib/python3.7/site-packages'] Server time: Fri, 29 Nov 2024 05:07:58 -0800 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): None Request information: USER: AnonymousUser GET: sort = 'active"\'!' POST: No POST data FILES: No FILES data COOKIES: No cookie data META: HTTP_ACCEPT_ENCODING = 'gzip,deflate' HTTP_CONNECTION = 'close' HTTP_HOST = '127.0.0.1:8000' HTTP_USER_AGENT = 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)' HTTP_X_FORWARDED_FOR = '52.204.37.237' HTTP_X_FORWARDED_HOST = 'lists.domedoman.ie' HTTP_X_FORWARDED_PROTO = 'https' HTTP_X_FORWARDED_SERVER = 'lists.domedoman.ie' PATH_INFO = '/archives/' QUERY_STRING = 'sort=active%22%27!' RAW_URI = '/archives/?sort=active%22%27!' REMOTE_ADDR = '127.0.0.1' REMOTE_PORT = '38786' REQUEST_METHOD = 'GET' SCRIPT_NAME = '' SERVER_NAME = '127.0.0.1' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' SERVER_SOFTWARE = 'gunicorn/20.0.4' gunicorn.socket = <socket.socket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 8000), raddr=('127.0.0.1', 38786)> wsgi.errors = <gunicorn.http.wsgi.WSGIErrorsWrapper object at 0x7fe24109e6d8> wsgi.file_wrapper = <class 'gunicorn.http.wsgi.FileWrapper'> wsgi.input = <gunicorn.http.body.Body object at 0x7fe240d83080> wsgi.input_terminated = True wsgi.multiprocess = True wsgi.multithread = False wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Admin', 'csa(a)web-analysts.net'),)" ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'lists.domedoman.ie', '192.46.218.224', 'zarathustra.domedoman.ie', '192.168.0.1'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = '/opt/mailman/mm' BROWSERID_AUDIENCES = ['http://localhost', 'http://localhost:8000', 'http://127.0.0.1:8000', 'http://lists.domedoman.ie', 'https://localhost', 'https://localhost:8000', 'https://127.0.0.1:8000', 'https://lists.domedoman.ie'] CACHES = {'default': {'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION': '127.0.0.1:11211'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'js': ['compressor.filters.jsmin.JSMinFilter'], 'css': ['compressor.filters.css_default.CssAbsoluteFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7fe24756d620> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'))" COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/opt/mailman/mm/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_URL = '/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': '127.0.0.1', 'PORT': '', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'MIGRATE': True, 'MIRROR': None, 'NAME': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' DEFAULT_CHARSET = 'utf-8' DEFAULT_EXCEPTION_REPORTER = 'django.views.debug.ExceptionReporter' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'noreply(a)lists.domedoman.ie' DEFAULT_HASHING_ALGORITHM = 'sha256' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_CONFIRMATION_FROM = 'postmaster(a)lists.domedoman.ie' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = 420 FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/opt/mailman/mm/fulltext_index'}} HYPERKITTY_DISABLE_SINGLETON_TASKS = True IGNORABLE_404_URLS = [] INSTALLED_APPS = "('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount')" INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ar-dz', 'Algerian Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('ig', 'Igbo'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('ky', 'Kyrgyz'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('tg', 'Tajik'), ('th', 'Thai'), ('tk', 'Turkmen'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'ar-dz', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_HTTPONLY = False LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LANGUAGE_COOKIE_SAMESITE = None LANGUAGE_COOKIE_SECURE = False LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.WatchedFileHandler', 'filename': '/opt/mailman/mm/logs/mailmansuite.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers': ['console', 'file'], 'level': 'INFO'}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1', '::ffff:127.0.0.1', '192.46.218.224')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '/' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.domedoman.ie' PREPEND_WWW = False Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default'} ROOT_URLCONF = 'urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = "('HTTP_X_FORWARDED_PROTO', 'https')" SECURE_REDIRECT_EXEMPT = [] SECURE_REFERRER_POLICY = 'same-origin' SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'noreply(a)lists.domedoman.ie' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 3 SOCIALACCOUNT_PROVIDERS = {'google': {'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}}, 'gitlab': {'SCOPE': ['read_user']}} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/opt/mailman/mm/static' STATIC_URL = '/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'America/Los_Angeles' USE_I18N = True USE_L10N = True USE_SSL = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = True USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'wsgi.application' X_FRAME_OPTIONS = 'DENY' YEAR_MONTH_FORMAT = 'F Y'

2 2

Suggested enhancement
by Alain D D Williams 29 Nov '24

29 Nov '24

The command: mailman members Shows who are member of a mail list - useful. It would be good if there was an option to show the mail list attributes for each user, eg: Delivery Status, Delivery Mode, Receive own postings, ... User type (member, moderator, etc) Have this printed one line/user with attributes on the line. A --json format option would be great. mailman addmembers being able to take the json format as input would be great. I have been playing with the REST interface but that is prolly to hard/complex for simple use. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 0

New domain cannot set set host
by Alain D D Williams 29 Nov '24

29 Nov '24

I have created a new domain - via postorius I want to set the 'Web Host' to be the same as the new domain but I cannot see that domain in the drop down list. Even if I save it and then edit the domain I still cannot see it. I went into mailman3-web/settings.py and added it to ALLOWED_HOSTS - no joy. I can see the domain in table mailman3.domain and mailman3web.django_mailman3_maildomain But it is not in table mailman3web.django_site Please how do I do this ? Thanks -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 5

Connection lost during _handle_client()
by Alain D D Williams 28 Nov '24

28 Nov '24

I thought that I was there ... it worked on my test machine but not on a live machine :-( Sending an email to the list just disappears after it is given to mailman. Debian with exim4 Exim looks OK, /var/log/exim4/mainlog says: 2024-11-28 00:59:45 1tGSsi-005OW3-1o <= addw(a)phcomp.co.uk H=freshmint.phcomp.co.uk (mint.phcomp.co.uk) [2001:4d48:ad51:2f00::2:2] P=esmtps X=TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=no S=1187 id=Z0fAe9xODd2y33N8(a)phcomp.co.uk 2024-11-28 00:59:45 1tGSsi-005OW3-1o => chat(a)bray.phcomp.co.uk R=mailman3_router T=mailman3_transport H=localhost [127.0.0.1] C="250 Ok" 2024-11-28 00:59:45 1tGSsi-005OW3-1o Completed /var/log/mailman3/smtp.log Nov 28 00:59:45 2024 (1268378) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 28 00:59:45 2024 (1268378) Peer: ('127.0.0.1', 42128) Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) handling connection Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) >> b'LHLO bf2024.phcomp.co.uk' Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) >> b'MAIL FROM:<addw(a)phcomp.co.uk> SIZE=2241' Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) sender: addw(a)phcomp.co.uk Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) >> b'RCPT TO:<chat(a)bray.phcomp.co.uk>' Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) recip: chat(a)bray.phcomp.co.uk Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) >> b'DATA' Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) >> b'QUIT' Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() I am concerned about the connection lost message above. Mailman sees it, the message ID matches that at the end of the first line in the exim log (above): /var/log/mailman3/mailman.log Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> Is there any more logging that I can look-at/switch-on to see what is happening ? Thanks -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 3

Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server
by peterrflores＠hotmail.com 28 Nov '24

28 Nov '24

Hello Everyone, I’m currently working on setting up Mailman3 on a server to manage several different mailing lists for a project. I’ve successfully installed Mailman3 and Postorius, and I can create and manage individual mailing lists through the Postorius web interface. However, I’ve encountered a couple of challenges that I need assistance with: Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. I checked this: https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ https://www.igmguru.com/machine-learning-ai/generative-ai-training https://lists.mailman3.org/mailman3/lists/test2.mailman3.org/ Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. I’d greatly appreciate any insights or advice the community can offer. Thanks in advance for your time!

2 1

Notifying owners of membership changes but not moderators
by Perry Kollmorgen 27 Nov '24

27 Nov '24

Hi, It looks like this list setting under Automatic Responses is the primary control for if email notifications regarding membership changes are sent or not: Notify admin of membership changes: Yes/No Should administrator get notices of subscribes and unsubscribes? Which is this setting name: "admin_notify_mchanges" I have a fair number of moderators however who don't want these notifications and only a single owner who appreciates the notifications on membership changes. Is there any way to have these only for Owners ? Cheers, Perry

2 4

Migrating users from MM2 to MM3 on a new server?
by jkoral＠luc.edu 25 Nov '24

25 Nov '24

Is there a way to copy users from the old MM2 server to a new MM3 server? Also, will it copy their password as well?

2 1

Unexpexted error: if you are sure you want to run as root, specify --run-as-root"
by w.schoener＠alp.dillingen.de 25 Nov '24

25 Nov '24

I want to execute some commands in mailman shell. I log in terminal as super user. But when I use the command mailman shell -l my.list.id i get the responce: "error: if you are sure you want to run as root, specify --run-as-root" I tried: mailman shell -l --run-as-root my.list.id but this does not help. Thank you for all hints. Wolfgang

3 3

Moving existing lists to a new domain
by Jeremy Stanley 21 Nov '24

21 Nov '24

I've moved lists and archives between domains in Mailman 2.1 and Pipermail, but not yet with Mailman 3 and Hyperkitty. I have a working multi-domain deployment, and one of the organizations using it is working on changing their domain name. Forwarding incoming messages at the MTA and setting up redirects on the Web server are simple enough, but internally within MM3/Django reside the bits I'm less certain about. Since all the lists for the given domain will be moving to the same unused new domain on the existing server, and can move at the same time, I suppose this could be done through (offline if necessary) backend database update queries. Is there anything outside the DB which would need updating or regenerating for this too? Is this how others have tackled similar tasks in the past, or is it recommended to export/import lists one at a time out of one domain and into another? Any tips are greatly appreciated! -- Jeremy Stanley

2 6

Hyperkitty configuration
by Alain D D Williams 21 Nov '24

21 Nov '24

Well, I have finally got it to archive something. One simple thing that tripped me up was the ARCHIVER_KEY • mailman-hyperkitty.cfg says: # The shared api_key, must be identical except for quoting to the value of # MAILMAN_ARCHIVER_KEY in HyperKitty's settings. api_key: SecretArchiverAPIKey Which is confusing as it is referring to "# Mailman API credentials" in the file mailman-web.py • mailman-web.py says: MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' It would be good if the lines in mailman-web.py were: # The value below is the same as api_key in mailman-hyperkitty.cfg except that the value here has quotes round it MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' And the lines in mailman-hyperkitty.cfg were: # The shared api_key, must be identical except for quoting to the value of # MAILMAN_ARCHIVER_KEY in HyperKitty's settings (mailman-web.py) # The value here does not have quotes api_key: SecretArchiverAPIKey And if you want to be really nice check if the api_key value is enclosed in quotes and generate a message if so. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 1

Must issue a STARTTLS command first when forwarding from old server to new server
by jkoral＠luc.edu 20 Nov '24

20 Nov '24

I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS?

2 3

Problems configuring hyperkitty
by Alain D D Williams 20 Nov '24

20 Nov '24

I am having another go at installing mailman3 - I seem to have mailman3 & postorius working - although basic testing, much more needed to confirm that I understand it. I want to get hyperkitty working before I start full testing. I am running Debian 12 - Bookworm and have installed the Debian packages. The database is Mysql. This is not a virtualenv setup. There is no documentation in the hyperkitty package so I am following: https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html I read the following: "The database can be created with the following command: django-admin migrate --pythonpath example_project --settings settings " I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty. • What database & tables will that be ? It would be really useful to be told so that I can check. • The config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ? • I have several different maildomains each with several lists. Some lists in different domains have the same name. Do I need a different example_project/settings.py for each domain, if so what changes ? One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ? django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] Is there some better documentation that I have failed to find ? Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

3 2

MM2.1 -> MM3.3 migration. To hold or not hold
by mark＠suburbia.org.au 19 Nov '24

19 Nov '24

Hi, I've spent the past week slowly migrating from MM2.1 to MM3.3. One of the lists migrated was set to hold all user posts for moderation, as the list isn't a discussion list but a newsletter sent out on occasion to user/members. I am seeing unexpected behaviour post-migration. The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a non-member posts to the list" -- it says `Hold for moderation` The migrated members when viewed all have a Moderation Action of `Hold for moderation`, which is also expected. When I add new members through Mass operations -> Mass subscribe, the new members have a Moderation Action of `None`. I've looked through the archives of this list, and from what I can tell: According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > None does not mean no moderation. None means use the list default > as opposed to one of the specific actions defined The thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… seems to also repeat the above, that `none` means the configured setting for the list. However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is `None`, but when I posted to the list from the address, it was not held for moderation, and went through. Am I missing something with the expected functionality? If it helps; Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] Postorius Version 1.3.8 Cheers, Mark

3 11

Template for Password Reset Email
by Mark 18 Nov '24

18 Nov '24

Hi, I have a list and user account set with French as the preferred language. Most message emails (such as the Welcome email) all arrive in French, but not the Password Reset email (shown below) - it arrives in English. I'm guessing that there may not be an .mo file for it. I don't see a template for the Password Reset email in the list's administration settings. Is it possible to create a template for it? Something like "list:user:action:reset"? My thinking is, if creating a template is possible, to (a) write it in French for this list; and (b) rewrite it differently as it's confusing some users. Regards, Mark ----------------------------------------------------------------------- Subject: [lists.domain.com] Password Reset Email ----------------------------------------------------------------------- Hello from lists.domain.com! You are receiving this email because you or someone else has requested a password for your user account. However, we do not have any record of a user with email imark(a)myemail.com in our database. This mail can be safely ignored if you did not request a password reset. If it was you, you can sign up for an account using the link below. https://lists.domain.com/accounts/signup/ Thank you for using lists.domain.com! lists.domain.com

2 6

Removing a moderator via the REST API
by Andy Matthews 15 Nov '24

15 Nov '24

You can currently add moderators to a mailing list via the REST API by posting to the `members` endpoint with `role` set to `moderator`. However it doesn't appear that you can remove a person as moderator via the API, per a comment made by Mark on 8/12/24 in this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… We've already got scripts we use to manage moderators on lists, but we're trying to convert everything over to use the API. Does anyone have an idea of when this functionality will make it into the API? Thank you.

2 3

Migrating from old V2 server to new V3 server. Questions.
by jkoral＠luc.edu 14 Nov '24

14 Nov '24

We have figured out how to migrate from one server to another, but after removing the list from the old server, the e-mails are still trying to go there. Is there something that needs to be done in mailman so that the e-mail list will hit the new server instead? Does it just take time? Thank you, Joe Koral

2 26

Show list history
by pau.baiges＠csuc.cat 14 Nov '24

14 Nov '24

Hi, is there a way to know the history of a specific list, such as the changes that have been made over time? We want to see the history of members who have been added or removed. I can only see the mailman logs from the last 5-6 days Thank you

2 1

Installation Questions [Installation}
by Arte Chambers 14 Nov '24

14 Nov '24

Hello everyone, I'm running Ubuntu 24.10 and following the Virtualenv instructions <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u…>. When creating the mailman user per the instructions I find that the mailman user doesn't have sufficient permissions to do things later in the installation such as creating files in /etc. What steps should I take to ensure that the mailman user has the correct permissions to install the Mailman app. Thank you, Arte Chambers

5 11

Problems getting started with postorius
by Alain D D Williams 14 Nov '24

14 Nov '24

I am having another go with mailman3, being a long time MM2 user, but am getting increasingly frustrated. I am using on Debian 12 (Bookworm) and have installed the various Debian packages - mailman3-full does that. I have successfully started the mailman3 and mailman3-web services. I went to: http://localhost/mailman3/postorius/domains/new/ 'Add a new domain' I enter a 'Mail Host' -- a domain that does exist on this machine I choose a Web host from the drop down list -- same as Mail Host I click on 'Create Domain' and the page refreshes with the same information but under the Mail Host I see in red: {"title": "500 Internal Server Error"} I eventually tracked it down. The problem was that I had signed in with an account "addw@localhost". That, for some reason, failed validation above. I hacked the database and changed to "addw(a)localhost.localdomain" and creating the new domain worked. I could send email to addw@localhost - so at the MTA level it is correct. So please can the initial account creation do the same validation as does adding a new domain. I have looked but cannot find any documentation on postorius than https://docs.mailman3.org/projects/postorius/en/latest/ which is not helpful for a user or system admin. Can you point me to something better. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 1

Postorius List members
by Alain D D Williams 14 Nov '24

14 Nov '24

I have a test list with a few members. For each member it is showing me: Address, Delivery mode, Moderation action, bounce score. It is NOT showing Delivery status (Enabled, Disabled, Disabled by owner, ...). The only way of seeing this is by clicking on the email address (Subscription options). Is it possible to add delivery status to the summary where many users are shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of what is happening to users. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 2

No e-mail distribution after import of archive
by Markus Grandpré 13 Nov '24

13 Nov '24

Dear Mr. Sapiro, on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list. Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months. With kind regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

3 7

Changes in Django admin interface are not syncing to postorius gui /database
by ulf.rapphahn＠offis.de 12 Nov '24

12 Nov '24

Hello, I have the lasted version of mailman3 in an fresh venv installation and I am testing it for our upcoming migration from v2.1. When I add a new list in the django admin interface this list will never appear in postorius (vice versa it works). The new list is also not in both databases: SELECT * FROM mailman.mailinglist; SELECT * FROM mailmanweb.hyperkitty_mailinglist; (Why two databases are needed with redundant data?) The same when changing for example the description of an existing list in the django admin interface it doesn't change the description of the list in postorius. Vice versa it works. Changes made in postorius are also seen in django. Could please someone help me or explain this behavior? I hope it is a problem with my configuration. Thank you and regards, Ulf

4 7

Maximum recipients in an email.
by b.dirk＠gmx.de 12 Nov '24

12 Nov '24

Hello, where can I configure the maximum recipients in an email in mailman3? In my postfix configuration is set a limit "smtpd_recipient_limit = 200" and in the mailman3 smtp.log i will get a error message like "failed with code 452, b'4.5.3 Error: too many recipients'". Mailman3 repeats the delivery for these addresses, but i would like to configure correctly. The delivery of mails is then faster. Thanks. Best regards, Dirk

2 1

Add member to a list by email
by b.dirk＠gmx.de 12 Nov '24

12 Nov '24

Hello, I'm trying to add members by email with the following content. Recipient: testlist-request(a)xxxxxxxx.de Email content: join address=max.mustermann(a)xxxxxxxx.de After I've sent this email, it still has to be confirmed in the Postorius web interface under member requests. How can I confirm membership by email, or deactivate this confirmation for moderators? Thanks. Best regards, Dirk

2 1

Bulk delivery status change?
by Stephen Daniel 11 Nov '24

11 Nov '24

Mistakes were made, and for while every single outbound email bounced. I've fixed the mistakes, but now in my largest and most active email list, every single user's delivery status is "Disabled by Bounces". Is there a way to bulk fix this? Or do I have to go into each user, one at a time, and fix them? Thanks! -- Steve

3 7

Postorius not HTML-decoding < to "<" characters
by Ron / BCLUG 10 Nov '24

10 Nov '24

Andy Smith wrote on 2024-10-30 20:59: > # Block access to the signup form from Tor exit nodes. > <Location /mailman/accounts/signup> > <RequireAll> > Require all granted > Include /etc/apache2/tor-exit-list.conf > </RequireAll> > </Location> If we look at the above message, there are less-than and greater-than symbols around the Apache keywords in the email as expected. If we look at the archived version of the message, we see a slightly mangled representation: # Block access to the signup form from Tor exit nodes. <Location /mailman/accounts/signup> <RequireAll> Require all granted Include /etc/apache2/tor-exit-list.conf </RequireAll> </Location> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Hopefully I've assigned the blame to Postorius accurately and no formatting nor archiving issues make the issue difficult to understand. Thanks.

3 5

Create an eml command in a plugin
by antoine.depoisier＠ikmail.com 09 Nov '24

09 Nov '24

I try to create an EML command to allow moderators to accept a subscription request made by an address. I created this command in CLI first, to test if it works, and it works well except to send the welcome message. After that, I tried to create the EML command in my plugin, and when I'm testing this command, nothing happens. Also, when using the command EML help, my command is not shown on the email sent. Maybe I missed something to add in the configurations files. Should I add some configuration files for this command ? Here are the working tree command_eml_addmember_mailman_plugin __init__.py commands __init__.py eml_accept.py cli_test_accept.py

2 1

Postorius admin/user guide
by Florin Pasăre 08 Nov '24

08 Nov '24

Hello, We're trying to update mailman to version 3 from version 2, and I can't seem to find some non-technical guide for Postorius, something like an owners manual for all the configurations available in Postorius. Is there such a thing? Thank you, Florin

3 2

Members (and moderators) can't view the list of members.
by mrl＠psfc.mit.edu 07 Nov '24

07 Nov '24

I installed Mailman 3 almost 2 years ago. I only now noticed that members of a mailing list can't view the list of members. Even moderators can't see the list. Only Owners. The error message is "You do not have permissions to visit this page." Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] Postorius Version 1.3.8 Any ideas? I did make a few "minor" changes to the code, but hopefully it didn't cause this problem. What file(s) contains the code that checks for permissions? Or maybe there is a config file? I also notice by default, for all users, in their "Global Mailman Preferences", the default setting for "Hide Address" is "Yes". How can I change that to be "No". And can I reset that setting for all my present users? Thanks. - Mark

2 1

How to keep virtualenv install secure?
by Lichtinger, Bernhard 07 Nov '24

07 Nov '24

Hi, I am looking for some advice: If we use the virtualenv install method, how does one keep track of security updates for all the installed dependencies? I can think of: - Upgrade regularly all installed packages inside the virtualenv. This might break mailman3 if there are incompatible updates. - Try to track all dependencies and check if there are security updates published. This might be impossible to achieve. - Security updates are so rare, we do not need to bother. ;) Thanks, Bernhard

3 2

Abusive user creation - ideas for mitigating
by Andy Smith 07 Nov '24

07 Nov '24

Hi, My mailman3.auth_users table contains 131 rows, of which 113 of them were created in the last week. All of these users have a 10 character long random string of lowercase letters as their chosen username. Their email addresses are all over the place. I only noticed this was happening because an unusual number of the subscription confirmation messages were bouncing back to me as postmaster, and I saw the unlikely user names. I matched up some of the date_joined timings with logs of HTTP POST to /mailman/accounts/signup and every single one so far was a unique IP address. So I am not going to get very far with firewalling. Does anyone have any suggestions what I can do to avoid this? Specifically what I would like to avoid is sending a confirmation email to these potentially innocent addresses. … Hmm, actually I've just noticed that all of them are Tor exit nodes. Looks like I could probably autogenerate an Apache ACL that lists all Tor exit nodes and bans them from posting to /mailman/accounts/signup. Thanks, Andy

2 3

Backup and restore a single list
by sherin＠raidm.com 06 Nov '24

06 Nov '24

Hello, I am new to mailman3 . I am looking for the procedure to backup and restore a single mailing list from mailman3. If any one know the procedure or the documentation , please point me

3 7

Where to find disabled members?
by Bill Oliver 05 Nov '24

05 Nov '24

Now that I have mailman running smoothly, I'm having to deal with a few other issues. When I changed vendors for my vps, my vendor gave me a static IP address that was apparently run by Satan himself. The ip address is -- or was -- on a number of blacklists. I have spent the past couple of weeks going through various appeals processes to get whitelisted, and I think I'm in good shape. In the meantime, a fair number of subscribers have been disabled. When I look at Postorius -> Settings -> Bounce processing, I see all of the policies I can play with, but I don't see how to a) See who is disabled, and b) un-disable them by hand or... do I just have to wait seven days for them to automatically get un-disabled? Thanks! billo

2 2

member appears twice in list - how?
by Jose Bernal 05 Nov '24

05 Nov '24

I've got a list member showing up twice in a list (same email address). Can't use the GUI to remove the member from this list (get a 503 error) Screenshots attached, underlying database query reveals no duplicates. Wondering how this is possible or where else I should be looking to resolve this duplicate before I simply remove their entry from the members table altogether. Thank you, --------------------- José Bernal Web/Application Engineer Cell 541-228-8481 jbernal.web.dev(a)gmail.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screen Shot 2024-11-05 at 10.53.55 AM.png Content-Type: image/png Name: Screen Shot 2024-11-05 at 10.59.12 AM.png Replaced multipart/alternative part with first alternative.

2 1

"held for moderation" - alias domain details sought
by Greg Newby 05 Nov '24

05 Nov '24

Hi friends. I've viewed this old thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… (and the Postfix docs it links to). Those documents don't seem to guide my situation, or maybe I just need a more specific example. The problem is that when messages are delivered to the alias domain, they are held for moderation. I.e., mail to the alias domain like testlist(a)domain.tld is held for moderation, but mail from the same subscribed, non-moderated user to testlist(a)lists.domain.tld is posted immediately without moderation. I wonder whether my main domain needs to be @domain.tld and my alias domain needs to be @lists.domain.tld - is that what I should try? Or, am I not setting up the alias domain correctly? Details: I'm writing to ask for advice so that mailman messages to address(a)domain.tld can also be sent to address(a)lists.domain.tld. There are various other non-Mailman addresses (local Unix accounts and aliases) handled by @domain.tld as well as @otherdomain.tld on the same server. I have a running 3.3.10 server (venv, using Postfix and PostgreSQL under Ubuntu 24.04LTS). The configured domain is of the form: lists.domain.tld and it's working ok. I put this in /etc/aliases and it seems to work, to forward messages from testlist(a)domain.tld to testlist(a)lists.domain.tld: testlist: testlist(a)lists.domain.tld I know it works because I see it in MM3's smtp.log and mailman.log, including a line like this in mailman.log: Oct 12 21:12:27 2024 (2560960) HOLD: testlist(a)lists.domain.tld post from gbnewby(a)petascale.org held, message-id=< CANLuyJZd8NNn5rOLe3XUhooG9F33U_7VOQXrS-7Z241koAV_Ww(a)mail.otherdomain.com>: Message has implicit destination And, indeed, the message is held for moderation. In the MM3 configuration panel for Domains ( https://lists.domain.tld/mailman3/domains/), I have put "domain.tld" in the "Alias domain" field. Thanks for any guidance. I appreciated seeing the recent threat about "redirecting -bounces replies" which also addresses alias domains. ~ Greg

3 4

HSTS Missing from HTTPS Server
by jkoral＠luc.edu 05 Nov '24

05 Nov '24

In my configuration, I am using Apache to reverse proxy the requests to a uwsgi. After our security office scanned the server, it was shown that HSTS is missing from the HTTPS server. The instructions say to add some lines to /etc/apache2/sites-enabled/. The only file in there is 000-default.conf that holds the configuration, but the VirtualHost is port 80. I am using an F5 to to automatically redirect port 80 to port 443, but it is still showing this vulnerability. My question is, how can enable the Virtual Host for 443 on the server? Or can that configuration be located somewhere else? Or can I just create a new Virtual Host with the added configuration for mailman? Thanks, Joe Koral

2 1

The dread "relay access denied" error
by Bill Oliver 05 Nov '24

05 Nov '24

I've been trying to avoid asking this question since "relay access denied" problems are usually pretty silly configuration errors that I should pick up. But I've been staring at this for three days and I'm stumped. Once again here's the scenario. I set up mailman3 on Ubuntu 24.04 and it's running without a hitch, particularly now that I added the appropriate archival commands. I decided to create a backup on an older server of mine running Ubuntu 22.04. The setup is almost identical except for domain names. Unfortunately, in the second setup, I'm getting "relay access denied" to senders/recipients outside the host domain. Things go fine to list members on the local machine. Mailman is successfully sending admin mail to mailman(a)bill-oliver.com Mail not using mailman works fine. The domain where everything works is billoblog.com. The domain I'm setting up is bill-oliver.com Here's the error in syslog (mirrored in mail.log) on bill-oliver.com trying to talk to list members oliver(a)billoblog.com and billo(a)billoblog.com:: Nov 1 21:24:52 mail postfix/smtpd[10193]: NOQUEUE: reject: RCPT from 162-144-108-19.bluehost.com[162.144.108.19]: 454 4.7.1 <oliver(a)billoblog.com>: Relay access denied; from=<tradfp-bounces+oliver=billoblog.com(a)bill-oliver.com> to=<oliver(a)billoblog.com> proto=ESMTP helo=<162-144-108- 19.bluehost.com> Nov 1 21:24:52 mail postfix/smtpd[10193]: disconnect from 162-144-108- 19.bluehost.com[162.144.108.19] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 quit=1 commands=7/8 Nov 1 21:24:52 mail postfix/smtpd[10193]: connect from 162-144-108- 19.bluehost.com[162.144.108.19] Nov 1 21:24:52 mail postfix/smtpd[10193]: NOQUEUE: reject: RCPT from 162-144-108-19.bluehost.com[162.144.108.19]: 454 4.7.1 <billo(a)billoblog.com>: Relay access denied; from=<tradfp-bounces+billo=billoblog.com(a)bill-oliver.com> to=<billo(a)billoblog.com> proto=ESMTP helo=<162-144-108-19.bluehost.com> Nov 1 21:24:52 mail postfix/smtpd[10193]: disconnect from 162-144-108- 19.bluehost.com[162.144.108.19] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Nov 1 21:25:48 mail dovecot: auth-worker(10954): Debug: conn unix:auth- worker (pid=10903,uid=116): Disconnected: Connection closed (fd=-1) Nov 1 21:25:48 mail dovecot: auth-worker(10954): Debug: mysql(localhost): Connection finished (queries=1, slow queries=0) Nov 1 21:27:28 mail dovecot: auth: Debug: mysql: Connection finished (queries=0, slow queries=0) FYI, 162-144-108-19.bluehost.com is my ip address and bluehost.com is the VPS vendor. I don't know why that pops up, since the domain is bill-oliver.com. I assume it's VPS-related magic. Here are similar errors in /opt/mailman/mm/var/logs/smtp.log: Nov 01 21:22:46 2024 (1573) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 01 21:22:46 2024 (1573) Peer: ('162.144.108.19', 51476) Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) handling connection Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'LHLO mail.bill-oliver.com' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'MAIL FROM:<billo(a)billoblog.com> SIZE=1486 BODY=8BITMIME' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) sender: billo(a)billoblog.com Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'RCPT TO:<tradfp(a)lists.bill-oliver.com>' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) recip: tradfp(a)lists.bill-oliver.com Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'DATA' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'QUIT' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) connection lost Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) Connection lost during _handle_client() Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> recipients refused: {'oliver(a)billoblog.com': (454, b'4.7.1 <oliver(a)billoblog.com>: Relay access denied')} Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> recipients refused: {'billo(a)billoblog.com': (454, b'4.7.1 <billo(a)billoblog.com>: Relay access denied')} Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> smtp to tradfp(a)bill-oliver.com for 2 recips, completed in 0.27154111862182617 seconds Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> post to tradfp(a)bill-oliver.com from billo(a)billoblog.com, 1448 bytes, 2 failures Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> delivery to oliver(a)billoblog.com failed with code 454, b'4.7.1 <oliver(a)billoblog.com>: Relay access denied' Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> delivery to billo(a)billoblog.com failed with code 454, b'4.7.1 <billo(a)billoblog.com>: Relay access denied' Nov 01 21:24:11 2024 (1574) <173051065026.1640.13931339026208387550(a)162-144-108-19.bluehost.com> smtp to tradfp(a)bill-oliver.com for 1 recips, completed in 0.24669885635375977 seconds Nov 01 21:24:11 2024 (1574) <173051065026.1640.13931339026208387550(a)162-144-108-19.bluehost.com> post to tradfp(a)bill-oliver.com from tradfp-request(a)bill-oliver.com, 1222 bytes I have gone over my main.cf and master.cf a zillion times. Worse, I've compared them with the same files in the setup that works, and I can't find a significant error) though things are in a slightly different order. I don't know if I'm missing something big or am just a poor proofreader. Any ideas would be appreciated. Here's the obligatory main.cf and master.cf in /etc/postfix. I use dovecot and virtual domains and virtual mailboxex administered using postfixadmin. Here's the main.cf: # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 3.6 on # fresh installs. compatibility_level = 3.6 #Enable TLS Encryption when Postfix receives incoming emails smtpd_tls_cert_file=/etc/letsencrypt/live/mail.bill- oliver.com/fullchain.pem smtpd_tls_key_file=/etc/letsencrypt/live/mail.bill- oliver.com/privkey.pem smtpd_tls_security_level=may smtpd_tls_loglevel = 1 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache #Enable TLS Encryption when Postfix sends outgoing emails smtp_tls_CApath=/etc/ssl/certs smtp_tls_security_level = may smtp_tls_loglevel = 1 smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains myhostname = mail.bill-oliver.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mail.bill- oliver.com bill-oliver.com lists.bill-oliver.com virtual_mailbox_limit = 0 mailbox_size_limit = 0 message_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 #Enforce TLSv1.3 or TLSv1.2 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 mailbox_transport = lmtp:unix:private/dovecot-lmtp smtputf8_enable = no virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c f hash:/opt/mailman/mm/var/data/postfix_vmap #virtual_transport = lmtp:unix:private/dovecot-lmtp virtual_mailbox_base = /var/vmail virtual_minimum_uid = 2000 virtual_uid_maps = static:2000 virtual_gid_maps = static:2000 policyd-spf_time_limit = 3600 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_policy_service unix:private/policyd-spf smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination # Milter configuration milter_default_action = accept milter_protocol = 6 smtpd_milters = local:opendkim/opendkim.sock non_smtpd_milters = $smtpd_milters unknown_local_recipient_reject_code = 550 ########################################### Here's the master.cf (comments deleted) : smtp inet n - y - - smtpd submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_tls_wrappermode=no -o smtpd_sasl_auth_enable=yes -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticate d,reject -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth smtps inet n - y - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticate d,reject -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache postlog unix-dgram n - n - 1 postlogd uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) policyd-spf unix - n n - 0 spawn user=policyd-spf argv=/usr/bin/policyd-spf Thanks, billo

2 2

How to fix: [Django] ERROR (EXTERNAL IP)
by Jigme Datse 02 Nov '24

02 Nov '24

This feels like something that I should have working. I know I've not been attending to things all that well, so the thing that has happened, that's got us from, "possibly doing nothing," to throwing this error is that I went to update my mail server, and in the update, Mailman3 stopped working entirely (it was a variety of things), but now it's launching, and will load the main web interface... but Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix. How to fix, probably isn't quite what I'm looking for, it's how to diagnose. The error tells me that the IP address is 127.0.0.1 and that 127.0.0.1 is in the ALLOWED_HOSTS. I *mostly* see this coming from Google, but when I go and look at the webpage, I get: normal page at /mailman3/lists/ But my lists, all give me... Something went wrong HTTP error 500: {"title": "500 Internal Server Error"} I've tried to figure out where to go from here, and right now I'm not making any progress, so I thought I'd ask here.

2 6

redirecting -bounces replies
by Hirayama, Pat 02 Nov '24

02 Nov '24

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>

3 3

Do i need a mailman-hyperkitty.cfg file?
by Bill Oliver 30 Oct '24

30 Oct '24

While trying to set up my new mailman installation in Ubuntu 22.04, which doesn't quite work yet, I decided to compare my config files with my Ubuntu 24.04 LTS installation, which does seem to work to the degree I've tested it. I noticed this little snippet in the settings.py file: # Set this to match the api_key setting in # /opt/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). MAILMAN_ARCHIVER_KEY = 'Secret_Hyperkitty_API_Key' Aha, I thought. I should have changed that. Then I noticed that I didn't even have a mailman-hyperkitty.cfg file, and I can't find mention of it in the venv instructions. I *have* installed mailman- hyperkitty during the "pip install mailman-web mailman-hyperkitty" step. I did a "find" on /opt/mailman, and it doesn't seem the file is there at all. Do I need this file? I found a template here: https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… Do I need to copy and paste that in my installation? Thanks! billo

2 2

Welcome message issue
by Mohsen Masoudfar 29 Oct '24

29 Oct '24

Good afternoon I have an issue with welcome message. A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. - is there a mailman cli option to update the default template for a single list? I couldn't find it in WUI. I reviewed all parameters and variables of the list and couldn't find one that might be related to it. We are running an old version of Mailman 3. Thanks Mohsen

2 2

New installation, new issue: mailman3 migrate -- no module CommonMark
by Bill Oliver 27 Oct '24

27 Oct '24

My Ubuntu 24.04 installation is working great, and I have a list running perfectly. I'm now trying to install mailman3 on an older server, this time runing ubuntu 22.04. I'm following the venv installation instructions again, but suddenly came up with a new error. I've made it to the "Run database migrations" section I run mailmanweb-migrate and get: (venv) mailman@mail:~$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 128, in get_package_libraries module = import_module(entry[1]) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/opt/mailman/venv/lib/python3.10/site- packages/postorius/templatetags/markdown.py", line 21, in <module> from readme_renderer import markdown as md_render File "/opt/mailman/venv/lib/python3.10/site- packages/readme_renderer/markdown.py", line 16, in <module> from CommonMark import commonmark ModuleNotFoundError: No module named 'CommonMark' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.10/site- packages/mailman_web/manage.py", line 87, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/__init__.py", line 436, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 412, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 458, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 106, in wrapper res = handle_func(*args, **kwargs) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/commands/migrate.py", line 100, in handle self.check(databases=[database]) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 485, in check all_issues = checks.run_checks( File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/checks/registry.py", line 88, in run_checks new_errors = check(app_configs=app_configs, databases=databases) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/checks/templates.py", line 60, in check_for_template_tags_with_the_same_name for module_name, module_path in get_template_tag_modules(): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 105, in get_template_tag_modules for name in get_package_libraries(pkg): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 130, in get_package_libraries raise InvalidTemplateLibrary( django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'postorius.templatetags.markdown': No mod ule named 'CommonMark' I know nothing about CommonMark. Since I've suffered the error cascade problem of trying to fix things and just making it worse, I stopped here. Can I ignore this error, or what can I do to fix it? Thanks! billo

2 5

501 Message has defects
by jgn1980＠gmail.com 25 Oct '24

25 Oct '24

Hi I'm using GNU Mailman 3.3.8 (Tom Sawyer) on debian 12, and I have this issue on a scheduled e-mail, every day: 2024-10-25T04:00:04.874081+01:00 XXXXXXX postfix/lmtp[29258]: CEB32100F44: to=<XXX(a)XXX.XX>, relay=localhost[127.0.0.1]:8024, delay=0.02, delays=0.01/0/0.01/0.01, dsn=5.0.0, status=bounced (host localhost[127.0.0.1] said: 501 Message has defects (in reply to end of DATA command)) I have already changed some settings on the postfix and list configurations, without success. Outlook 365 and gmail receive the email without issues. Does anyone have any idea of how I can fix this? Thanks,

2 1

Timeout error on anonymous subscribe
by vogt＠spamcop.net 25 Oct '24

25 Oct '24

Hi, I am running a mailman 3.3.9 server (pip installation). It's working fine so far. However, I have problems setting a template. I set a '[list:user:action:subscribe]' template for a list with some simple text like "test1234". When someone wants to subscribe on the list page without creating an account, it takes five seconds until "HTTPSConnectionPool(host='lists.example.org', port=443): Read timed out. (read timeout=5)" appears on the page. The mail address has been added pending confirmation but no mail gets send. mailman.log shows just exceptions about the timeout itself: Sep 09 15:01:45 2024 (2070549) deque: do_confirm_verify Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.11/site-packages/urllib3/connectionpool.py", line 536, in _make_request response = conn.getresponse() ^^^^^^^^^^^^^^^^^^ ... requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='lists.dkrz.de', port=443): Read timed out. (read timeout=5) [09/Sep/2024:15:01:45 +0200] "POST /3.1/members HTTP/1.1" 400 132 "-" "GNU Mailman REST client v3.3.5" The access log suggests that getting the template took 5s: ==> /opt/mailman/mm/var/logs/access.log <== 127.0.0.1 - - [09/Sep/2024:13:01:45 +0000] "GET /mailman3/api/templates/list/community.lists.example.org/list:user:action:subscribe HTTP/1.1" 200 8 "-" "python-requests/2.32.3" Running curl on that url returns immediately $ curl -v 'http://localhost:8000/mailman3/api/templates/list/community.lists.example.o…' I have captured the network traffic on localhost interface lo and I can see that the request is sent through the tcp connection and acknowledged. Then 5 seconds later the server (port 8000) sends a push data with the response and closes the connection with FIN. The data exchanged on the connection looks like this: GET /mailman3/api/templates/list/community.lists.example.org/list:user:action:subscribe HTTP/1.1 Host: lists.example.org User-Agent: python-requests/2.32.3 Accept-Encoding: gzip, deflate Accept: */* X-Forwarded-Proto: https X-Forwarded-For: 2001:638:1234:1224::111 X-Forwarded-Host: lists.example.org X-Forwarded-Server: lists.example.org Connection: Keep-Alive HTTP/1.1 200 OK Server: gunicorn Date: Mon, 09 Sep 2024 13:01:45 GMT Connection: close Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff Referrer-Policy: same-origin Cross-Origin-Opener-Policy: same-origin X-Frame-Options: DENY Vary: Accept-Language, Cookie Content-Language: en Content-Length: 8 test1234 The timestamp 13:01:45 is the time of the timeout. The request started five seconds before that. It looks to me as if the connection/keepalive handling is not working properly or the server isn't pushing the response immediately, but it gets buffered until the 5s timeout. Occassionally, I have capture a requests, where the client side would send a FIN to the server and only then the server would send the http response with the final packets. Does anyone have an idea how I can fix this? Thanks, Gerald

3 9

User account issue after importing data from Mailman 2.x server
by dgoldsmith＠sans.org 24 Oct '24

24 Oct '24

We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. I just started looking at a user and a list in both the Postorius and Django admin web UIs and found: - in Postorius: - list exists, has 20K plus subscribed members and has 3 list owners - user exists and is subscribed to this list - in Django: - in HyperKitty section - in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators) - in the Emails page, there are 149K plus entries - in the Profiles page, there are 147 entries - in the Accounts->Email addresses page, there are only 155 entries - in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Thanks, David Goldsmith

2 1

Logging subscribes/unsubscribes
by Brian Carpenter 22 Oct '24

22 Oct '24

Does Mailman 3 log subscribes and unsubscribes for each list the way Mailman 2 did? Brian

5 7

Add domain to Mailman, can't create list with that new domain
by Andy Matthews 22 Oct '24

22 Oct '24

I'm testing locally to try and support additional domains. I can add new mailing lists with a domain: announce-123(a)mydomain.com I can't add a new mailing list with an alternate domain: announce-123(a)testing.com Following the documentation for domains I'm able to successfully add the new domain (locally) with the following steps: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… 1. Shell into the mailman server 2. Shell into the mailman Python environment: mailman shell 3. Add a new mailing list. from mailman.interfaces.domain import IDomainManager from zope.component import getUtility manager = getUtility(IDomainManager) manager.add('testing.com') show_domains() # with method from the above documentation URL <Domain testing.com> <Domain mydomain.com> But then when I run a cURL command (from the mailman server) to add a list with that new domain I get an error: $ curl -k -u restadmin:restpass -X POST -H "Content-Type: application/json" --data '{"fqdn_listname": "new-list(a)testing.com"}' https://0.0.0.0:8001/3.1/lists {"title": "400 Bad Request", "description": "Domain does not exist: testing.com"} Am I doing something wrong, or missing a step? If not, how do I add support for additional domains such that I can provide mailing list support for that domain?

3 11

OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?
by Bill Oliver 19 Oct '24

19 Oct '24

OK, I think I was clearly in the phase of dealing with errors caused by my attempts to deal with previous errors. So I backed out and did a clean install. Again, the installl seemed to go without a problem. Then: 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" forensic pathologists to discuss cases. 2) I added a couple of users: oliver(a)billoblog.com on the same box as the mailinglist, though on different virtual domains, and william.oliver(a)knoxcounty.org, a local government domain not associated with my box. Results: The welcome message did not get delivered to either address. When I send email from those addresses to tradfp(a)forensicpath.us, I get the following error from both: Your message couldn't be delivered The message you sent to tradfp(a)forensicpath.us couldn't be delivered due to: Recipient email address is possibly incorrect. Further information 5.1.1 <tradfp(a)forensicpath.us>: Recipient address rejected: User unknown in virtual mailbox table If you sent this message to multiple addresses, you'll receive a notification like this for every one that didn't arrive. That is when I started going down the dovecot rabbit hole. Here's the (what I think is relevant) part of the mail.cf file: virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c f virtual_mailbox_base = /var/vmail virtual_minimum_uid = 900 virtual_uid_maps = static:900 virtual_gid_maps = static:900 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains In my previous attempt, I added hash:/opt/mailman/mm/var/data/postfix_lmtp to both virtual_mailbox_maps and virtual_alias_maps, but I haven't done that yet here. I thought I'd ask and make sure I should. Should that be my next step? Thanks, billo

2 3

Debug=False breaks Django/MM3-Login-page
by Stefan Bauer 18 Oct '24

18 Oct '24

Hi folks, I'm trying to hide the custom 404 error messages from Django. ------------------------- Page not found (404) Request Method: GET Request URL: http://......./non-existent-2008020390 Using the URLconf defined in mailman_web.urls, Django tried these URL patterns, in this order: mailman3/ archives/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] accounts/ admin/ postorius/ hyperkitty/ The current path, non-existent-2008020390, didn’t match any of these. You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. ----------------------------- Switching DEBUG=True (currently set in settings.py) to false does indeed hide additional debugging output, but following pages are not accessible anymore (Server Error). user-profile/ accounts/logout/ hyperkitty/ Switching back to DEBUG=True brings back accessibility. This is Mailman Core-Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] any help is greatly appreciated. Thank you. Stefan

2 1

adding personalized email header/content in mailman 3
by Alex I 17 Oct '24

17 Oct '24

adding personalized email header/content Hello, I'm upgrading from mailman 2.1 and need to have personalized email header and content. In 2.1 eventually (couldn't get custom handler work) I had to modify Decorate.py handler. Basically encrypting email and passing it as a parameter in google required One-click unsubscribe email header link (same in the message body). I tried creating a custom Handler (custom_header.py) in 3.3.19, adding outgoing_pipeline = custom_header in config [mta] section but it doesn't seem to be activating. Thanks

2 6

Verification emails 'helo' rejected
by Greg Newby 16 Oct '24

16 Oct '24

Hi friends. I'm now getting a 500 server error upon signing up a new username on the web-based front end. The username is created in the back end, but the verification email does not get sent. This is GNU Mailman 3.3.9 (Tom Sawyer), venv, Ubuntu 24.04LTS, PostgreSQL, Postfix Here are the corresponding logfile entries from mailmanweb.log: smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 <mail>: Helo command rejected: need fully-qualified hostname')} and from mail.log: Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost> proto=ESMTP helo=<mail> lists.domain.tld is the domain for Mailman3. I don't know why it's trying to send email from root@. I've seen places where 'localhost' appears in the Mailman settings (settings.py, mailman.cfg, mailman-web.py), and tried changing them to the host's FQDN and restarting mailman3 and mailman3-web, but the problem persists. Suggestions will be appreciated. ~ Greg

4 8

mailmanweb/django?: too many postgresql DB connections
by api＠egartech.com 16 Oct '24

16 Oct '24

Hello, I'm migrating from mailman 2.1 to the latest version (3.3.9) on Almalinux 9 (python 3.19, postgresql 13.16). Have followed the instructions here https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install to perform a clean install on a new VM. Everything seems to be working (well, I just created one list and doing some basic tests). What I have noticed is hundreds of PGsql connections from mailmanweb. Once mailmanweb service is started there are new non-stop DB connections requests (from Django I guess), here is just 1 second from PGsql log: 2024-10-10 12:15:37.112 EDT [3217] DEBUG: forked new backend, pid=3747 socket=10 2024-10-10 12:15:37.113 EDT [3217] DEBUG: server process (PID 3746) exited with exit code 0 2024-10-10 12:15:37.318 EDT [3217] DEBUG: forked new backend, pid=3748 socket=10 2024-10-10 12:15:37.318 EDT [3217] DEBUG: server process (PID 3747) exited with exit code 0 2024-10-10 12:15:37.523 EDT [3217] DEBUG: forked new backend, pid=3749 socket=10 2024-10-10 12:15:37.524 EDT [3217] DEBUG: server process (PID 3748) exited with exit code 0 2024-10-10 12:15:37.728 EDT [3217] DEBUG: forked new backend, pid=3750 socket=10 2024-10-10 12:15:37.729 EDT [3217] DEBUG: server process (PID 3749) exited with exit code 0 2024-10-10 12:15:37.934 EDT [3217] DEBUG: forked new backend, pid=3751 socket=10 2024-10-10 12:15:37.935 EDT [3217] DEBUG: server process (PID 3750) exited with exit code 0 Few minutes later there are around 300 dead (TIME_WAIT) connections to port 5432 like these: tcp 0 0 127.0.0.1:33728 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40392 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:50860 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40254 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40218 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40110 127.0.0.1:5432 TIME_WAIT I'm totally unfamiliar with Django so not sure where even to look, but that doesn't looks right to me. Thanks

1 1

Database permission problem?
by Bill Oliver 16 Oct '24

16 Oct '24

I have mailman3 installed and mostly configured on a linux machine running ubuntu 24.04. I can use mailmanweb to add and delete mailinglists and users. However, mail is not getting delivered at all. I have both mysql and postgres installed -- I'm using postgres only for mailman, and mysql for dovecot and postfix. Mail, in general, works fine. I'm hosting four virtual domains on this box, and mail to and from all of them to many users gives me no errors. When I add a new user (and thus try to send a welcome message) mail.err log gives me: 2024-10-15T12:40:11.193687-04:00 mail postfix/virtual[960838]: error: open database /opt/mailman/mm/var/data/postfix_lmtp.db: Permission denied I've tried playing with file permissions. I put postfix,mail, and vmail in the mailman group, and tried giving ownership of postfix_domains, postfix_lmtp, and postfix_vmap to user postfix, but that changed nothing. Currently, it sits at: root:/opt/mailman/mm/var/data# ls -l total 36 -rw-rw-r-- 1 postfix mailman 0 Oct 15 12:53 postfic_vmap.db -rw-rw-r-- 1 postfix mailman 12288 Oct 15 12:53 postfic_vmap.db.db -rw-rw---- 1 postfix mailman 353 Oct 13 07:54 postfix_domains -rw-rw-r-- 1 postfix mailman 0 Oct 15 12:53 postfix_domains.db -rw-rw-r-- 1 postfix mailman 12288 Oct 15 12:53 postfix_domains.db.db -rw-rw---- 1 postfix mailman 1155 Oct 13 07:54 postfix_lmtp -rw-rw-r-- 1 postfix mailman 0 Oct 15 12:53 postfix_lmtp.db -rw-rw-r-- 1 postfix mailman 12288 Oct 15 12:53 postfix_lmtp.db.db -rw-rw---- 1 postfix mailman 1118 Oct 13 07:54 postfix_vmap So, I'm assuming this is a database permissions error, but I don't know how to fix it. As an aside, my main.cf is below. Any help would be appreciated. billo %cat main.cf smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 3.6 on # fresh installs. compatibility_level = 3.6 #Enable TLS Encryption when Postfix receives incoming emails smtpd_tls_cert_file=/etc/letsencrypt/live/mail.forensicpath.us/fullchai n.pem smtpd_tls_key_file=/etc/letsencrypt/live/mail.forensicpath.us/privkey.p em smtpd_tls_loglevel = 1 smtpd_tls_security_level=may smtpd_tls_loglevel = 1 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache #Enable TLS Encryption when Postfix sends outgoing emails smtp_tls_CApath=/etc/ssl/certs smtp_tls_security_level = may smtp_tls_loglevel = 1 smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = mail.forensicpath.us alias_maps = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 #Enforce TLSv1.3 or TLSv1.2 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 mailbox_transport = lmtp:unix:private/dovecot-lmtp smtputf8_enable = no virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf #added 20241009 for mailman hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c f #added 20241009 for mailman hash:/opt/mailman/mm/var/data/postfix_vmap virtual_mailbox_base = /var/vmail virtual_minimum_uid = 900 virtual_uid_maps = static:900 virtual_gid_maps = static:900 policyd-spf_time_limit = 3600 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination, check_policy_service unix:private/policyd-spf # Milter configuration milter_default_action = accept milter_protocol = 6 smtpd_milters = local:opendkim/opendkim.sock non_smtpd_milters = $smtpd_milters #Mailman transport stuff transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains

5 12

max_day_to_hold - when in force?
by Wikinaut 15 Oct '24

15 Oct '24

There are quite few discussions (back to 2020) dealing with the variable max_day_to_hold and the (non-) handling of the set value, I found for example Marc's comment https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… : I'm really not sure what you are looking to do, but I can tell you that while the max_days_to_hold list attribute exists and can be set, the actual discarding of held messages older than max_days_to_hold is not implemented. Thus the setting currently does nothing. My question: Are there any plans to bring this into action, so that held messages are really discarded after that number of days? (like it was in mailman2)?

2 1

're' problem is sending messages to queue/shunt for an entire domain
by Greg Newby 15 Oct '24

15 Oct '24

Hi friends. I have multiple domains under MM3 (venv, postfix+postgres, Ubuntu 24.04LTS). Currently at version GNU Mailman 3.3.9 (Tom Sawyer). Following some user complaints, I've discovered that one of the domains isn't working at all. Messages arrive via postfix and are in the MM smtp.log, but then generate a Python error in mailman.log. Other domains are working as usual. The lists in this domain used to work (I can see messages in the archives, and have received copies). But I imported a bunch more MM2 lists since then, and perhaps there is a problem with one of their configurations. Pointers to how to fix this will be appreciated! Here is the error from ~mailman/mm/var/logs/mailman.log: ==> mailman.log <== Oct 13 23:27:34 2024 (365022) Uncaught runner exception: multiple repeat at position 11 Oct 13 23:27:34 2024 (365022) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/runners/incoming.py", line 80, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/rules/banned_address.py", line 40, in check if ban_manager.is_banned(sender): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py", line 103, in is_banned re.match(ban.email, email, re.IGNORECASE) is not None): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 167, in match return _compile(pattern, flags).match(string) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile p = _compiler.compile(pattern, flags) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile p = _parser.parse(p, flags) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 979, in parse p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub itemsappend(_parse(source, state, verbose, nested + 1, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse raise source.error("multiple repeat", re.error: multiple repeat at position 11 Followed by a message that it's going to queue/shunt: Oct 13 23:15:25 2024 (365022) SHUNTING: 1728886525.4656847+d1a03bf710a246d029a087eabd40bed11c1af4b5 ... where it stays. Delivery never happens. I've tried with listname(a)lists.domain.tld as well as listname-owner(a)lists.domain.tld. The lists in the domain seem to be set up properly -- they used to work fine! I am suspicious the problem happened when I imported some other lists, but those imports didn't cause any errors. I've done the usual sequence of restarting mailman services, rebooting the server, double-checking the configuration files, and reviewing the list settings. Thanks for your help! ~ Greg

2 2

Search function returning results from another list
by Marco van Tol 15 Oct '24

15 Oct '24

Hi there, We have several lists on our list server here, and noticed that if we do this: - go to the archive of public list x - type in "minutes" in the search bar If will: - show a screen: list-x search results for query "minutes" - have 3 results in there for another private list - show a message that you need to login to view the message if you click on one Our current mailman core version is: 3.3.9 Our current hyperkitty version is: 1.3.10 Our index engine is: xapian_backend.XapianEngine Does this make sense? Thanks! Marco van Tol RIPE NCC

1 2

Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails
by francesd919＠gmail.com 12 Oct '24

12 Oct '24

Hi everyone, I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. These emails mentioned that the subscription was disabled due to bounce score. Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. I have some questions: 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. 3. What could have cuased functioning emails to bounce and therefore being disabled? Thank you in advance! Frances 3.

2 1

mailman changeaddress: Address already exists; can't change
by joelbrownstein＠computer.org 12 Oct '24

12 Oct '24

Hi, We migrated ~100 lists from mailman2 to mailman3 (very nice!) including > 6000 distinct email addresses ("subscribers"). I would like to run the mailman changeaddress command to do a global change of email for a member that moved. But they have other subscriptions using their new email, so both the old and new address are migrated to mailman3 as distinct "members", which prevents the mailman changeaddress from making the change with error: $ mailman changeaddress "EMAIL_1" "EMAIL_2" Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS Try 'mailman changeaddress -h' for help. Error: Address "EMAIL_2" already exists; can't change. Is there a workaround? Thanks, Joel

2 1

MM3 error on moderation request
by Odhiambo Washington 11 Oct '24

11 Oct '24

MM3 - 3.3.10, Postorius 1.3.13. After receiving the notification to attend to a moderation request: ``` At your convenience, visit https://mm3-lists.kictanet.or.ke/mm/lists/kictanet.lists.kictanet.or.ke/hel… to approve or deny the request(s). ``` Upon visiting the link I ended up with a server error. mailmanweb.log has the below to say: ``` [ERROR] [2024-10-10 12:29:15,905] [log] 809040 139858772735552 Internal Server Error: /mm/lists/kictanet.lists.kictanet.or.ke/held_messages Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/defaulttags.py", line 1026, in find_library return parser.libraries[name] ~~~~~~~~~~~~~~~~^^^^^^ KeyError: 'humanize' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/contrib/auth/decorators.py", line 23, in _wrapper_view return view_func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/postorius/auth/decorators.py", line 63, in wrapper return fn(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/postorius/views/list.py", line 889, in list_moderation return render(request, 'postorius/lists/held_messages.html', context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loader.py", line 61, in render_to_string template = get_template(template_name, using=using) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loader.py", line 15, in get_template return engine.get_template(template_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/backends/django.py", line 33, in get_template return Template(self.engine.get_template(template_name), self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/engine.py", line 175, in get_template template, origin = self.find_template(template_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/engine.py", line 157, in find_template template = loader.get_template(name, skip=skip) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loaders/cached.py", line 57, in get_template template = super().get_template(template_name, skip) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loaders/base.py", line 28, in get_template return Template( ^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 154, in __init__ self.nodelist = self.compile_nodelist() ^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 200, in compile_nodelist return parser.parse() ^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 513, in parse raise self.error(token, e) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 511, in parse compiled_result = compile_func(self, token) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loader_tags.py", line 293, in do_extends nodelist = parser.parse() ^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 513, in parse raise self.error(token, e) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 511, in parse compiled_result = compile_func(self, token) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/defaulttags.py", line 1088, in load lib = find_library(parser, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/defaulttags.py", line 1028, in find_library raise TemplateSyntaxError( django.template.exceptions.TemplateSyntaxError: '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 [WARNING] [2024-10-10 12:29:16,384] [log] 809040 139858704070336 Not Found: /mc/compose ``` How to fix? -- 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]

2 2

Two trivial questons:
by Bill Oliver 10 Oct '24

10 Oct '24

First: Last night I got everything installed and, I think, working. Unfortunately, I forgot to write down the name and password of the superuser I created. I know what I put in as password, but I cant' remamber the name of the superuser. I know I could just create another superuser with "mailmanweb createsuperuser" but I was wondering if there was a "mailmanweb" command for *listing* superusers. If not, I'll just make another superuser... Second: I have the "example.com" error in the login screen. The instructions state that this is a problem with making SITE_ID=1. Okay, but I don't know what to change it to. I tried SITE_ID=2 on a lark and everything broke, and the instruction say not to do SITE_ID=0. Apparently it has to be an integer (I also tried putting in site name and got that error). So... where do I change it? Thanks! billo

1 3

Congrats on the instructions for installation on ubuntu, what about migration?
by Bill Oliver 09 Oct '24

09 Oct '24

So I went ahead and tried to install mailman3 on ubuntu 24.04 using the virtual environment approach. It worked like a charm. There were a very few glitches, all from me not reading the instructions closely (e.g. not replacing MY_SERVER with my server name, Doh). The whole thing, from start to finish was about two hours. I appreciate all y'alls efforts in this. The reason I'm doing this is that I'm having to migrate from a server that's going to be defunct soon. I've been running a mailman3 mailing list on that for a few years. Is there a tutorial/instructions on migrating data from an old system to a new one? It's actually not the end of the world if I don't get all the old emails transferred, but I'd like to get the email addresses of the participants moved over easily... I believe that I set it up in 2020, but did not do any version upgrades since then... Thanks! billo

3 3

Upgrade docker-mailman to v0.5.2
by Christopher 08 Oct '24

08 Oct '24

Hi Abhilash, I checkout the v0.5.2 for testing my upgrade from 0.4.6 and noticed, that the docker-image-version is still set to 0.4 in docker-compose.yaml. Is there any reason for it or should it be set to 0.5? I´m still using my good old mariadb. I did not find any upgrade-informations about breaking-changes. Do you have any experience with migrating from 0.4.6 to 0.5.2 on mariadb? Best regards Chrclaus

1 0

anomalous behavior
by donato＠molino.it 05 Oct '24

05 Oct '24

Hi, I installed mailman-full on debian 12. Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. I have three MLs: 1) example(a)example.com 2) test(a)example.com 3) hello(a)example.com For the n. 2 and 3 are fine, but 1 doesn't deliver. The configurations are identical for all 3: smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' I also enabled all debugging in mailman.cfg. But everything is fine Thanks Donato

3 5

Should I try to install mailman3 on Kubuntu 20.04?
by Bill Oliver 05 Oct '24

05 Oct '24

I have been a happy camper running mailman3 on a vps I rent from a vendor, running CentOS 7. CentOS 7 is past end of life, so I moving over to a new machine running Kubuntu 20.04 LTS. I have been searching the intertubes and have seen a bunch of people having headaches trying it. So... Is Ubuntu 20.04 cool with mailman3? Should I go ahead and give it a shot or use a different distro? Should I do the apt install, the virtualenv install, or try the docker install? thanks billo

4 5

reset bounce-scores?
by IEM Network Operation Center (IOhannes m zmölnig) 04 Oct '24

04 Oct '24

i'm running a mailman-3.3.8 instance, and would like to reset the bounce-score for a (number of) user(s). i searched the internet and this list's archives, but haven't found anything useful so far. due to a misconfiguration of our universities reverse DNS lookup, the bounce score of some users has rocketed in the last days - some users have already been unsubscribed because of that. could anybody please share how i can reset the bounce score? gfmasdr IOhannes ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

2 1

makemigrations --merge error after Debian upgrade
by Chupin Maxime 03 Oct '24

03 Oct '24

Hi, I upgraded my debian version, and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: ``` CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). To fix them run 'python manage.py makemigrations --merge' ``` So I tried `mailman-web makemigrations --merge` that ended with ``` PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' ``` There is no such a file in the migration directory. Any idea ? Thanks in advance, All the best Maxime Chupin

4 19

Confusing order of checkboxes in Postorius
by Markus Grandpré 02 Oct '24

02 Oct '24

Dear list, dear Mailman3 developers, dear Mark Sapiro, in Postorius under "Mass operations / Mass subscribe" we find the order of the checkboxes confusing: 1. Pre confirm 2. Pre approved 3. Pre Verified 4. Invitation We think it would be easier for us and our mailing list administrators to understand the interaction of these settings if they were displayed in the following order: 1. Pre confirm 2. Pre Verified 3. Pre approved 4. Invitation as in our opinion "Pre confirm" and "Pre Verified" belong together more than "Pre confirm" and "Pre approved". Incidentally, a typing error has crept into the term "Pre Verified". It should read "Pre verified". Yours sincerely, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 0

Mailman Core release
by Abhilash Raj 02 Oct '24

02 Oct '24

Hey Everyone! I am pleased to announce new release of Mailman Core 3.3.10. This includes both bug fixes and new features. A full list of changes can be found at the usual location[1]. This release includes a Breaking change and nntp runner no longer starts automatically in the default release. You can easily enable the runner by updating your `mailman.cfg`. See the release notes[1] for details on how. This release can be downloaded from PyPI[2] or using `pip install mailman==3.3.10`. For those interested in package signatures, both the source tarball and built wheel are available in Gitlab releases[3] along with their signatures. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://pypi.org/project/mailman/ [3]: https://gitlab.com/mailman/mailman/-/releases/v3.3.10 -- thanks, Abhilash Raj (maxking)

1 0

Default values for lists in Mailman 3
by Markus Grandpré 30 Sep '24

30 Sep '24

Dear list, I would like to activate the invitation setting for all lists as default. In Mailman 2.1 I have done this in the file </etc/mailman/mm_cfg.py>: DEFAULT_SUBSCRIBE_OR_INVITE = Yes How can I do this in Mailman 3? Can I also transfer other default values like: ... DEFAULT_SERVER_LANGUAGE = 'en' DEFAULT_SEND_REMINDERS = 1 DEFAULT_SUBSCRIBE_OR_INVITE = Yes DEFAULT_PRIVATE_ROSTER = 2 DEFAULT_ARCHIVE = Off DEFAULT_ARCHIVE_PRIVATE = 1 ... from the very same configuration file to Mailman 3? Is there a documentation of the default values for lists in Mailman 3? Best regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

2 4