January 2022 - Mailman-users - lists.mailman3.org

Re: Held messages: Long time waiating for response of the Mailman API
by Krinetzki, Stephan Jan. 31, 2022

Jan. 31, 2022

Hi everyone, any news here? We are running with Pyton 3.6 - maybe a Python Upgrade can speed Mailman up? Regards Stephan -- Stephan Krinetzki IT Center Gruppe: Anwendungsbetrieb und Cloud Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24866 Fax: +49 241 80-22134 krinetzki(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pkcs7-signature Name: smime.p7s

5 14

DMARC DNS settings for MM3?
by Jay Hamilton-Roth Jan. 31, 2022

Jan. 31, 2022

Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com -or- v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com -or something else- Our DNS' SPF record is: v=spf1 ip4:aa.bb.cc.dd +a +mx ~all [Note: aa.bb.cc.dd is a redacted address] I'd rather not experiment on DMARC record settings for fear of making a bad situation worse. Thanks in advance for any assistance.

2 1

mailman 2.1 or 3.0 (or another MLM)
by nate Jan. 29, 2022

Jan. 29, 2022

Hello mailman users out there - I have been a casual user of mailman for 21 years now I think it is. Most of my lists were super small (my only current lists have no more than 8 members each), super low volume. It's "just worked" over the years, no issues. I have been using Linux since 1996, not a newbie here. 21 years ago I deployed mailman as part of our corporate email and then there were a lot more users. Since that time I just use mailman on my personal server. I did a apt-get dist-upgrade on my system and was surprised to see mailman had vanished. Wasn't expecting that.. not a big deal, or so I thought. I am running Devuan 4, which is based on Debian. Investigating further it seems Debian at some point dropped Mailman 2.1 and started including Mailman 3. OK, not too bad I thought.. I was/am prepared to start my mailing lists from scratch again, manually copy/paste over settings/users/etc. Don't care about archives etc. I setup mailman 2.1 on another Devuan 3.x system and copied my mailman configs over to it, and can view them fine via the mailman cgi scripts through Apache, I was planning on just copy/pasting list settings between the two systems for each list. Roughly 10-15mins into trying to get mailman3 off the ground I just find myself overwhelmed. That doesn't happen often. I'm honestly completely shocked at how it seems the complexity of the system has increased by orders of magnitude. I have been browsing around https://docs.mailman3.org/en/latest/pre-installation-guide.html (and other links on that documentation site) But as much information as there is, to me there really isn't any information there. If that makes sense. I'm sure it doesn't make sense so let me give an example. On this page: https://docs.mailman3.org/en/latest/config-web.html I assume that would lead me to how do I configure the web interface so I can do stuff with it. I setup an admin account, then it goes into scheduled tasks(which appear to be handled by the Debian package already but don't know what these tasks would have to do with a web interface). I tried sending a test email but that failed, I looked at the setting up email portion but it does not give any indication where that config would be stored, a recursive grep on /etc for EMAIL_BACKEND turns up nothing (there is a /etc/mailman3 directory with some files in there). Then it goes into other things like task queues, full text searching, here I am just looking for info on where this web interface is, where is the config, what port does it listen on? Is it a cgi like mailman2? It seems like it could be a standalone service. Then it shows a bunch of other settings, not indicating what file these are stored in(or what directory the file is in), etc etc etc. Debian's own documentation is severely lacking in this department as well, normally I am used to going to /usr/share/doc/<package>/ and there is some useful stuff. There is stuff for mailman3 but it's minimal at best. So I'm thinking mailman3 is not the package for me. I've really appreciated mailman 2.1 (and earlier versions) as I said they always just worked, never had to think about them. I'm sure a lot of good hard work has been put into 3, I just don't recall the last time I looked at a project and just honestly didn't even know where to begin which surprised me so much given my 20+ year history of mailman as a user and as an admin. Is there some document(s) out there that would be more beneficial to me in setting up mailman3? I see that mailman 2 looks like it's still being maintained, I assume mailman3 is the result of python3 code and mailman2 perhaps uses python 2.7? I am unsure on the ability to run mailman2 on a modern Debian-based distro since of course Python 2.7 is pretty obsolete at this point (or maybe Mailman 2.1 doesn't use python I don't recall). I could try to install the older mailman 2.1 package on Devuan 4 and see what happens I don't know if it would be that simple or not. Or is there a better MLM for simple use cases? I used Majordomo back in the 90s and was happy to get onto Mailman from that. Something similar to Mailman 2.1 in features/functionality. Worst case I could just use aliases in my postfix config at the end of the day that is all that is really needed, though I do like some level of access control on who can email the lists(even if nobody outside the list knows the list exists), I've had some of these lists for 2 decades, old habits die hard right? I did some searches for mailing list software on the Debian package archives and saw a few options, nothing really stood out at me as something super interesting yet though. I don't mean to come across as harsh or complaining or anything I'm just here in shock kind of. Thinking about what the best solution for me would be. My mailing lists have been broken for a couple of weeks but that's really not a big deal. thanks nate

6 14

Cannot request password reset: "The e-mail address is not assigned to any user account"
by dave＠aasv.org Jan. 28, 2022

Jan. 28, 2022

I have set up Mailman Core Version GNU Mailman 3.3.5 with Mailman Core API Version 3.1 (Python 3.8.10) using the version 0.40 Docker images. I was able to get things set up and tested by requesting a password reset for the MAILMAN_ADMIN_USER specified in the docker.yaml. Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). Using the MAILMAN_ADMIN_USER I can sign in, view the list of all the users, see their Addresses (one each) and Subscriptions, but even after toggling off "Verified" for the staff email address, clicking Update, then turning Verified back on and updating again, I still can't reset the password for that email address from the "forgot pasword" screen. Even tried adding that email address as another list owner. I have not made any API calls specific to adding users because the API documentation says, "Since her email address is not yet known to Mailman, a user is created for her." This does seem to have happened; GET 127.0.0.1:8001/3.1/users does show everyone's display name and unique user_id strings. I have tried using the API to PATCH a temporary password to the user but that didn't fix the inability to reset. The encrypted password does show in the /users/ data reported by the API (where previously there had been none), and a POST to users/<user_id>/login with that password return the 204 status shown to indicate success (instead of 403)... but I can't log in using Postorious with this user's email address and password. I also tried PATCHing the cleartext_password to /users/<email_address> and wasn't able to login or reset after that either. According to the API, each of the users -- webadmin where I can reset the password and staff where I can't -- does have a single address. (In the following, I redacted the API username and password ; changed email addresses, and IP address. And the display name, but left the timestamps and user_ids ) $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "webadmin(a)example.com", "original_email": "webadmin(a)example.com", "registered_on": "2021-11-25T04:20:33.408184", "self_link": "http://1.2.3.4:8001/3.1/addresses/webadmin@example.com", "verified_on": "2021-11-25T04:20:33.960577", "user": "http://1.2.3.4:8001/3.1/users/29bf1eef2ee14f39a7990757544f11a9", "http_etag": "\"394c07148f3fd0479cc582358b63b919fd988e36\""}], "http_etag": "\"a6621373598d299c32aa946fef7e32167d796bf3\""} $ curl --user xxxx:xxxx "127.0.0.1:8001/3.1/users/73235926306843ccb41f288d0464240a/addresses" {"start": 0, "total_size": 1, "entries": [{"email": "staff(a)example.com", "original_email": "staff(a)example.com", "registered_on": "2021-12-15T02:25:24.055741", "self_link": "http://1.2.3.4:8001/3.1/addresses/staff@example.com", "display_name": "Staff Member", "verified_on": "2021-12-15T02:40:04.941153", "user": "http://1.2.3.4:8001/3.1/users/73235926306843ccb41f288d0464240a", "http_etag": "\"f24ba7ca9d71a7f814dc41d70c48ce947c1324be\""}], "http_etag": "\"e8d5b9f3ce0abbc7bbf51c03c69367f82679f93e\""} I am probably missing something, but this second query seems to confirm that the address "staff(a)example.com" is assigned to the user 73235926306843ccb41f288d0464240a and so shouldn't I should be able to request a password reset for "staff(a)example.com"? I've tried tailing all the log files I can find while attempting the reset and am not seeing any error messages, but I don't know exactly where to look. Thank you for any suggestions for what to try next! Dave

3 4

bounce handling in mm3 available?
by Stefan Bauer Jan. 28, 2022

Jan. 28, 2022

Hi, what happens with bounce-mails that are processed by mailmans postfix instance? Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: to=<company-newsletter-bounces(a)lists.company.tld>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) But the list-owner does not get any notification, nor do i see any bounce-information in the pistorious-gui. How are the bounce-mails handled? Thank you. Stefan

2 4

getting all registered users and their lists
by IOhannes m zmoelnig Jan. 27, 2022

Jan. 27, 2022

hi, TL;DR is there a scriptable way to get all users that have registered in my mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? longer version: we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that this is not the newest version; at this point, please refrain from asking me to upgrade my Debian installation or even to switch to a venv installation of mailman3: i'll eventually do that but right now i've gt a problem to solve :-)) a few weeks ago, we invited a number of people to join a new mailinglist via a link that points to the subscription interface of the list, e.g. <https://lists.example.com/postorious/lists/foo.lists.example.com/> now of course a number of these people had problems with the webinterface, confusing the big "Subscribe" button at the bottom of the page with the much smaller "Sign Up" button in the header (in German this button reads "Registrieren" which has a meaning that is pretty similar to "Subscribe"). people that "Signed up" typically do not understand that they have not been subscribed to any mailinglist (yet), wondering why they do not get any emails. at least this is what we suspect from feedback we got. to fix the situtation, i would like to check which users had this problem (and eventually contact them to explain the problem). for this i would like to get a listing of all users that are not subscribed to any mailinglist. i would also like to query, when a given user has signed up (so i can reduce the number of false positives) how would i do that? ideally i would rather not work on an SQL level. gfdmfas IOhannes

2 3

Inline display of attachments
by Axel Rau Jan. 26, 2022

Jan. 26, 2022

I have turned on HYPERKITTY_RENDER_INLINE_IMAGE and Archive Rendering mode set to Markdown text, but images in JPEG or PDF format are not displayed inline. Should this work or are my expectations to high? Thanks, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

django request error
by tibor.molnar＠waltoninstitute.ie Jan. 26, 2022

Jan. 26, 2022

I recently got postorius web interface stopped with an error, from web log: WARNING 2021-09-29 14:46:47,071 39320 django.request Not Found: /mailman//postorius/lists/ from website: This page either doesn't exist, or it moved somewhere else. I wonder what would be the source of this error / anyone else experienced this error since I haven't changed anything. Regards, Tibor

5 12

Held messages: Long time waiating for response of the Mailman API
by Stephan Krinetzki Jan. 25, 2022

Jan. 25, 2022

Hello, We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? Greetings Stephan

2 3

Re: Hyperkitty 403 Forbidden Error
by Josef Dietl Jan. 23, 2022

Jan. 23, 2022

Dear all, Sorry for coming back to a topic that seems to be done for 18 months now. I'm staring at this issue for a few days now (on and off). But I still get these messages: Jan 19 22:43:27 2022 (149439) HyperKitty failure on https://lists.[...]/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) . and consequently, nothing ends up in the archive. I have checked (among others): - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP address, different orders, '*'. (Asterisk makes a difference, see at the bottom) - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in mailman-hyperkitty.cfg (except for the quotes). According to the editor's color coding, the quotes are "right", too. I have removed special characters to circumvent diverging treatment in different environments - I guess it doesn't matter, but wget --user restadmin --password [.] http://localhost:8001/3.1/lists works, too. - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter I'm running a fresh package installation from Debian Bullseye with certificates from Certbot with nginx, so Certbot may have messed with my nginx config, but even that seems to be OK: Yes, Certbot has inserted http->https redirection, but I'd expect that a https base_url and ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. Mailman info says GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] . REST root url: http://localhost:8001/3.1/ Hyperkitty is 1.3.4, Postorious is 1.3.4, too. To provide all possible information, I'm also adding the nginx log that seems to correspond to that request (no other requests at that time, give or take five minutes): Yes, everything yields 403 response codes. [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . repeated many times, there seems to be quite a few testmessages in the queue . [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=6xpENHLEHQ0kD53vXt5RpKzPDOsKbcN9 HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . again repeated many times . [.] - - [19/Jan/2022:22:46:51 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" I'd appreciate a new idea where I could look for clues. Thanks a lot, Josef

2 3