- Mailman-users - lists.mailman3.org

moderation notices for list-owner being redirected to mailman address
by Philippe B Feb. 10, 2022

Feb. 10, 2022

We have seen a very strange behavior on 2 separate occasions/lists over the past month. A SENDER(a)SOME.DOMAIN emails OURLIST(a)OUR.DOMAIN, and that post is (correctly) held for moderation. The moderation notification is sent by OURLIST-owner(a)OUR.DOMAIN to OURLIST-owner(a)OUR.DOMAIN, and everything works fine. But in a few very rare cases, at some point during the convoluted delivery path to the mailbox of the actual human owner of OURLIST, the recipient is changed from OURLIST-owner(a)OUR.DOMAIN to mailman(a)OUR.DOMAIN. I am going to paste full headers below (with fake public IPs), but I think that these 2 particular lines highlight the problem: X-MailFrom: OURLIST-bounces+OURLIST-owner=OUR.DOMAIN(a)OUR.DOMAIN X-MailFrom: OURLIST-bounces+mailman=OUR.DOMAIN(a)OUR.DOMAIN because only the first one is present normally. We know from the headers that the recipient gets changed on the Mailman host, but we have no idea why or how, because all the aliases are set up correctly, and there is no connection between OURLIST's (non-)members/etc and mailman(a)OUR.DOMAIN. Do you have any troubleshooting suggestions? Thanks. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Note: ec2-12-34-56-78.us-west-2.compute.amazonaws.com, lists.OUR.DOMAIN, and MAILMAN-SERVER.OUR.DOMAIN are different ways of addressing essentially the same system. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Received: from SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [6.7.8.9]) by MAILMAN-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 2B6E51A288F for <mailman(a)lists.OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:52 -0800 (PST) Received: by SMTP-SERVER.OUR.DOMAIN (Postfix) id E825C207053B; Tue, 1 Feb 2022 07:10:51 -0800 (PST) Delivered-To: mailman(a)OUR.DOMAIN Received: from SMTP-SERVER.OUR.DOMAIN (localhost [127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id D468B2070A45 for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) X-Spam-Scanned: at OUR-ORGANIZATION on SMTP-SERVER.OUR.DOMAIN by amavisd-new Authentication-Results: SMTP-SERVER.OUR.DOMAIN (amavisd-new); dkim=pass (1024-bit key) header.d=OUR.DOMAIN header.b="********"; dkim=pass (1024-bit key) header.d=OUR.DOMAIN header.b="********" Received: from filter-send ([127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [127.0.0.1]) (amavisd-new, port 12345) with LMTP id YgQELyXHaR1X for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) Received: from [172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 9E8DE207053B for <mailman(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:51 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 SMTP-SERVER.OUR.DOMAIN 9E8DE207053B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OUR.DOMAIN; s=unixmail; t=**********; bh=*******************************************=; h=Subject:From:To:Date:List-Id:List-Help:List-Owner:List-Subscribe: List-Unsubscribe:From; b=***************************************************************** ****************************************************************** ****************************************= Received: from SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [6.7.8.9]) by MAILMAN-SERVER.OUR.DOMAIN (Postfix) with ESMTP id B138C1A288F for <OURLIST-owner(a)lists.OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) Received: by SMTP-SERVER.OUR.DOMAIN (Postfix) id 7766E207053B; Tue, 1 Feb 2022 07:10:49 -0800 (PST) Delivered-To: OURLIST-owner(a)OUR.DOMAIN Received: from SMTP-SERVER.OUR.DOMAIN (localhost [127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 676682070A73 for <OURLIST-owner(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) X-Spam-Scanned: at OUR-ORGANIZATION on SMTP-SERVER.OUR.DOMAIN by amavisd-new Received: from filter-send ([127.0.0.1]) by SMTP-SERVER.OUR.DOMAIN (SMTP-SERVER.OUR.DOMAIN [127.0.0.1]) (amavisd-new, port 12345) with LMTP id j2xEFERoaVLS for <OURLIST-owner(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) Received: from [172.17.0.2] (ec2-12-34-56-78.us-west-2.compute.amazonaws.com [12.34.56.78]) by SMTP-SERVER.OUR.DOMAIN (Postfix) with ESMTP id 2C264207053B for <OURLIST-owner(a)OUR.DOMAIN>; Tue, 1 Feb 2022 07:10:49 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 SMTP-SERVER.OUR.DOMAIN 2C264207053B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=OUR.DOMAIN; s=unixmail; t=**********; bh=*******************************************=; h=Subject:From:To:Date:List-Id:List-Help:List-Owner:List-Subscribe: List-Unsubscribe:From; b=***************************************************************** ****************************************************************** ****************************************= Subject: OURLIST(a)OUR.DOMAIN post from SENDER(a)SOME.DOMAIN requires approval From: OURLIST-owner(a)OUR.DOMAIN To: OURLIST-owner(a)OUR.DOMAIN MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6658935924254827098==" Message-ID: <164372824697.288.9427163605184740636@MAILMAN-SERVER> Date: Tue, 01 Feb 2022 07:10:46 -0800 Precedence: bulk X-Mailman-Version: 3.3.5 List-Id: <OURLIST.OUR.DOMAIN> List-Help: <mailto:OURLIST-request@OUR.DOMAIN?subject=help> List-Owner: <mailto:OURLIST-owner@OUR.DOMAIN> List-Subscribe: <mailto:OURLIST-join@OUR.DOMAIN> List-Unsubscribe: <mailto:OURLIST-leave@OUR.DOMAIN> X-MailFrom: OURLIST-bounces+OURLIST-owner=OUR.DOMAIN(a)OUR.DOMAIN X-MailFrom: OURLIST-bounces+mailman=OUR.DOMAIN(a)OUR.DOMAIN X-Mailman-Rule-Hits: implicit-dest X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mailman.OUR.DOMAIN-0; nonmember-moderation; administrivia; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header

3 13

Customise Postorius templates?
by Duane Raymond Feb. 8, 2022

Feb. 8, 2022

Hi, I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html to var/templates/lists/summary.html As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!)

5 10

Time Zone Issue in Postorius
by Andy Summers Feb. 8, 2022

Feb. 8, 2022

Hello, I'm encountering an error that sounds similar to this previous thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I've tried setting my TIME_ZONE to 'UTC' in my settings.py and settings_local.py files (and restarting Mailman), but when I check the datetime for a held message in Postorius, the datetime seems to be pushed +8 hours unexpectedly. My Postorius account time zone is set to "US/Pacific". As a workaround, I might be able to find a "wrong" time zone that would possibly reduce the unintentional additional hours difference and show the "correct" time zone in Postorius for the "Held Messages" page, but I don't think this is the right way to fix the issue. I think I've tried setting the TIME_ZONE setting to "America/Los_Angeles" in my settings.py file in place of 'UTC' in the past, but the result was still different than expected. Does anyone know if there are other places besides the mailman settings.py and settings_local.py files where something needs to be set so that I don't get an unintentional extra +8 hours of time difference when looking at messages on the "Held Messages" page of a mailing list? Thank you, Andrew

5 5

Error 500 on held_messages page
by Stephan Krinetzki Feb. 4, 2022

Feb. 4, 2022

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 Feb. 4, 2022

Feb. 4, 2022

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 Feb. 1, 2022

Feb. 1, 2022

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 Feb. 1, 2022

Feb. 1, 2022

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 Feb. 1, 2022

Feb. 1, 2022

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 Jan. 31, 2022

Jan. 31, 2022

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 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