- Mailman-users - lists.mailman3.org

Footer question...
by David Partain 27 Jul '21

27 Jul '21

Hi, Background: I have a painful mailman3 installation based on ubuntu 18.04 packages, a mistake I regret but have to live with until I can finish a fresh install of the latest. Currently running on mailman 3.1.1-9 and python-django-mailman3 version 1.1.0-4 (if that matters). I migrated > 1200 lists from an old mailman2 installation. That brought along all of the footers (naturally), and now I'm trying to get rid of them but failing miserably. I've spent a fair bit of time reading archives of this list, but I'm still stuck. Here's what's configured... In /etc/mailman3/mailman.cfg: -------------------------------------------------------------------------------------------------------------------------- var_dir: /var/lib/mailman3 # Root directory for site-specific template override files. template_dir: $var_dir/templates -------------------------------------------------------------------------------------------------------------------------- In that directory, list-specific directories like: /var/lib/mailman3/templates/lists/list.mydomain/ and, as an example, en/list_member_digest_footer.txt For the migrated lists, that might have: ------------------------------------------------------------------------------------------------------------------------- _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} ------------------------------------------------------------------------------------------------------------------------ Based on what I've read elsewhere, my first attempt was to create an empty file doing 'cp /dev/null list_member_digest_footer.txt' to replace the one installed in migration. That had no effect. As a shot-in-the-dark, I did 'cp /dev/null list:member:regular:footer.txt' to see if that might have some effect. Nope. I suppose some decision is made earlier in the process to tack on the footer, so these files I'm manipulating have zero effect. Anyone have suggestions of what I can do? Thanks in advance. David

2 1

requiring questionnaire from new users
by Ethan Furman 27 Jul '21

27 Jul '21

Greetings! Is there a way to require new users to answer a questionnaire when they subscribe? I suspect that one of the lists I manage is getting a lot of subscribers who don't understand what that particular list is for, and having to answer a question or two would allow me to direct them to better resources. Any and all info appreciated! -- ~Ethan~

2 1

non-members issue with held email
by Lars Schimmer 20 Jul '21

20 Jul '21

Hi I want to check a issue with a few mailing lists of us. We do run mailman3 on debian with debian package 3.2.1-1 (not yet updated for backup reasons). We created a new mailinglist, added 3 owner and several members. Now we want some email addresses to post to that list but not receive mails from the list. So I added those to the "non-member" area of the mailinglist and checked every non-member to "acceppt at once". But on a test, a email address, which is owner AND non-member, cannot send to mailinglist, always get a "HOLD: ...... The message is not from a list member" The Email address in that HOLD log entry is the same as in the owner/non-member list. Any idea howto check the mailman3 logs for this case? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 1

Deleting default "example.com" domain breaks everything
by mcarter＠corneredrats.com 18 Jul '21

18 Jul '21

Hello. I'm new with v3 of mailman. Installed via aptitude on deb10. After I logged in as admin, I created my actual domain, as "example.com" was there by default. I then deleted example.com, and everything broke. The only site I had was still using example.com. How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? Thanks.

3 2

Debian10 pkg install: set up Postorius superuser?
by mcarter＠corneredrats.com 16 Jul '21

16 Jul '21

Hey, all. I've installed mailman3 to replace mailman2 from the Deb10 package mailman3-full. Command line appears to work, but I had to manually add the Uwsgi module to get the user web site to run. I can't find a reference to what the default admin user password is, and running "python settings.py createsuperuser" doesn't work with error: root@mail:/usr/share/mailman3-web# python manage.py createsuperuser Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management Any idea what else needs to get installed that the aptitude package missed? Any way to just manually set the admin's password without having to install anything else?

1 1

Problems with hyperkitty
by Lucia Moreno 15 Jul '21

15 Jul '21

Dear mailman support, We have an issue with hyperkitty. In the last month the space used by hyperkitty_email postgres table has increased from 54GB to 400GB and it is constantly increasing with no end. Is there any simple way of knowing what is taking so much space? Like for example display how much archiving space (or achived emails) is used by each mailing list? Looks like a mailing list has gone crazy but from the logs everything looks fine. Any help is very much appreciated. THanks a lot for your precious help!!

2 1

[MM3-users]Is it possible to grant all users the ability to Create List
by Carrie Knox 13 Jul '21

13 Jul '21

Hello, Our company is evaluating mailman3 as an option for company internal list serving. One of the requirements is that anyone with access to the list server be allowed to create and manage lists. Is this possible? If so, how? Is there a "create list" role that can be added for all registered users? Thanks

5 5

accept mails from several Users, not list members beside members, howto
by Lars Schimmer 13 Jul '21

13 Jul '21

Hi I do look out for a method to accept mails from list members and a number of 20-30 Email addresses (not list members) to a mailing list. All others should be denied to post to the list. I can add those as non-members, but AFAIK I cannot define a special rule for them in "message acceptance". Under "message acceptance" the line "non-members" is set to deny, but if I set it to "default procesessing" - will it allow ALL email addresses, or just the group of "non-member" users? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 3

cache files?
by Dave McGuire 13 Jul '21

13 Jul '21

Hi folks. I'm seeing quite a few .css files, thousands of them totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. Some of them date back to when I set up the mm3 instance a few years ago. Is this expected, or am I missing a cron job or something to clean them up? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 3

Trying basic install of mailman3 in docker, but how do you set allowed hosts?
by bob B 12 Jul '21

12 Jul '21

I am starting small, My goal is just to get mailman3 running in docker and test the website access via curl from the host, then I will move on from there In the docker instructions it says SERVE_FROM_DOMAIN: The domain name from which Django will be served. To be added to ALLOWED_HOSTS in django settings. Default value is not set. This also replaces Django's default example.com SITE and becomes the default SITE (with SITE_ID=1). But where do I set the ALLOWED_HOSTS I added this to the yaml file - ALLOWED_HOSTS=127.0.0.1 under environments mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - ALLOWED_HOSTS=127.0.0.1 - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - SECRET_KEY=333blah-blah-secret - HYPERKITTY_API_KEY=333someapikey ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: But when I try: [docker-mailman]# curl 127.0.0.1:8000 <h1>Bad Request (400)</h1>[root@bmimailmandr1 docker-mailman]# [root@bmimailmandr1 docker-mailman]# I see this in the logs [docker-mailman]# cat /opt/mailman/web/logs/mailmanweb.log WARNING 2021-07-08 17:40:46,979 1642 django.request Bad Request: / ERROR 2021-07-08 19:20:58,416 1641 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: /

2 1

Help! List traffic shunted to gmail/yahoo spam folders
by Matt Wilbur EFS 12 Jul '21

12 Jul '21

Hello, I've been through DKIM hell and back. Now I'm to the point where when I "show original" mail with gmail it says SPF, DKIM and DMARC all pass, but it's still going to the spam folders. Has anyone sorted this? thanks! matt ----- show original: Delivered-To: somebody(a)gmail.com Received: by 2002:a02:968f:0:0:0:0:0 with SMTP id w15csp1521828jai; Sat, 10 Jul 2021 14:33:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy72rM7rrvKmz7wlOVjj2M02l971IurhWQqYjQlhjZNhtJ1m7uph2Y/p85GAtq4x56KMLi4 X-Received: by 2002:a05:6830:270b:: with SMTP id j11mr3612659otu.352.1625952812813; Sat, 10 Jul 2021 14:33:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625952812; cv=none; d=google.com; s=arc-20160816; b=LSNHINAAV62ePpOJ85HzOKFKSRBzP4htN0SkBgG3HnZp7eVAUY7td/ibOWIsVDy0Iz AcAK6WoRhDKhHmlnx71LAo3COnbmD5TWGle/Kp8cx2tMS5bxRXw+Rb5FZYblTPIiwyFo 7u7zXTTxKCzbyCQgAmpvsQN55N41TRq1je6dTMdo1j4T6msO5pvLzfnJRT3Oo+ZP3sYY K3lOEEl1MNFcmVTxsHY73tdNMncq5TTLGdqdYvT+GDd5a6QnjrkWQvhk783kppNB6kFC dgiXst5Ql/jUbe4NnS1T+i/md+WcXTitmryEtY8lxzCjEnT6NFA5IcHw/tChpH4OqyPv MGIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:reply-to:from:list-unsubscribe :list-subscribe:list-post:list-help:list-archive:archived-at:list-id :subject:precedence:message-id-hash:content-language:mime-version :user-agent:date:message-id:to:dkim-signature:dmarc-filter :dkim-signature; bh=4HN4XCD73340TTta47Nw8NNNFEbWsNLm9zWdectMYcI=; b=K3ANa/+WBrM8ChcoYKIUkoRZ3sgDZB77S3BRFFu2WZCOBA5pGlG176jCzA1hOz7b+6 1ewP/Imzh16yBVGzugL+/JQZJlCWV1F5S6jq8xeoQIPbkM2JGKIUFAS9+Sk+JNKDTMl4 nMTFiDVfTMkgK6f1guKxBhqHroJKJ4eAUwxjHcX17nZwvY5SOeP0UqnyQaGmeRnJuXel fcdBoY5TqnDMxq7709anmcYRQuIahso/UPjzZrdMsrTJaRhScAxfa0ZQOVnjf4bkyf0D 1/eLCHEl+oZlzNXT06ghOzPFC91g/TxComGBLRWc1G5nk92gqBPrQh9690sbOuqmHZA8 ybPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=(a)sditdg.org header.s=mail header.b=BteyCkCY; dkim=neutral (body hash did not verify) header.i=(a)gmail.com header.s=20161025 header.b="Kt/xXWZE"; spf=pass (google.com: domain of testing-bounces(a)sditdg.org designates 65.50.252.27 as permitted sender) smtp.mailfrom=testing-bounces(a)sditdg.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sditdg.org Return-Path: <testing-bounces(a)sditdg.org> Received: from sditdg.org ([65.50.252.27]) by mx.google.com with ESMTPS id w3si10563091oiv.8.2021.07.10.14.33.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 10 Jul 2021 14:33:32 -0700 (PDT) Received-SPF: pass (google.com: domain of testing-bounces(a)sditdg.org designates 65.50.252.27 as permitted sender) client-ip=65.50.252.27; Authentication-Results: mx.google.com; dkim=pass header.i=(a)sditdg.org header.s=mail header.b=BteyCkCY; dkim=neutral (body hash did not verify) header.i=(a)gmail.com header.s=20161025 header.b="Kt/xXWZE"; spf=pass (google.com: domain of testing-bounces(a)sditdg.org designates 65.50.252.27 as permitted sender) smtp.mailfrom=testing-bounces(a)sditdg.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=sditdg.org Received: from sditdg.org (localhost [127.0.0.1]) by sditdg.org (Postfix) with ESMTP id 9079DC1DF0; Sat, 10 Jul 2021 14:33:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sditdg.org; s=mail; t=1625952811; bh=4HN4XCD73340TTta47Nw8NNNFEbWsNLm9zWdectMYcI=; h=To:Date:Subject:List-Id:List-Archive:List-Help:List-Post: List-Subscribe:List-Unsubscribe:From:Reply-To:From; b=BteyCkCYE4gLRLEUV+nsoK7PM5Ayj0ce+ZgWkUdqtbwQynND4zs1PLPwebsALsP5k NYVnZLBJGHoXOA256v+imGl4BD8IFXe1onyY6VSKcJfx/2vYwfwwnDyB3zkc9s9BYO K0B4EPVOepbjClhUg5Z5JnOSyZhoIWjQHZwFsXpY+di5B2y5sDMvDyWLJHh3GGhw8y zijl2IJZDCaF3iVq4EFlxP4UfHvQ+bmfkGGmjYVJvkmsQWAsTFUb7UawK3w3m9Z6LN W+hV9H3L+95O+CIfUz0q7kG7T5gwz/eoce9ewv7xhimpVPjuatgLt4hFJcvzwaohmp S/u54SwGh0iVA== Received: from cat.efs.org (cat.efs.org [10.128.128.46]) by sditdg.org (Postfix) with ESMTPS id 0D110C1DF0 for <testing(a)sditdg.org>; Sat, 10 Jul 2021 14:33:29 -0700 (PDT) X-Spam-Status: No Authentication-Results: cat.efs.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=(a)gmail.com header.b="Kt/xXWZE" X-EFS-MailScanner-EFA-Watermark: 1626557599.13472@k3T7MnvZ29zIPokD4fCFrg X-EFS-MailScanner-EFA-From: somebody-else(a)gmail.com X-EFS-MailScanner-EFA: Found to be clean X-EFS-MailScanner-EFA-ID: 4GMjtw2R5xzYrqBb X-EFS-MailScanner-EFA-Information: Please contact matt(a)efs.org for more information Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (no client certificate requested) by cat.efs.org (MailScanner Milter) with SMTP id 4GMjtw2R5xzYrqBb for <testing(a)sditdg.org>; Sat, 10 Jul 2021 14:33:12 -0700 (PDT) DMARC-Filter: OpenDMARC Filter v1.4.1 cat.efs.org 4GMjtw2R5xzYrqBb Authentication-Results: cat.efs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: cat.efs.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pl1-f180.google.com with SMTP id v14so9940plg.9 for <testing(a)sditdg.org>; Sat, 10 Jul 2021 14:33:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=; b=Kt/xXWZEIVQlTx1hyx4VeQlW8OZc+z5Uxz8vkIaQJkK5PhHmc6/0safN0MGVJcXoBe ii3/LXmMTkbbZEztKBdVIV5TI8ZqvMOS2uvJk//lFVgq/AbcKOGcrNTfg7tTpfL7knQY 79CWtAE/etBKni0pONNORAevyCQq07YwJRFvSuZDEB2mWnk+SxQpkudgEX6ngXtNKqiW OroAx3fTcEO/tEQEVCKCdJAOSi5T1gmk/nTonU1zpmw+LJTOBcgCYZu4ppIwsss1eRbH TgaZO8yhoHztSP8MCjF2fwG5GYdcgYtI1Scq8XQVVe9f7mdrOU1NMDT6+8fiZltvSg0y KaUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=; b=Jdlw1Ajc3T80d9gzMNci+0GYQ1vI7B1AzIc+4qv4t/x57S1l6PkmwmtiDV9HqJIVcA wUE9Fuih0yFJHMRwSQX/nsPLIKwmC4HO34V3Diy0NltMDSTBQFjTJ8xJY6kSmX8IXSN5 fBBvQkS9AjQbLZUm7a4ttfK6o4A5gBKSaj60I7+sc5hUxCLK+hEcb7F1pnD0AoE2/Zlz nLfyg2FNA+/BclTgRI7kgjY0+ro67BdU4KS3/E5ltSngLRSMijouKzAp9ITzzms1pBKT OkFPwRPQ3PBzcBPGF4SrQK7pcUKhdsmua7upMia3pOBjh/HvC9aUgsGUsj+T5xqOe0xU ANcA== X-Gm-Message-State: AOAM531v1T1CpYQn1gzRqHpER9tizVVsXfwKmSdvQBkSgRi3IBxptEIl Vhgt9h0ndeYsYoGUJOo+P1ttSeVVslSmlA== X-Received: by 2002:a17:90b:798:: with SMTP id l24mr46030558pjz.141.1625952789010; Sat, 10 Jul 2021 14:33:09 -0700 (PDT) Received: from [192.168.86.248] (cpe-76-93-161-126.san.res.rr.com. [76.93.161.126]) by smtp.gmail.com with ESMTPSA id d2sm8574671pjo.50.2021.07.10.14.33.08 for <testing(a)sditdg.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 10 Jul 2021 14:33:08 -0700 (PDT) To: testing(a)sditdg.org Message-ID: <fb1474b0-27d5-65ed-26b2-1753b95994c0(a)gmail.com> Date: Sat, 10 Jul 2021 14:33:07 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 Content-Language: en-US Message-ID-Hash: ZY5T327H5SEXWCMGQQMQCDSJ6IYBLNHA X-Message-ID-Hash: ZY5T327H5SEXWCMGQQMQCDSJ6IYBLNHA X-MailFrom: somebody-else(a)gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.2 Precedence: list Subject: [Testing] test List-Id: <testing.sditdg.org> Archived-At: <https://sditdg.org/mailman3/hyperkitty/list/testing@sditdg.org/message/ZY5T…> List-Archive: <https://sditdg.org/mailman3/hyperkitty/list/testing@sditdg.org/> List-Help: <mailto:testing-request@sditdg.org?subject=help> List-Post: <mailto:testing@sditdg.org> List-Subscribe: <mailto:testing-join@sditdg.org> List-Unsubscribe: <mailto:testing-leave@sditdg.org> From: Matt Wilbur gmail via Testing <testing(a)sditdg.org> Reply-To: Matt Wilbur gmail <somebody-else(a)gmail.com> Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit test _______________________________________________ Testing mailing list -- testing(a)sditdg.org To unsubscribe send an email to testing-leave(a)sditdg.org

3 4

List rename
by Joel Lord 07 Jul '21

07 Jul '21

I'm in an odd situation where I need to rename a bunch of lists. They were all created on mailman2 originally and migrated to mailman3 (very successfully, TYVM) but the names were all originally discuss-<foo>@domain and it's very confusing to be sure you're always sending to the correct <foo>. We want to completely rename the lists to <foo>-discuss@domain. These lists do not keep archives, so if I have to resort to extracting the subscriber lists and the configs and building new lists, I'm completely fine with that. Problem is, I'm really used to MM2 and config_list and could do this without thinking using those tools... that I don't have. Running MM3 3.2.2 trying to make this happen. Any assistance I could get will be greatly appreciated. THANKS! -- Joel Lord Web Administrator, Alpha Psi Omega Grand Cast etc... etc... etc...

5 6

Mailman3 in docker help
by bader＠cchmc.org 07 Jul '21

07 Jul '21

Trying to get mailman3 stood up in Docker and having some issues following the instructions. Currently my docker-web image is not running. Today it won't start, yesterday it was exiting with 0 status immediately. [root@mailman3dockerhost docker-mailman]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0d7e6be7cf80 maxking/mailman-core:0.3 "docker-entrypoint.s…" 18 hours ago Up 3 seconds 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core d1071c541bda postgres:9.6-alpine "docker-entrypoint.s…" 18 hours ago Up 7 seconds 5432/tcp dockermailman_database_1 [root@mailman3dockerhostdocker-mailman]# For my .yaml file I added in the " - ALLOWED_HOSTS=['*',]" in mailman-web thinking that was the issue. I am also not sure about networks, I have ports setup but no IP's i.e ---------------------------- ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: ---------------------------- but some examples I have come across have IPs, but no ports listed ---------------------------- networks: mailman: ipv4_address: 172.19.199.2 ---------------------------- I thought access to the container's are from the Docker's Host machines IP and the port I specify in the .yaml file. Also I am running the docker as root, just to test, but what is the best practice for running the mailman containers? ---------- here is my yaml file with some bits removed for security [root@host docker-mailman]# cat docker-compose.yaml version: '2' services: mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core volumes: - /opt/mailman/core:/opt/mailman/ stop_grace_period: 30s links: - database:database depends_on: - database environment: - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - DATABASE_TYPE=postgres - DATABASE_CLASS=mailman.database.postgresql.PostgreSQLDatabase - HYPERKITTY_API_KEY=********* ports: - "127.0.0.1:8001:8001" # API - "127.0.0.1:8024:8024" # LMTP - incoming emails networks: mailman: mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - ALLOWED_HOSTS=['*',] - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - HYPERKITTY_API_KEY=********* - DEBUG=TRUE - SECRET_KEY=********* - SERVE_FROM_DOMAIN=domain.hostname.org - MAILMAN_ADMIN_USER=lists - MAILMAN_ADMIN_EMAIL=admin(a)domain.hostname.org ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: database: environment: - POSTGRES_DB=mailmandb - POSTGRES_USER=mailman - POSTGRES_PASSWORD=******* image: postgres:9.6-alpine volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: networks: mailman:

1 0

Re: Editing a Subscriber's Mailman 3 list Settings
by Mark Sapiro 01 Jul '21

01 Jul '21

On 7/1/21 12:28 PM, Terry Earley wrote: > Postorius Version 1.1.2 Which was released in December, 2017. I don't offhand know which version fixed it, but I'm sure it's been fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Editing a Subscriber's Mailman 3 list Settings
by Terry Earley 01 Jul '21

01 Jul '21

Admin users can edit subscriber's Mailman list settings. Once that subscriber registers as a user, then only he/she can edit. Admin no longer has permission to change these settings. [image: editSubscriberByAdmin.gif] Terry Earley

2 1

Re: Mailman - delete or backup old archived messages
by Lucia Moreno 01 Jul '21

01 Jul '21

Hi Mark, We are facing the same issue. My postgres database is growing too fast and I would need to do some creaning of old archives dated from 2001 and keep only the last, lets say... 5 years. Could you please help us with the development of such a script? I have no experience in python. Thanks a lot in advance, Lucia

2 2

How to secure LMTP transport?
by Adam Minski 30 Jun '21

30 Jun '21

Hello, what is recommended to secure traffic to LMTP port 8024 by SSL/TLS? Thx Adam

2 1

mailman web spamming uwsgi error log.
by Sarah H 29 Jun '21

29 Jun '21

I'm having an issue with the mailman web logs (/opt/mailman/web/logs/uwsgi-error.log) spamming the below: 20:53:44 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/django_q/cluster.py", line 436, in worker res = f(*task["args"], **task["kwargs"]) File "/opt/mailman/venv/lib64/python3.6/site-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month mlist = MailingList.objects.get(name=mlist_name) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/query.py", line 417, in get self.model._meta.object_name hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList matching query does not exist. the best match I can find in the archives is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I have used suggested command there (/opt/mailman/venv/bin/mailman-web runjobs recent_threads_cache) as well as manually running the hourly, daily, weekly, and monthly crons manually and all run successfully but I'm still getting the same entries spamming the logs to the point that when I discovered this the logs were 9.6GB in size. I do not have a list named "MailingList".

2 3

Re: List rename
by Christina A Hilfer 28 Jun '21

28 Jun '21

Hi Joel, I know it's been a while since you found your work around but can you give the exact steps prior to the update SQL commands you provided? I am getting a syntax error on the first one and I have not been able to figure out how to move forward. Thanks, Christina [cid:image001.png@01D76C01.D1DFEF40]<http://www.unr.edu/> Christina Hilfer Senior Application Specialist Office of Information Technology - IT Operations 1664 N Virginia Street Reno, NV 89557 work-phone: 775-784-1967<tel:775-784-1967> email: chilfer(a)unr.edu<mailto:chilfer@unr.edu> website: http://oit.unr.edu/

1 0

Help with some 'withlist' configuration changes
by David Partain 23 Jun '21

23 Jun '21

Hi, Firstly, a repeat that I have a relatively broken (and soon to be fixed, I hope) installation of mailman3 based on Ubuntu 18.04 distrib packages (3.1.1-9) that stumbles along by me dealing with a bunch of things by hand that I hope'll go away once I'm up to the current version. In this set-up, I get a fair number of items shunted. Since I have this wonky version where stuff isn't always exposed in the web interface, I have to fix these things by hand. An example is that something gets shunted because of too many recipients, where I do: sudo -u list mailman withlist somemailmanlist m.max_num_recipients = 0 commit() sudo -u list mailman unshunt I've managed to find a number of these, such as m.max_message_size, m.require_explicit_destination, and m.administrivia. My questions are undoubtedly foolish, but here goes: 1. Is there any way to print the entire 'm' structure? If so, I'd perhaps be able to figure out the answers to my other questions. 2. Is there a way for me to correct the following shunt-ing issues with 'withlist'? I've been unable to figure out how... a. 'moderation_reasons': [ 'Message has no subject'] / 'rule_hits': ['no-subject'] b. Some things get caught as 'rule_hits': ['nonmember-moderation']. However, if I look in the (web-based) config, it shows that non-members should be accepted but the messages are shunted nonetheless. I don't know what to look for in 'm' or how I might clear these messages. 3. I have no idea what these are telling me to do about digest messages. Suggestions? This is the entire info I get from 'mailman qfile': ------------------------------------------------------snip snip---------------------------------------------- [----- start pickle -----] <----- start object 1 -----> <----- start object 2 -----> { '_parsemsg': False, 'digest_number': 457, 'digest_path': '/var/lib/mailman3/lists/somelist/digest.31.457.mmdf', 'lang': 'en', 'listid': 'somelistid', 'version': 3, 'volume': 31, 'whichq': 'digest'} [----- end pickle -----] ------------------------------------------------------snip snip---------------------------------------------- 4. I have some that have 'rule_hits': [] (it's empty) but are shunted nonetheless. I can't see anything weird other than one of the messages has a utf-8 subject. Any ideas? 5. Some messages that were sent to -request addresses (e.g., subscribe messages, confirm, approve messages) are being shunted. What should I do with these? Thanks for your patience. Cheers, David

2 2

Mailman3 service on mailman-3.3.4 is not getting started
by Shashikanth Komandoor 23 Jun '21

23 Jun '21

Hi team, I am trying to install mailman 3.3.4, the currently available latest version at https://docs.mailman3.org/en/latest/install/virtualenv.html on RHEL 7.5. As part of the installation, I am not creating any user with the name *mailman* and instead going with the *root* user only. Along with that I am using the directory */var/lib/mailman* as the root directory. Also, I have rsyslog service running on my machine and using postgresql-11 as the database service. My mailman3 service looks like this: # cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=rsyslog.target network.target postgresql-11.service [Service] Type=forking PIDFile=/var/lib/mailman/var/master.pid User=root Group=root ExecStart=/var/lib/mailman/venv/bin/mailman start ExecReload=/var/lib/mailman/venv/bin/mailman restart ExecStop=/var/lib/mailman/venv/bin/mailman stop [Install] WantedBy=multi-user.target Now, the issue is while I am trying to start the service, it is showing the below error and the status looks like as following: # systemctl start mailman3 Job for mailman3.service failed because a configured resource limit was exceeded. See "systemctl status mailman3.service" and "journalctl -xe" for details. # systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; disabled; vendor preset: disabled) Active: failed (Result: resources) since Wed 2021-06-23 12:51:27 IST; 1min 7s ago Process: 16277 ExecStart=/var/lib/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Jun 23 12:51:27 psumm3.nic.in mailman[16277]: os.execl(*execl_args) Jun 23 12:51:27 psumm3.nic.in mailman[16277]: File "/usr/lib64/python3.6/os.py", line 527, in execl Jun 23 12:51:27 psumm3.nic.in mailman[16277]: execv(file, args) Jun 23 12:51:27 psumm3.nic.in mailman[16277]: TypeError: expected str, bytes or os.PathLike object, not NoneType Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Starting Mailman's master runner Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Generating MTA alias maps Jun 23 12:51:27 psumm3.nic.in systemd[1]: PID file /var/lib/mailman/var/master.pid not readable (yet?) after start. Jun 23 12:51:27 psumm3.nic.in systemd[1]: Failed to start GNU Mailing List Manager. Jun 23 12:51:27 psumm3.nic.in systemd[1]: Unit mailman3.service entered failed state. Jun 23 12:51:27 psumm3.nic.in systemd[1]: mailman3.service failed. I can't understand where the issue might be. Thank you in advance. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 1

PermissionError: [Errno 1] Operation not permitted
by Sarah H 22 Jun '21

22 Jun '21

The system we are running mailman 3 on crashed, it filled the drive, and when it was restarted and the issue cleared I found that mailman3 will not start, it returns the following: Jun 21 14:12:29 mailman[513274]: Traceback (most recent call last): Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/bin/mailman", line 11, in <module> Jun 21 14:12:29 mailman[513274]: load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 829, in __call__ Jun 21 14:12:29 mailman[513274]: return self.main(*args, **kwargs) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 782, in main Jun 21 14:12:29 mailman[513274]: rv = self.invoke(ctx) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke Jun 21 14:12:29 mailman[513274]: return super().invoke(ctx) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke Jun 21 14:12:29 mailman[513274]: return _process_result(sub_ctx.command.invoke(sub_ctx)) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1066, in invoke Jun 21 14:12:29 mailman[513274]: return ctx.invoke(self.callback, **ctx.params) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 610, in invoke Jun 21 14:12:29 mailman[513274]: return callback(*args, **kwargs) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/decorators.py", line 21, in new_func Jun 21 14:12:29 mailman[513274]: return f(get_current_context(), *args, **kwargs) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/cli_control.py", line 91, in start Jun 21 14:12:29 mailman[513274]: status, lock = master_state() Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/master.py", line 104, in master_state Jun 21 14:12:29 mailman[513274]: os.kill(pid, 0) Jun 21 14:12:29 mailman[513274]: PermissionError: [Errno 1] Operation not permitted Jun 21 14:12:29 systemd[1]: mailman3.service: Control process exited, code=exited status=1 Jun 21 14:12:29 systemd[1]: mailman3.service: Failed with result 'exit-code'. this is via starting as root with systemctl start mailman3, or as the user mailman using /opt/mailman/venv/bin/mailman start originally there was a similar error PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/locks/master.lck' and another similar error (that I can't find presently) for the logfile, both were owned by root when I checked them so I changed the owner back to mailman. anyone have any insight? there isn't much in the way of description on the error so I'm not sure what it's lacking permissions on. (and tried chown -R for the /opt/mailman folder already since everything there should be owned by mailman anyway)

2 2

integrate subscribe form in Website -> CSRF-token
by Jens Günther 22 Jun '21

22 Jun '21

Hello, we wanted to integrate a subscribe-form in our website after Update from Mailman2 to Mailman3. Before it was quiet easy and supposedly still is, but we can't figure out what to do with the CSRF-token-problem. Is there anywhere a documentation on this? We can't find one. If not, I would like to post more on what we tried with the html-code and what is coming up afterwards. (forbidden 403 - CSRF-verification failed. Request aborted.) Thanks in advance! Jens.

4 4

Bounce Score
by Jeff 22 Jun '21

22 Jun '21

Is there an easy way to determine a list member’s bounce score and/or reset that to zero? Thanks much, Jeff

2 1

How to identify the exact reason behind the shunting of the mails ?
by Shashikanth Komandoor 20 Jun '21

20 Jun '21

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in-built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values. I am almost running 2000 lists with 128 GB RAM and 24 Cores on a single VM and on which all the mailman 3 components are running. I have been running this setup in production for the past 2 years and 6 months. From the beginning of the above setup until recent days, I observed a few mails moving to the shunt queue now and then. But from recent days it is observed that many mails are moving to the shunt queue. I browsed many websites but I could not get a proper resolution for identifying the exact reason behind the shunting of the mails. Because of which I had been asking the user to resend the mails instead of suggesting the user regarding the issue properly. I in fact used the command "mailman qfile <filename.pck>" even then I don't understand what might be wrong with the mail composition. Most of the time I see *unknown-8bit* in To or CC fields and I don't know if it is linked with the reason for shunting or not and I don't get any clue from it either. Is there any chance to find out the reason for shunting of the mails through any means ? -- Thanks & Regards, Shashi Kanth.K 9052671936

2 6

ModuleNotFoundError: No module named 'settings'
by Michela 18 Jun '21

18 Jun '21

Hello! I've just set up Mailman 3 with Hyperkitty and Postorius in venv via pip by using the guide at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… on Oracle Linux 8.3 with Python 3.6.8. The process seemed to go smoothly and without errors. The log file, /opt/mailman/web/logs/uwsgi-error.log, contains the following stack trace, however. Note the bit toward the bottom: "ModuleNotFoundError: No module named 'settings'" Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 224, in fetch_command app_name = commands[subcommand] KeyError: 'qcluster' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_web/manage.py", line 30, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 231, in fetch_command settings.INSTALLED_APPS File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 76, in __getattr__ self._setup(name) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 63, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 142, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' [uwsgi-daemons] throttling "/opt/mailman/venv/bin/mailman-web qcluster" for 245 seconds [uwsgi-daemons] respawning "/opt/mailman/venv/bin/mailman-web qcluster" (uid: 1002 gid: 1002) Mailman and mailman-web do start without errors when I run them via their systemd unit files and Postorius serves up pages (without styles and such, which I'll fix later). SELinux is disabled, at least while I work through this issue. I've gone over the configuration files, and everything appears to be in order as written in the installation instructions, but that's likely not the case. :) My configuration files outside of the Mailman virtual environment are in /etc/mailman/: (venv) [mailman@host ~]$ ls /etc/mailman3/ mailman.cfg __pycache__ settings.py uwsgi.ini When searching the web about this, I only found one result, on this very list, but it didn't have quite enough information for me to solve my issue. It might also not quite be the same problem: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Might you be able to point me in the right direction on solving this issue? Please tell me if there is any more information I can provide to that end. Best, Michela

7 9

Mailman - delete or backup old archived messages
by olenkoigetublim＠gmail.com 18 Jun '21

18 Jun '21

Hello Mailman team! I have been using Mailman-Suite (Hyperkitty + Postorius) quite a long time now and now i was wondering if there is any way to erase or export old archived messages and back them up elsewhere (for example messages, that are older then 1 year). Didnt find any suitable option under "python3 manage.py" command and also didnt find any up to date post which related to mailman3 and python3. Additional info: *Database: Postgresql13 *Mailman version: 3.3.4 *Python version: 3.6 Br, Dim

2 1

Mailman archive issues (Hyperkitty)
by klillipuu＠gmail.com 16 Jun '21

16 Jun '21

Hello All! I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). I also mention, that hyperkitty is a pretty old version - 1.1.4. The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? Extra information: * I have also noticed some memory violation issues which has caused by uwsgi. * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Output from mailman.log: HyperKitty failure on http://localhost/hyperkitty/api/mailman/archive: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (504) Exception in the HyperKitty archiver: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (1808) Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html>

5 13

#mailman irc channel moving to libera.chat
by Abhilash Raj 15 Jun '21

15 Jun '21

Hey Everyone, As some of you might already know that Freenode IRC server now has new owners and most of the volunteer staff have decided to move away from it to create a new IRC server libera.chat[1] due to the policies of the new owners. Along with many other open source projects, we have also decided to move away from freenode to use libera.chat instead. We have registered #mailman there and will be using that as primary IRC channel for Mailman things. Freenode has also decided to drop all registrations, so, #mailman channel there is no longer registered to any member of Mailman Core team as of some time earlier today (Tue June 15th). [1]: https://libera.chat/ -- thanks, Abhilash Raj (maxking)

1 0

docker-mailman Bump to 3.3.4
by matthew＠alberti.us 11 Jun '21

11 Jun '21

Hi Mailman Docker Maintainer(s) (maxking 😊 ), Just wanted to see if the docker-mailman will be bumped to 3.3.4. I believe docker-mailman release 0.3.11 is the latest release, and that gives us Mailman 3.3.3. Thank you. - Matt Alberti

1 0

OS update 18.04 -> 20.04 with Python 3.6 -> 3.8
by Torge Riedel 06 Jun '21

06 Jun '21

Hi, just want to report that updating my server's OS from Ubuntu 18.04 to 20.04 including an upgrade from Python 3.6 to 3.8 worked 75% on the mailman3 installation. Stopping and disabling the service before prevented most of the problems, but I forget to disable the cron jobs. **sigh** So whenever you have to upgrade your OS including python, don't forget the cron jobs. After OS upgrade I renamed both "venv" directories and rebuild them from my notes. Worked. Starting up mailman-core was easy. Getting mailman-web back to work was a little tricky: 1. After rebuild I forgot to run the post-update script, overseen that in my notes. **sigh #2** 2. My uwsgi-emperor was totally confused and needed some guidance and manual remove of .sock file 3. Finally I got this in the logs: /opt/mailman/web/venv/lib/python3.8/site-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. Seehttps://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( I checked the reference file from here: |https://gitlab.com/mailman/mailman-suite/raw/master/mailman-suite_project/settings.py?inline=false| and it misses the "retry" value. After adding it to Q_CLUSTER everything works fine. Kind regards Torge

1 0

Long-shot cry for help
by David Partain 03 Jun '21

03 Jun '21

Hi, I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... 2. There's this one curious cron job... * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings (yes, I know python2.7 is a problem... see the last paragraph below). These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? ----------------------------------- Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Cheers, David

4 3

Send MySQL data to mailman list for distribution
by Zden Pos 02 Jun '21

02 Jun '21

I'm trying to connect existing MySQL data to the Mailman distribution list. Actually, a message is sent from the web page. It remains on this page and is also stored in the MySQL table on the provider server. This is working fine. I have also existing Mailman distribution list generated from the cPanel on the provider server as well. This list is working fine when used for a direct mailing. I need to link the MySQL table to the Mailman distribution list. When the message is posted on the web page and stored in the MySQL table, it is also to be sent to members as per the Mailman distribution list. I don't know where to configure it. In the phpMyAdmn page of the MySQL or in the Malman menu ? Thank you for your help

3 2

Getting connection timed out
by blackout69 01 Jun '21

01 Jun '21

Hello everybody, for a couple of days I have been seeing several lines calling these on /var/log/mail.log May 22 18:22:57 glugct postfix/qmgr[21205]: 0ACE641C1B: from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) May 22 18:23:06 glugct postfix/qmgr[27175]: 0ACE641C1B: from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) May 22 18:23:36 glugct postfix/smtp[27177]: 0ACE641C1B: to=<myaddress(a)simail.it>, relay=none, delay=55152, delays=55122/0.07/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) May 22 19:33:06 glugct postfix/qmgr[27175]: 0ACE641C1B: from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) May 22 19:33:36 glugct postfix/smtp[28757]: 0ACE641C1B: to=<myaddress(a)simail.it>, relay=none, delay=59352, delays=59322/0.04/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) May 22 18:33:06 glugct postfix/qmgr[27175]: 955D241C15: from=<direttivo-bounces(a)catania.linux.it>, size=11026, nrcpt=3 (queue active) May 22 18:33:36 glugct postfix/smtp[27474]: 955D241C15: to=<myaddress(a)simail.it>, relay=none, delay=124379, delays=124349/0.02/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) May 22 19:43:06 glugct postfix/qmgr[27175]: 955D241C15: from=<direttivo-bounces(a)catania.linux.it>, size=11026, nrcpt=3 (queue active) May 22 19:43:36 glugct postfix/smtp[28975]: 955D241C15: to=<myaddress(a)simail.it>, relay=none, delay=128579, delays=128549/0.04/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) But always on a single email address.What could it depend on?Probable that the mail.simail.it server is blacklisted? Thank you in advanc -- blackout69

4 11

How to store additional information about lists?
by Andreas Barth 30 May '21

30 May '21

Hi together, I need to add custom attributes to the mailing lists: "responsible department": Free text field who is responsible from an organisational pov (not a person but an entity) Enhance the boolean public to a tri-state: public, restricted audience and private (restricted audience means: some people could subscribe themself - how that works is a different topic but w/o the information this can't be achived) - of course this could also be implemented as a second boolean that e.g. splits "not public" into "restricted audience" and "private" (means: nothing goes wrong for code that doesn't know this difference). Any hints how to do that best? Is it possible to store custom attributes, or should that be stored elsewhere? Andi

4 19

email command join - problem
by sky.x＠nazelenej.sk 28 May '21

28 May '21

Hi All Im using Mailman core 3.3.4 on Ubuntu 20.04 with python 3.8 anf have this problem with email command join. When send command to ml-request@ join address=some.email(a)domain.com Response is: Confirmation email sent to 3dsome.email(a)domain.com It add characters 3d to email and realy sent confirmation to it. Also help command for join return me join [digest=<no|mime|plain>] [address=user(a)example.com] But digest doesnt work as after command join digest=no address=some.email(a)domain.com i get join bad argument: digest=no I will be thankfull for any help/advice. S.

3 5

trying to clean up the "held messages" mess
by Bjoern Franke 28 May '21

28 May '21

Hi, I migrated a Mailman3 installation on Debian10 yesterday evening from Debian packages to PIP (thanks to [1]). I think some bugs which existed before are now cleaned out, but mailman still threw exceptions when trying to get the "held messages". I went through the pendedkeyvalue table of the MySQL DB to get all request ids of the held messages and their lists and discarded the messages via curl and the REST API. Mailman also logged the discarding was successful. The amount of held messages is now reduced, but e.g. a list with 120 held messages before has till 59 held messages. And now I'm confused: where are they? Best Regards Bjoern [1]https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10

2 3

non-member moderation: list default vs default processing
by dancab＠caltech.edu 24 May '21

24 May '21

I've started testing and importing lists from Mailman2 to Mailman3. I've found that there's an inconsistency with the non-members moderation setting. As a result we have non-members unable to email a list via Mailman3 that had no problem on Mailman2. Each time this problem has come up I've had to change the moderation setting from "List Default" to "Default Processing". But I've also noticed that some non-members were imported and already have "Default Processing" configured. Can you help me understand what determines this setting in Mailman3? It seems this would be something addressed via the mailman import21 option I've been using to import the lists. Thanks. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu

2 4

Intermittent: pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77
by Torge Riedel 24 May '21

24 May '21

|Hi list, sometimes I get the following error in mailman core's log: "pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77". I attached the full log after this mail. I check the provided link in the log (|||http://sqlalche.me/e/2j85|) and also searched for it on the internet and found the following possible reasons: 1. DB user does not have permissions at all -> I doubt that, because in general mailman is working ok 2. DB user is not allowed to connect from remote -> I doubt that too, because everything is on one host and DB user is allowed to connect from localhost 3. Multi-Threading -> pymysql is mentioned to be not thread-safe and each thread needs its own connection May this be caused by multi-threading? What do I have to do (is there anything I can do?) to solve this on my own?||||| Kind regards Torge || |Full log follows: [2021-05-23 07:31:45 +0200] [8244] [ERROR] Error handling request /3.1/lists?advertised=true&count=10&page=1 Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context cursor, statement, parameters, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute cursor.execute(statement, parameters) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute result = self._query(query) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query conn.query(q) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result result.read() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read self._read_result_packet(first_packet) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet self._get_descriptions() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions field = self.connection._read_packet(FieldDescriptorPacket) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet % (packet_number, self._next_seq_id)) pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77 The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 322, in on_get resource = self._make_collection(request) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 172, in _make_collection request, self._get_collection(request)) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 167, in _paginate return list_start, total_size, collection[list_start:list_end] File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/utilities/queries.py", line 42, in __getitem__ return self._query[index] File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3149, in __getitem__ return list(res) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3481, in __iter__ return self._execute_and_instances(context) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3506, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1020, in execute return meth(self, multiparams, params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_clauseelement distilled_params, File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1324, in _execute_context e, statement, parameters, cursor, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1518, in _handle_dbapi_exception sqlalchemy_exception, with_traceback=exc_info[2], from_=e File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ raise exception File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context cursor, statement, parameters, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute cursor.execute(statement, parameters) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute result = self._query(query) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query conn.query(q) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result result.read() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read self._read_result_packet(first_packet) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet self._get_descriptions() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions field = self.connection._read_packet(FieldDescriptorPacket) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet % (packet_number, self._next_seq_id)) sqlalchemy.exc.InternalError: (pymysql.err.InternalError) Packet sequence number wrong - got 102 expected 77 [SQL: SELECT mailinglist.list_id AS mailinglist_list_id, mailinglist.preferred_language AS mailinglist_preferred_language, mailingli$ FROM mailinglist WHERE mailinglist.advertised = true ORDER BY mailinglist.list_id LIMIT %(param_1)s] [parameters: {'param_1': 10}] (Background on this error at: http://sqlalche.me/e/2j85) |

3 5

Unknown attribute: process_bounces
by xlefloch＠alwaysdata.com 21 May '21

21 May '21

Hello, I've upgraded my Mailman installation from those versions: mailman==3.2.2 postorius==1.2.4 mailmanclient==3.2.2 To those ones: mailman==3.3.0 postorius==1.3.3 mailmanclient==3.3.2 I'm having issues in Postorius in the settings section: Unknown attribute: process_bounces. When i'm printing the settings list for the concerned list retrieved by the REST API, i'am missing all the parameters related to the management of bounces. In the "mailinglist" table of the Mailman database, i have the columns managing these parameters. Anyone have any ideas? Regards,

2 3

New Mailman 3 installation issues
by sarah.hartt＠ionica.ca 21 May '21

21 May '21

I have been trying to get a mailman 3 installation working for longer than I'd like to admit. Core appears to be installed and working as desired but Postorius (and hyperkitty, but I haven't even started troubleshooting it while trying to get the web interface working) is only loading the main page with no lists shown and all remaining links return a server error (specific text is: "Server error An error occurred while processing your request." with the error text highlighted). I think I followed all of the installation instructions, including the updated pythonpath line in the systemd module, but it's entirely possible that there is an error somewhere along the way. I have had to make two minor tweaks, the /static/ location was moved from /opt/mailman/web/static to /var/www/mailman/ (owner mailman:nginx) as nginx was giving permissions errors (even if it owned the files or with the mod set to 777) with the default location and wouldn't load the css, and installed postgres directly from their repo as the method in the guide doesn't create the user. Aside from that everything should be exactly as laid out in the installation guide. The logs are showing everything running and the DB logs show all the queries going through successfully, there are no errors in the web logs corresponding with the errors being served on the site aside an entry for a 500 in the access logs [18/May/2021:12:13:01] "GET /archives/ HTTP/1.1" 500 1102 "http://mailman3/mailman3/lists/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.91 Safari/537.36" "-" when I took a look in the DB tables many of them appear to be empty, I have a few lists in core that were imported from 2.1 but no new lists created. Mailman: 3.3.4 Postorius: 1.3.4 OS: Oracle Linux 8.3 Python: 3.6 postgres: 13.2

4 11

timezone in hyperkitty
by erlonmz＠hotmail.com 21 May '21

21 May '21

How do I change the hyperkitty timezone?

7 8

Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'
by Mark Sapiro 21 May '21

21 May '21

On 5/19/21 10:37 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: > > Here are (what I think are :-)) the anonymized relevant parts of the smtp.log. > > May 19 08:52:29 2021 (126270) _handle_client readline: b'MAIL FROM:<aaaaaaaaaa.a.aaaaa-1(a)nasa.gov> SIZE=11726\r\n' > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) >> b'MAIL FROM:<aaaaaaaaaa.a.aaaaa-1(a)nasa.gov> SIZE=11726' > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) sender: aaaaaaaaaa.a.aaaaa-1(a)nasa.gov > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) << b'250 OK' > ... > May 19 08:52:29 2021 (126270) DATA readline: b'From: "Aaaaa, Aaaaaaaaaa A. (location)[employer,\r\n' > May 19 08:52:29 2021 (126270) DATA readline: b' Inc.]" <aaaaaaaaaa.a.aaaaa-1(a)nasa.gov>\r\n' That all looks good. I don't understand what's wrong. Can you apply the attached patch to mailman/rules/no_senders.py and see what you get in Mailman's debug.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 1

Can't deliver mails in queue
by Nathanael Schneider 20 May '21

20 May '21

Hello, I have stumbled upon some weird issues with my migration to mailman3.. I've followed the step by step instructions for installing mm3 manually in a venv with postfix and virtual aliases (if that is of any significance). Now the Problem is, that some lists don't deliver EMails at all. The list was one which I migrated with the mailman21 command. But the Mail I sent did not get through to no one and the mailman logs did not show anything. I then created a completely new List which did not exists in mm2.1, subscribed two addresses and sent myself an EMail. That one worked as intended. I then deleted the whole broken list and created it cleanly, added the same two people, sent an email and nothing. Did not show up in the Moderation Queue or anywhere. it also doesn't get shunted. It just never arrives. I then turned the log level to debug on the smtp module. And I only get the following statement, ever repeating, never ending: [...] May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4978db438> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb497f05f28> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4978adb38> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net [...] I have no clue what to do with this. I then turned the debug module loglevel to debug. Also nothing useful. Just an endless list of [...] May 19 18:17:29 2021 (7209) [outgoing] <function deliver at 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile May 19 18:17:29 2021 (7209) [outgoing] <function deliver at 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> [...] Which also tells me nothing I can understand. I have no clue what's going wrong. (I've turned on debugging both on the original member list and the reduced member list. Both hang on the first delivery they do). If I restart mailman, the message gets correctly shunted as it is interrupted mid-delivery. My maillogs don't register any activity beside the listpost. Any ideas what I need to do to figure out what's not working here or where the culprit could be? Not sure if it is related to the mailinglist being in mailman2.1 before. -- Nathanael Schneider

2 5

Bounce counter visibility for List Admins
by smorytko＠gmail.com 19 May '21

19 May '21

As you may know, we use MM3 but the Affinity/Empathy flavor and we only have List Administrator using the Postorious/Affinity. Unlike many here, we have no access to any server-based files. Can someone tell me if Postorious gives list administrators visibility into the bounce counters? While List Admins get to set various bounce counters we have no visibility of those counters until, all of a sudden, an entire source of subscribers hits the bounce threshold and gets bounced off the list. It would be really nice to be able to see the bounce counters and possibly head off trouble before users/subscriber mail hosts. It can serve as an effective early warning system that something is wrong. Assuming Postorious cannot, is there another way List Admins can inspect bounce counters? Email command? Thanks - Steve

3 3

Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'
by Mark Sapiro 19 May '21

19 May '21

Putting this back on the list. On 5/19/21 9:46 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> ... >> Have you set >> ``` >> [mailman] >> sender_headers: ... >> ``` >> in mailman.cfg?, and if so, to what? > > We have not changed it: > > [mailman] sender_headers: from from_ reply-to sender > > According to the smtp.log, there was an envelope sender ("MAIL FROM:.."), which matched the From header. In the example I'm looking at right now, the sender was not a member of the list, but the Accept these non-members box in the list settings has a regexp that matches the sender's domain. In another example from this morning, to a different list, the envelope sender and From header match, and is a member of the list. > > I don't see any obvious reason or configuration setting that would make either address invalid. First of all, the discard has nothing to do with whether the sender has any connection to the list. It only says the message had no sender at all. Assuming the message had a From: with a syntactically valid email address, this discard should not occur. Also, if the envelope (MAIL FROM:) was a syntactically valid email address, this discard should not occur. The address is validated by mailman/email/validate.py by first splitting it into `local_part`, `@`, `[domain_parts]` where domain_parts are the `between dots` parts of the domain and then validating the local_part and domain with regexps defined per > # What other characters should be allowed? > _valid_local = re.compile("[-0-9a-z!#$%&'*+./=?@_`{}~]", re.IGNORECASE) > # Strictly speaking, both ^ and | are allowed and others are allowed in quoted > # local parts, but this can open the door to certain web exploits so we don't > # allow them. > _valid_domain = re.compile('[-a-z0-9]', re.IGNORECASE) > # These are the only characters allowed in domain parts. Does the From: local part or the MAIL FROM: contain any characters not in the [-0-9a-z!#$%&'*+./=?@_`{}~] class? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

[Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/
by Mark Dadgar 19 May '21

19 May '21

I have a user attempting to access the list archives and he’s generating this login error. I have verified that he does have a django account. I’ve never seen this one before and I didn’t find anything relevant in the lit archives. Any ideas what’s going on here? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 ----------------------------------------------- From: noreply(a)pdc-racing.net Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /accounts/login/ Date: May 18, 2021 at 2:38:20 PM PDT To: mark(a)pdc-racing.net Internal Server Error: /accounts/login/ MultipleObjectsReturned at /accounts/login/ get() returned more than one EmailAddress -- it returned 2! Request Method: POST Request URL: https://mail.pdc-racing.net/accounts/login/ Django Version: 3.0.12 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.8.5 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/opt/mailman/mm/venv/lib/python3.8/site-packages'] Server time: Tue, 18 May 2021 14:38:20 -0700 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 146, in dispatch return super(LoginView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/views.py", line 159, in form_valid return form.login(self.request, redirect_url=success_url) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/forms.py", line 195, in login ret = perform_login( File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 174, in perform_login if not _has_verified_for_login(user, email): File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/utils.py", line 134, in _has_verified_for_login emailaddress = EmailAddress.objects.get_for_user(user, email) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/allauth/account/managers.py", line 54, in get_for_user ret = self.get(user=user, email__iexact=email) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/db/models/query.py", line 419, in get raise self.model.MultipleObjectsReturned( Exception Type: MultipleObjectsReturned at /accounts/login/ Exception Value: get() returned more than one EmailAddress -- it returned 2! Request information: USER: AnonymousUser

2 4

OS upgrade - anything to take care of?
by Torge Riedel 15 May '21

15 May '21

Dear MM3 users, today I upgraded one of two servers from Ubuntu 18.04 to 20.04 and - besides some minor config updates - postfix & dovecot worked well afterwards. So I am very optimistic that the upgrade of the second server from 18.04 to 20.04 will also work fine. But the second server is running MM3 (installed in venv) and I saw that on upgrade Python 3.8 is installed. Is there anything I have to take care of? Anything to do / change in venv? Kind regards Torge

4 10

Re: Core, Hyperkitty and Postorius releases
by Odhiambo Washington 15 May '21

15 May '21

On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > > > On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > /bin/sh: sass: Permission denied* > > > > Did you check the permissions on your sass binary? > My mailman installed in /opt/mailman/mm find /opt/mailman/ -type f -name sass yielded nothing! pip3 install sass generated so many errors then ended with: ERROR: Command errored out with exit status 1: /opt/mailman/mm/venv/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-cltizg93/sass_9783b9d070744303b5c04271674abc23/setup.py'"'"'; __file__='"'"'/tmp/pip-install-cltizg93/sass_9783b9d070744303b5c04271674abc23/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-1g2omozl/install-record.txt --single-version-externally-managed --compile --install-headers /opt/mailman/mm/venv/include/site/python3.7/sass Check the logs for full command output. I will have to blow away mailman and start afresh. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 17

Core, Hyperkitty and Postorius releases
by Abhilash Raj 15 May '21

15 May '21

Hey Everyone, I am pleased to announce new stable releases for Mailman Core, Postorius, Hyperkitty. These include both new features and bug fixes. Complete change log for each components: Mailman Core 3.3.3: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… Postorius 1.3.4 https://docs.mailman3.org/projects/postorius/en/latest/news.html Hyperkitty 1.3.4 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Minimum supported Python version is 3.6. You can install them using: $ pip install --upgrade postorius hyperkitty mailman We have also recently been working on making the installation instructions[1] to be more detailed and added a new FAQ[2] section for administrators where I hope to capture common questions from mailman-users list. Feedback or Merge Requests to improve these docs are welcome. You can either send an email or open an issue on Gitlab (easier to track) here[3]. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html [2]: https://docs.mailman3.org/en/latest/faq.html [3]: https://gitlab.com/mailman/mailman-suite-doc/issues Thanks to everyone who helped out with with this release and contributed if any way! :) thanks, Abhilash Raj On behalf of Mailman Core Team

4 10