- Mailman-users - lists.mailman3.org

SpamAssassin header confusion
by skenny＠scss.tcd.ie April 10, 2021

April 10, 2021

I'm struggling to understand an aspect of SpamAssassin headers, and would greatly appreciate any help. Here is my scenario: One of my mailbox addresses - say addr1(a)somewhere.com - is a member of a Mailman 3 mailing list. I send a spam email (e.g. one with the GTUBE string) to the list from a different address. My mail server (Postfix/Amavis/Spamassassin) correctly identifies the mail as spam, and, appropriately, adds several spam-related headers - X-Spam-Flag, X-Spam-Score etc. I can see, from the copy of the email that lands in /var/lib/amavis/virusmails on the mail server, that those headers are indeed present. The mail message is handed off to Mailman for processing. The list in question has nonmember_default_action set to "defer", so Mailman sends the message on to each member address. However, the message, as it appears in the inbox of addr1(a)somewhere.com, contains no X-Spam- headers. The only indication of the message's spammish nature is in the Subject line, which has been prepended with the familiar string "***SPAM*****". On the face of it, it looks like Mailman has removed the X-Spam-* headers. If that's so, I don't understand why. I would be very grateful if anyone could help me figure out what is going on here. Thanks in advance, Stephen

2 4

Database deadlock when trying to delete a member.
by Simon Coggins April 9, 2021

April 9, 2021

Hi, I’ve got a strange error. I migrated from mailman 2.1 to 3 using the migration guide on the website and things have been working fine. But I’m in the process of testing the new syncmembers command to replace some inhouse mailman API code we wrote. I’ve tracked my problem down to what appears to be a deadlock in the postgresql database. When trying to delete certain users the SQL query hangs and never returns. After doing some tracing and tracking it down to the database, I enabled DB logging of all queries and saw that the following query was never returning: DELETE FROM member WHERE member.id = 166814 If I try to run it manually I get the same issue, in psql it never returns. mailman=# explain analyze DELETE FROM member WHERE member.id = 166814; [… 60 seconds passes…] ^CCancel request sent ERROR: canceling statement due to user request CONTEXT: while deleting tuple (2998,72) in relation "member" I’m just wondering if there are any commands or scripts I can run to verify the database and it’s constraints to see if there is some error in the database data? Or where you’d recommend I go from here? It only impacts the user on this specific list. If I add this user to another list and remove them, everything works fine. This is on a test system so I can do various testing. I’m trying to find the root cause so that I can verify my production system isn’t impacted by the same thing. Setup Details: OS: Oracle Linux 7 (Redhat) Installed using pip via virtualenv talking to a local pgsql database on the same box. Data was migrated from a mailman 2.1 install into mailman3 using migration instructions on the website. PIP Modules versions: django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 psycopg2-binary 2.8.5 RPM packages: postgresql12-12.6-1PGDG.rhel7.x86_64 postgresql12-server-12.6-1PGDG.rhel7.x86_64 postgresql12-libs-12.6-1PGDG.rhel7.x86_64 postgresql12-devel-12.6-1PGDG.rhel7.x86_64 -Simon

4 13

Filter who can send on mailman3 list?
by marcus.granath＠gmail.com April 8, 2021

April 8, 2021

Hi! I have a mailman3 mailing list which I admin, and I would like setup the following rule. Me and 3 of my team mates (who are part of the mailman3 list) should be able to send on the list as well as an "no-reply" user, others on the mailman3 list should only be able to receive the e-mails (and of course be able to unsubscribe themself). Both the: "Default action to take when a non-member posts to thelist" and the "Default action to take when a member posts to the list" is set to "Default processing", and I tried to setup actions in the "Header Filters" - but no really success.. :-( So what I basically try do achieve is to have only the following addresses to be allowed to send announcements (e-mails) on the mailman3 list, and all others that are member of the mailman3 list will just receive the e-mails. The usual "announcements" are sent out as the "no-reply" address (that actually are not really part of the mailman3 list) ;-) no-reply(a)abc.com ("fake address" that actually are not really part of the mailing-list) peter(a)abc.com david(a)abc.com marcus(a)abc.com How to achieve this kind of filter with mailman3?

6 12

Configuration variables in Docker
by Jens Günther April 8, 2021

April 8, 2021

Hey there, we installed the latest Docker version of Mailman3 and it seems to work for now. But I have 2 problems with configuration: ## DJANGO_ALLOWED_HOSTS Here it says, that allowed hosts can be added: https://asynchronous.in/docker-mailman/web/ How de we add multiple hosts? Did I miss something? When we set 1 URL, everything works (with 2(!) Domains, since SERVE_FROM_DOMAIN is the first one). Is there a way I miss to input multiple hosts, that the variable is an array? We tried: - DJANGO_ALLOWED_HOSTS=example1.com,example2.com - DJANGO_ALLOWED_HOSTS='example1.com, example2.com' - DJANGO_ALLOWED_HOSTS=example1.com example2.com - DJANGO_ALLOWED_HOSTS=example1.com,\nexample2.com And I think some more, but never works. The corresponding config file says: ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. # "lists.your-domain.org", # Add here all production URLs you may have. "mailman-web", "172.19.199.3", os.environ.get('SERVE_FROM_DOMAIN'), os.environ.get('DJANGO_ALLOWED_HOSTS'), ] -> how is it possible to add an array for multiple Domains? -> if not possible, shall we provide a fix that it is? ## FILTER_VHOST I want this variable to be true in my container. When I set it as a starting variable like the other configuration options, then the variable in the container seems to be set: <code> # export | grep FILTER_VHOST= declare -x FILTER_VHOST="True" </code> But surely it still is set to false in mm-web-container: <code> # cat settings.py | grep FILTER_VHOST FILTER_VHOST = False </code> -> is it ok to put the variable like that!? -> if not, how can it be done, that it is preserved on restarting the container? -> if I see it right, it could be then something like: <code> FILTER_VHOST = os.environ.get('FILTER_VHOST_DOCKER'), </code> -> with some more exceptions-handling, it might work? Thanks in advance, Jens.

2 1

Seeting "Maximum number of recipients"
by David Partain April 8, 2021

April 8, 2021

Hi, I have an (admittedly old) version of Postorius in my install[1] on an Ubuntu 18.04 machine. Most things work fine. However, my version doesn't seem to have a way to set the maximum number of recipients under Message Acceptance, and mail is getting shunted because there was a setting for lists on the old mailman2 lists that I migrated over. If I'm going to avoid shunting, I have to change the value :) Since it isn't in Postorius, how should I change it? I'm frankly terrified of screwing things up on my production system, so any help would be appreciated. Cheers, David [1] python-django-postorius - 1.1.2-3

2 1

Maximum number of recipients Setting
by Brian Carpenter April 4, 2021

April 4, 2021

I have run several tests. It looks like on the 'Maximum number of recipients' setting, a 2 means 1. If I set it to 2, I can have the listname(a)listdomain.com only. If I have a CC, it comes to me for moderation. If I set it to a 3, I can send out to listname(a)listdomain.com plus a CC. If I set it to 3 and add 2 CC's plus the listname(a)listdomain.com address, it comes to me for moderation. -- Brian Carpenter Harmonylists.com Emwd.com

3 3

Mailman in Kubernetes
by danil＠smirnov.la April 3, 2021

April 3, 2021

For those who are interested in trying Mailman 3 in Kubernetes there is a Helm chart: https://github.com/danil-smirnov/mailman-helm-chart Your questions and contributions are very welcome! (Sending this from Hyperkitty UI, no clue how it will look like :D )

1 0

No digest.mmdf
by Christine March 29, 2021

March 29, 2021

I have mailman3 running now, more or less. Mailman did not send messages to my list, giving a permiission error on the digest.mmdf file, which was not there. I created the file and made list.list the owner, now it sends messages. I don't know what should have created the file or what set the permissions to the directory, I just thought I'd let you know. dagdag Christine -- dagdag is just a two character rotation of byebye

3 2

Rejection Reason for refusing a subscription request
by Brian Carpenter March 28, 2021

March 28, 2021

I was testing out the process of rejecting an incoming subscription request. Choosing the reject option for a moderated subscription request does send out a rejection notice but it gives no reason for the rejection. Please see: ------------------------------------------------------------------------ Your request to the redacted(a)redacted.com mailing list Subscription request has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "[No reason given]" Any questions or comments should be directed to the list administrator at: redacted-owner(a)redacted.com ------------------------------------------------------------------------ Is there a place somewhere in Postorius to provide a rejection reasons for moderated subscription requests? Does Mailman 3 core provide this via its REST api but it is just not revealed in Postorius yet? -- Brian Carpenter Harmonylists.com Emwd.com

3 7

rest api runner not running
by Christine March 27, 2021

March 27, 2021

Hi, I have been using mailman for about ten years, now I want to move the lists to another server, I have installed mailman3 there, most of it seems to be running, but the "rest api runner" is not. Nothing is listening on port 8001. What have I missed? What do I do to start the restapi runner? I checked the logs, I don't see anything suspicious. this is what systemctl status says: root@lists:~# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; 6min ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 173111 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM) Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation timed out. Terminating. Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result 'timeout'. Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server. There is nothing in mailman.log, nor in smtp.log dagdag Christine -- dagdag is just a two character rotation of byebye

2 1