- Mailman-users - lists.mailman3.org

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