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

Thanks to this very helpful community!
by Stephen Daniel Feb. 18, 2022

Feb. 18, 2022

All -- I want to express my heartfelt thanks to the people on this list who helped me stand up a modest mailman3 server. As of today I have 3 lists with a total of ~150 users running in production on a small VM in google's cloud. This implementation replaces a venerable mailman2 implementation running on servers that are to be decommissioned at some point in the near future. Thanks again! -- Stephen

1 0

FILTER_VHOST = True doesn't work fine with alias_domain
by Élodie BOSSIER Feb. 18, 2022

Feb. 18, 2022

Hello, My mailman3 installation is now functional, but the config "FILTER_VHOST = True" doesn't work fine when I define "alias_domain" for the 2 domains. I need to define that because I need to get "postfix_vmap" file. As you can see, list from others domains are visible on this URL : https://ml.franceserv.fr/postorius/lists/ I would like https://ml.franceserv.fr/postorius/lists/ and https://ml.viticreation.fr/postorius/lists/ with their own lists. Where I should check please to solve this ? Thank you in advance.

2 5

Mailman3-web/Postorius behind Lighttpd
by Élodie BOSSIER Feb. 18, 2022

Feb. 18, 2022

Hi, I'm using Mailman 3.3.3 (Tom Sawyer) on Debian Bullseye 11.2 from packages : #dpkg -l | grep mailman ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty ii python3-mailmanclient 3.3.2-1 all Python bindings for Mailman3 REST API (Python 3 version) I can access from localhost to http://127.0.0.1:8000/ which move me correctly to http://127.0.0.1:8000/postorius/lists/ and all seem to be correct. But 127.0.0.1:8000 listen only in localhost : #netstat -tanpu | grep 8000 tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 626175/python3 So I try to use my lighttpd as proxy as recommanded with this config : > scgi.protocol = "uwsgi" > scgi.server = ( > "/" => (( "host" => "127.0.0.1", "port" => 8000, "check-local" => > "disable" )), > ) but it's return me a "502 Bad Gateway". I see nothing on there logs : - /var/log/lighttpd/error.log - /var/log/mailman3/web/error.log - /var/log/mailman3/web/access.log But on the file : /var/log/mailman3/web/mailman-web.log I can see that : > QUERY_STRING > REQUEST_URI/postorius/lists/REDIRECT_STATUS200 > SCRIPT_NAME" 400 - I don't know what I'm doing wrong ... There is a way to solve it with lighttpd or bind the port 8000 to 0.0.0.0 instead 127.0.0.1 (which is not recommanded) ? Thank you in advance. Best regards, Elodie

2 2

High memory usage
by Prasanth Nair Feb. 18, 2022

Feb. 18, 2022

Hi, We are having an issue with high memory usage on our Mailman3 server. Initially, our server had 16GB RAM and the memory usage went up from 5% to 92% within a week. So, we increased the memory capacity to 32GB RAM and we can see that the memory usage is going up in the same pattern. Any idea why it is happening? or any suggestions? Kind regards, Prasanth Nair

5 10

Template Ignored?
by Stephen Daniel Feb. 17, 2022

Feb. 17, 2022

Mailman3 people -- I created a new list, and used postorius to create a template for " list:user:notice:welcome". I then used the mass subscription feature to add myself to the list, having checked "pre-confirmed", "pre-approved", and "pre-verified". I received a welcome message that appears to be the default welcome message. It certainly wasn't what I put into my template. Any suggestions on how I get mailman to use my template? Things I might be doing wrong? Thanks! -- Steve

2 5

changing the main template for subscriptions and more
by Jens Günther Feb. 15, 2022

Feb. 15, 2022

Hey there, in Mailman2 there was a simple link in the moderation-emails, with which I was able to open directly the "held-messages". I know how to manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) But: How can I change the template for all the lists (respectively maildomains/webdomains) so that I don't have to do this manually for all lists? I searched a bit for the corresponding template, but didn't find it. At the end it only says the following: "At your convenience, visit your dashboard to approve or deny the request." -> here I would like to add the following: "At your convenience, visit your dashboard to approve or deny the request: https://$domain/postorius/lists/$short_listname.$domain/held_messages" Or if someone sees another possibility to get us on the right track, it would be more than welcome, thank you! Kind regards, Jens.

4 7

Help with mailman user and mailman Web users
by Sherin Feb. 15, 2022

Feb. 15, 2022

Hi, I have installed mailman3 server and configured MailmanWeb ( hyperkity + Postorious ) . The service and everything works fine, but I am little bit confuses with the user management in mailman3, 1) I created an owner user for a mailing list using the mailmanclient api tools, # from mailmanclient.client import Client 2) I can't login to the Mailmanweb with this user For further investigation shows the mailman have its own database and the web frontend have its own database too. So my question is how to configure the webfrontend ( hyperkit+ postorious ) to use the accounts logins created from the mailmanclient api from the mailman core database. Or is there a way to use only one user management system ? Any help will be appreciated. -- Sherin

2 1

converting bulk accept_these_nonmembers in migration from mailman 2 to 3
by Lucio Chiappetti Feb. 12, 2022

Feb. 12, 2022

I have been instructed by Mark Sapiro to subscribe to this list to post questions related to mailman3. On Mon, 31 Jan 2022, Mark Sapiro wrote: > On 1/31/22 06:20, Lucio Chiappetti wrote: >> One of the lists of which I am a co-moderator has been moved from >> mailman 2 to 3. Actually the migration has been made operative yesterday (and so we got the first problems ...). Basic background. There are a number of lists within my institution (a nationwide research institution with many seats across our country), some are institutional (all staff subscribed ex officio) and managed by staff in one seat, some other are non-institutional (subscription is optional) and are managed by a few volunteers in other cities different from the seat where the mailman server runs. > In particular, the list settings for *_these_nonmembers are at Settings > -> Message Acceptance, but these settings in particular are deprecated > in Mailman 3 except for regexps. In Mailman 3 the preferred way to say > accept a nonmember is to create a nonmember for that user and set it's > Moderation action to Default Processing. If, a nonmember posts, the > nonmember record is automatically created, Let me explain our case, and how it was managed in mailman2. - originally our staff (of the order of 1000) had addresses like user(a)place.inaf.it or user(a)place.astro.it. Some had even two (say place1.inaf.it and place2.inaf.it), so they subscribed with ONE of their work addresses - later we got addresses like name.surname(a)inaf.it. New users subscribe with this address but MANY of the old ones continue to use the PREVIOUS address. - we implemented a spam filtering policy as follows: - staff (and former staff) can SUBSCRIBE with any address or CHANGE their address. Any subscribed address will be recognised. Mail is NOT held in moderation unless too bulky, or has undisclosed recipients - mail from non members with any address in the .it TLD or in the tng.iac.es domain (where some of our staff work) goes into moderation (this is achieved via regexp in hold_these_nonmembers) - anything else is silently discarded as spam (generic_nonmember_action = discard) - when some staff posts from a non-subscribed address (be it the home address, or one of the alternate addresses described above) it therefore goes into moderation because of hold_these_nonmembers - in mailman2 we could let them pass "manually" (if we recognised the person) or (in case they used an alternate address) tick to add them permanently to accept_these_nonmembers (in one tick) - at the end we got somehow fed up of this but we did NOT want to accept any address of the form ^.+@.+\.inaf.it (which could be forged) but found that we could simply put in accept_these_nonmembers two entries like @list1 @list2 where list1 and list2 are two institutional lists on the same server which contain all permanent and temporary staff or assimilated with their official address (these lists are automagically generated each week) (so at least any VALID EXISTING official address is accepted) What I found now (after the migration done by the administrators of the central seat) is that in mailman3: - accept_these_nonmembers is empty - there are 189 entries listed in Non-members (which look those formerly in accept_these_nonmembers) - hold_these_nonmembers was copied identical with the same regexp's as in mailman2 - I have inspected a few of them and found that they have Administration options Moderation set to List default - the effect of this apparently was that a post from some.guy(a)inaf.it (whose subscription address is guy(a)somewhere.inaf.it) was hold for moderation is this due to a loop with the regexp in hold_these_nonmembers ? the default action would be to let it pass Or should we set Administration options Moderation to Accept immediately ? - if so, how can we do it automatically for all 189 entries ? - or move back the 189 addresses to accept_these_nonmembers ? - or for the future have persons posting with alternate addrresses accepted for the future WITH ONE CLICk ? - AND LAST BUT NOT LEAST would the syntax @list1 in accept_these_nonmembers work in mailman3 ? already putting it back will save a lot of work. Many thanks -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ "All that is google does not glitter Nor all who use alpine/procmail are lost"

2 3

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