September 2024 - Mailman-users - lists.mailman3.org

How to remove Held Unsubscriptions
by Mark 10 Sep '24

10 Sep '24

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 6

Mass Subscribe caused Delivery Status to become "unset"
by chad.hays86＠gmail.com 09 Sep '24

09 Sep '24

One of the admins on our Mailman site said they recently performed a mass subscribe operation on list, however they noticed that for each user they subscribed, their "Delivery status" was unset, so they weren't receiving email updates whenever there was new activity on the list. They had to go in after the fact and manually set it to "Enabled" for each user that was subscribed via the mass subscription operation. Is this behavior expected? During the mass subscribed, pre-confirm, pre-approved, and pre-verified checkboxes were all checked.

3 3

It takes a very long time to display the list archives
by bryan.kartzman＠yu.edu 09 Sep '24

09 Sep '24

When I try to display the archives of any list in my mailman3 installation it takes forever for it to display. We are talking a good three or four minutes. It doesn't matter if there are 100 messages in the archives or just one. We are using postgres for the mailman3 and django databases. On the server, when I click to display a list's archives, I see the process "gunicorn: worker [gunicorn]" is using nearly 100% of available CPU.

1 0

Timeout error on anonymous subscribe
by vogt＠spamcop.net 09 Sep '24

09 Sep '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

1 0

when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented
by Ken Alker 09 Sep '24

09 Sep '24

We have been experiencing a strange anomaly. We are running a small-ish list. When a particular subscriber to the list sends an email to the list, a couple of dozen (or more) of the recipient's of the message end up with their bounce scores incrementing. This particular subscriber uses about three different email addresses when he sends his messages and every one of them causes this behavior. There is another subscriber who also causes this behavior when he sends an email to the list, but only one of the two email addresses he sends from causes this behavior. There is a third person who causes this behavior every time. There are dozens of other subscribes who don't generate this behavior when they send to the list. I can't figure out why this is occurring. I *assume* that Mailman re-writes the headers to add DKIM, etc., before sending them to the list recipients but it sure seems like something in the header from the original sender is ending up in the final header (or something is LACKING) which is not liked by the recipient's MTA's. It doesn't seem like a subscriber sending an email to the list should be able to cause this behavior - but I'm no expert. The recipients appear to be using many different mail platforms (ie. their addresses are not all, or even mostly, @google.com or some other domain; the recipients appear to be a pretty good cross section of platforms). This has been going on all year (maybe longer). Any help or troubleshooting suggestions would be greatly appreciated.

5 9

How to tell which lists on my server are being used?
by Bryan Kartzman 08 Sep '24

08 Sep '24

Is there an easy way to tell which lists on my Mailman 3 installation are being used (i.e. received posts in the last two or three months)?

4 4

Setting base_url for the domain to use it in the templates.
by Timour Bakeev 08 Sep '24

08 Sep '24

Hi all! I'm trying to use extended placeholders for the [templated texts](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/res… in the message footer that are sent to the members: > Along with these, Mailman supports placeholder as URLs for web interface when `base_url` property is set at the Domain level. These include: > domain_url - URL to homepage for a domain. > mailinglist_url - URL to homepage for a mailinglist. > held_message_url - URL to page for handling all held messages. > pending_subscriptions_url - URL to page for handling pending subscription requests. > pending_unsubscriptions_url - URL to page for handling pending unsubscriptions. The REST API docs mention `base_url` as the property of the domain: [domain URLs](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest… But my attempts to use REST API to set it fail: ``` curl --user 'restapi:restpass' \ -X PATCH \ -H "Content-Type: application/json" \ -H 'Accept: application/json' \ -d '{ "base_url": "https://example.net/mailman3" }' \ http://localhost:8001/3.1/domains/example.net | jq '.' { "title": "400 Bad Request", "description": "Unexpected parameters: base_url" } ``` My MM3 instance is the latest(3.3.9), provided by the maxking mailman-core docker image. It looks like there is a lot of confusion about `base_url` in general, as hyperkitty seems also use the property with the same name, for example: https://lists.mailman3.org/hyperkitty/list/mailman-users@mailman3.org/threa… So what is the correct way to get those extended placeholders to work in the templates? It's also not clear to me, what the the primary domain should be for the installation - server hostname, as in `lists.mailman3.org` or the domain, used in the mailing list(s) itself, like `mailman3.org` for mailman-users(a)mailman3.org... With best regards, Timour Bakeev

4 6

Mailman3 migration and/or archiving problem
by hnpilot＠phnet.fi 06 Sep '24

06 Sep '24

I have installed a mailman3 server following this documentation: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… After a few hiccups I got mailman and postorius working and migrated one list according to this documentation: https://docs.mailman3.org/en/latest/migration.html It seemed to work and also hyperkitty_import was run without errors (or at least none shown up). Running update_index command said that there were 0 threads copied but I kjnow that the archive isn't empty. But now when I tried to open the list info page from lists view it dies with 500 error. After diving into the different log files I found an error message that it cannot find /etc/mailman3/mailman-hyperkitty.cfg. Great. Only that the cfg file exists and seems to my (unexpert) eyes correct. After that problem I tried to create a new list. Creation seemed to go all right but also with it, trying to open the list info page it shows 500 error. When googling for a solution I landed on a message stating that there might be double entries for the same list in listarchiver table but when I checked ot turns out that the table is empty! I am a bit confused how to figure out the base cause of the problem and would very much appreciate any pointers. wbr hank

2 1

Archive not updated
by mailman3＠escapade.ch 06 Sep '24

06 Sep '24

Hi All, Env: Debian bookworm debian pkg mailman 3.3.8-2~deb12u2 Status I moved from MM2 to MM3 Import of the archives worked, no issue problem: current emails sent to the list are not being archived. What have I done: - based on the list here I've checked different settings in the cfg files - looked for errors in the log What else can I do to solve this problem ? Many thanks in advance for your help. Manny

3 2

Can you use @list to include members in accept these non-members in v3?
by Lieuallen, Thomas Otis 05 Sep '24

05 Sep '24

In Mailman v2, one could use @listname in ‘accept_these_nonmembers’: A line consisting of the @ character followed by a list name specifies another Mailman list in this installation, all of whose member addresses will be accepted for this list. I don’t see this option listed in version 3. Is it no longer supported/allowed? Is there another option? We often send email to lists of lists and have loved that @listname option to help us deliver email to 20+ lists without needing to approve the emails each time or reconfigure all the lists when another sender needs to be added. Thank you Tom Lieuallen Oregon State University

3 4