- Mailman-users - lists.mailman3.org

Error 500 on held_messages page
by Stephan Krinetzki 04 Feb '22

04 Feb '22

Hello all, we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? This is the mailman shell command we used: mailman shell -l listname(a)lists.example.com <removed> Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. Die Variable 'm' ist die listname(a)lists.example.com Mailingliste >>> msg_db = getUtility(IMessageStore) >>> req_db = IListRequests(m) >>> reqs = list(req_db.held_requests) >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... 32598: 1 [...] 107656: 1 107737: 1 107758: 1 >>> from mailman.app.moderator import handle_message >>> handle_message(m, 107758, Action.discard) >>> reqs = list(req_db.held_requests) >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... 32598: 1 [...] 107656: 1 107737: 1 >>> handle_message(m, 92927, Action.discard) Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message key, msgdata = requestdb.get_request(id) TypeError: 'NoneType' object is not iterable >>>

2 4

HELP: mailman send empty mails
by Axel Rau 04 Feb '22

04 Feb '22

In one mailing list all posts are empty, just one sentence: The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. What can I do? I'm lost Axel -- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

Docker mailman 3 and upgrading questions
by bob B 01 Feb '22

01 Feb '22

I am running mailman 3 in docker and trying to figure out -how to upgrade -can you back out. For example I installed docker with a git pull • git clone https://github.com/maxking/docker-mailman docker images shows REPOSITORY TAG IMAGE ID CREATED SIZE maxking/mailman-web 0.3 9ba9d3d7084d 4 months ago 487MB maxking/mailman-core 0.3 26c920c0094b 4 months ago 178MB **** database is hosted via external database I only installed it a few months ago, am I really on 0.3.0 , I assume I am on 3.0 from 2019 and that is what "git clone https://github.com/maxking/docker-mailman" gets???? looking at the release matrix "https://github.com/maxking/docker-mailman/releases?page=2" It looks like the latest releases are 0.4.1 for core & 0.4.2 for web, How do I upgrade, is it a "git pull" or "docker update" command? If something does not work, is there a way to back out? What version should I go to from 0.3? I am thinking it should be v0.3.12 cause that won't break anything? But how do I do that? The documentation at https://asynchronous.in/docker-mailman/. says

2 1

Is there an example of a complete installation for https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-install (ie. standard installation)?
by matt＠fes.org 01 Feb '22

01 Feb '22

What i'm looking for is the directory structure, files, configs of a working mailman3 installation (with passwords/secrets obscured, etc). - /etc/mailman3, /opt/mailman, /etc/nginx, /etc/postfix, etc... I've tried 3 or 4 installations with varying degrees of success. For me, more issues seem related to configuration, not the actual installation. So having an example installation to compare proper configuration (and perhaps file/directory placement) would really help to sanity check what i've installed. Since this installed copy would be created for each release, it would exist at some point. Is it possible this could be made available (with pws/secrets obscured...)? I've seen quite a few threads related to configuration issues...hopefully it would help with those as well.

2 3

National language messages in mm3 notifications
by Ivan Kuznetsov 01 Feb '22

01 Feb '22

Hello There is a problem with moderator/administrator notifications used national (non-acsii) characters in templates. Messages came with all non-ascii chars changed to '?' As I can see some parts of customizable text are originated from localized messages (mailman/messages/<country code>/LC_MESSAGES), other from site/domain/list templates. I made some localization/translation of LS_MESSAGES for Russian language via Weblate site and import .po file to test site setup. Web interface messages seems to be ok but email notifications are not. Content-type: and Content-Transfer-Encoding: headers are not suitable for national charsets. Mailman processes has enviroment variable LANG set to ru_RU.UTF-8. Preferred language for site administrator (listmaster) is Russian What am I missing in setup? Return-Path: <test-bounces(a)solvo.ru> [...] Received: from mail-g3-vlan10 (localhost [IPv6:::1]) by mail-g3 (Postfix) with ESMTP id 889784800512D for <kia(a)solvo.ru>; Tue, 18 Jan 2022 00:00:22 +0300 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ????????? ????????????? ???????? ? ?????? ???????? test(a)solvo.ru: 1. From: listmaster(a)solvo.ru To: =?utf-8?b?0JjQstCw0L0g0JrRg9C30L3QtdGG0L7Qsg==?= <kia(a)solvo.ru> Message-ID: <164245320388.3361727.10723274392705308145@mail-g3-vlan10> Date: Tue, 18 Jan 2022 00:00:03 +0300 Precedence: bulk X-Mailman-Version: 3.3.5 List-Id: =?utf-8?b?0KLQtdGB0YLQvtCy0YvQuSDRgdC/0LjRgdC+0Lo=?= <test.solvo.ru> List-Help: <mailto:test-request@solvo.ru?subject=help> List-Owner: <mailto:test-owner@solvo.ru> List-Subscribe: <mailto:test-join@solvo.ru> List-Unsubscribe: <mailto:test-leave@solvo.ru> [...] The test(a)solvo.ru list has 1 moderation requests waiting. ????????? ????????? ????????: ????????????: ikuznetsov(a)solvo.ru Please attend to this at your earliest convenience.

2 3

No resend after delivery bouned
by Axel Rau 31 Jan '22

31 Jan '22

My listserver has been blocked with 550 and I received bounce score on <list_add> has been incremented. notifications. After resolving the block issue, I'm now waiting for mailman to resend the mails. Now, after 3 hours, nothing has happened so far. What is wrong here? Axel -- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

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

31 Jan '22

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 31 Jan '22

31 Jan '22

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 29 Jan '22

29 Jan '22

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 28 Jan '22

28 Jan '22

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