- Mailman-users - lists.mailman3.org

Feature request, hyperkitty, low volume lists
by Alain D D Williams 09 Jan '25

09 Jan '25

I host several low volume mail lists. Typically these are announcement lists where low volume is deliberate -- too many emails and people might unsubscribe. These lists are archived but most months there are not any postings. Browsing the archives can mean much clicking to find content, this is done better with mailman2. My request is to make finding content easier. Possibilities: • On the summary (left hand side) put the number of posts after the month name • Only show months (left hand side) where there are any posts For an example see: https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… (There is one post in November) 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 5

Moderation via email?
by Arte Chambers 08 Jan '25

08 Jan '25

Is it possible to approve or deny message and subscription requests from email? Thank you, Paul 'Arte Chambers' Robey

1 0

Mailman3 Docker persmission denied
by Commander456 06 Jan '25

06 Jan '25

Hello everyone, I recently installed the mailman-core Docker image (Version 0.5) and tried to create a list using the mailman commands inside the container. I used the --notify argument but doesn't receive any mail (I'm the list owner), However, inside the mailman.log I get the following error: Jan 06 20:54:25 2025 (156) Uncaught runner exception: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' Jan 06 20:54:25 2025 (156) Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 164, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: ^^^^^^^^^^^^^^^^^^^^ PermissionError: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' Jan 06 20:54:25 2025 (156) Skipping and preserving unparseable message: 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8 These are my file permissions: mailman-core:/opt/mailman/var/queue# ls -l total 48 drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 archive drwxrwx--- 2 mailman nogroup 4096 Jan 6 20:54 bad drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 bounces drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 command drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 digest drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 in drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 nntp drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 out drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 pipeline drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 retry drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 shunt drwxrwx--- 2 mailman nogroup 4096 Jan 6 20:54 virgin mailman-core:/opt/mailman/var/queue/virgin# ls -l total 0 Do you have any idea what I'm doing wrong? Thank you

2 2

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