August 2021 - Mailman-users - lists.mailman3.org

how to become member of mailman-users list
by Shashikanth Komandoor Aug. 31, 2021

Aug. 31, 2021

Hi Team, One of my colleagues is trying to become a member of the mailman-users list but she is not able to become so even after sending multiple emails to the list. Could someone suggest this ? -- Thanks & Regards, Shashi Kanth.K 9052671936

2 2

Question about message bounce stats
by Ruth Ivimey-Cook Aug. 30, 2021

Aug. 30, 2021

When I used Mailgun some time back, it had a feature of, for any specific outgoing mailing, being able to show you stats and other details of which mails were received ok, which bounced, and which were undeliverable, which I found helpful to check every so often. Their system also kept track of long-term trends, eg for addresses that frequently failed. Does Mailman3 keep such stats, and if so is there any way to get access to them, even if only API? I would think it useful to do so (and yes, for individual outgoing messages at least for a period). Regards, Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 9

auto-away notices as bounces
by Andreas Barth Aug. 30, 2021

Aug. 30, 2021

Hi, I had a user complaint that his subscription was disabled. Looking into details, his mail provider sent out lots of auto aways notices marked with Auto-Submitted: auto-replied (vacation) Should we not exclude these as being counted as bounce? (List settings are "Individual" for "Personalize" and yes for both "Include RFC2369 headers" and "Include the list post header". Regards, Andi

3 6

(nagios-)Monitoring for mailman3?
by Andreas Barth Aug. 29, 2021

Aug. 29, 2021

Hi together, does anyone have a sensible nagios monitoring for mailman3? (I had the issue that after a data base restart mailman3 was somehow disturbed but the basic web interface was still available, just the detailed pages like .../lists/$listid/ showed the error) Andi

2 1

Logging subscriptions and unsubscriptions
by Christian Schoepplein Aug. 28, 2021

Aug. 28, 2021

Hi, I am in the process to migrate from mailman 2 to mailman 3 and currently I am setting up the new environment and do some tests and play around with the new system. I'd like to have a seperate log for list subscriptions and unsubscriptions. For that reason I added the following section to the mailman-extra.cfg file: [logging.subscribe] path: subscribe.log That created a file called subscribe.log but not everything regarding subscription / unsubscriptions is added to the file. When subscribing and unsubscribing a user via mail only the following line is shown: Aug 27 10:58:31 2021 (28) tmod(a)mm3.example.com: held subscription request from chris(a)example.com Nothing regarding the finished subscription and absolutely nothing regarding the unsubscription performed later. Also in mailman.log I can find the following lines: Aug 27 10:58:05 2021 (28) deque: do_confirm_verify Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 356, in _step_send_confirmation raise StopIteration StopIteration Aug 27 10:58:31 2021 (28) deque: subscribe_from_restored Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 326, in _step_get_moderator_approval raise StopIteration StopIteration Aug 27 10:58:33 2021 (29) OWNER: <163005471133.28.13827351997075408419@mailman-core> Is this because a higher logging level or is this an error? I can find nothing really helpfull regarding subscriptions and unsubscriptions in any logfile. Is this wanted or can this changed by any configuration setting or are this information stored in the database? Cheers, Schoepp

2 1

Unwanted E-mail to Maillists Submitted via Postorius Interface
by matthew＠alberti.us Aug. 28, 2021

Aug. 28, 2021

Hi Everyone, I’ve seen a recent uptick in SPAM messages making it into mailing lists. Looking at the raw, it seems that the e-mails are being submitted thru the Postorius/Hyperkitty “Start a New Thread” interface. Is there a way to turn that off? We would want people to only be able to post via e-mail. Part of the problem is that our anti-spam system RSPAMD trusts the mailman-web IP… so it doesn’t scan things originating from there.. ☹ Another uestion: Is there a way to implement captcha, or is there a recommended gate that can be put in the signup process? Apparently bots are finding a way thru the signup process, and then sending messages to the list via the Postorius web interface. There seems to be a Django plugin for it; but it appears the Mailman code would have to be adjusted to implement it. I’m open to any suggestions, including on places to check for misconfiguration. 😊 Thanks. - Matt Alberti

4 5

docker mailman-core mailman3 image not responding on port 8024
by bob B Aug. 25, 2021

Aug. 25, 2021

Ok, I took a step back and started fresh... So the issue appears to be that mailman-core docker image is not replying on port 8024. I did a packet capture and it shows (172.23.01 is the gateway for the docker network on the host, 172.23.03 is the IP of mailman-core when I did the capture) *************************************** 1 2021-08-16 14:15:14.865053 172.23.0.1 172.23.0.3 TCP 74 34066 → 8024 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=985607751 TSecr=0 WS=128 2 2021-08-16 14:15:14.865084 172.23.0.3 172.23.0.1 TCP 54 8024 → 34066 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0 *************************************** The above show the docker host sending/relaying mail to mailman-core, but mailman-core does not acknowledge on port 8024. The images are up i.e *************************************** 58923db6fb9f maxking/mailman-core:0.3 "docker-entrypoint.s…" 26 minutes ago Up 25 minutes 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core *************************************** Docker yamel has the port setup (8024) *************************************** services: mailman-core: image: maxking/mailman-core:0.3 container_name: mailman-core hostname: mailman-core . . ports: - "127.0.0.1:8001:8001" # API - "127.0.0.1:8024:8024" # LMTP - incoming emails networks: mailman: *************************************** I can nc to the ports for docker web & 8001 on core and they are listening But 8024 is not responding *************************************** #>docker-mailman-host]# nc -v 172.23.0.4 8000 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.4:8000. ^C #>docker-mailman-host]# nc -v 172.23.0.4 8080 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.4:8080. ^C #>docker-mailman-host]# nc -v 172.23.0.3 8001 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.23.0.3:8001. ^C #>docker-mailman-host]# nc -v 172.23.0.3 8024 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connection refused *************************************** Docker logs show postfix is up on mailman-core *************************************** sudo docker logs mailman-core List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------+---------+----------+------------+------------+--------------------- mailmandb | mailman | UTF8 | en_US.utf8 | en_US.utf8 | postgres | mailman | UTF8 | en_US.utf8 | en_US.utf8 | template0 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + | | | | | mailman=CTc/mailman template1 | mailman | UTF8 | en_US.utf8 | en_US.utf8 | =c/mailman + | | | | | mailman=CTc/mailman (4 rows) Postgres is up - continuing Using Postfix configuration Found configuration file at /opt/mailman/mailman-extra.cfg HYPERKITTY_URL not set, using the default value of http://mailman-web:8000/hyperkitty *************************************** Any ideas is there anything else I can do to troubleshoot? Is the issue with the mailman-core image?

3 10

Error on timeout vs retry values
by Robert Moody Aug. 25, 2021

Aug. 25, 2021

Hi everyone, I have recently setup a new mailman3 service using the venv method. Everything is functionally working however I keep getting an error sent to the mailman email every min which I can not seem to figure out why. /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details.""" I have edited the timeout and retry values in the /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and restarted both mailman and mailman-web however this still keeps repeating. Any ideas? Regards, Robert -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 6

Mailman backend maintenance task
by eugenio.jordan＠esa.int Aug. 24, 2021

Aug. 24, 2021

Dear all. My apologies if the answer to this question is obvious, but I am pretty newbie for 3 version, and to be very honest I haven't had enough time yet to have a deep look into the documentation. Our customer is currently using PostGRESQL as backend, and we would like to perform some maintenance tasks, namely running vacuum full, or at least trying to rebuild hyperkitty_email primary key related index. We have been asked on the real impact of putting in place such initiative. Though the latter is related to archiving, I haven't found a way to stop just Hyperkitty or Django related processes other than stopping Mailman's core, hence preventing mails addressed to distribution lists from being delivered, could you please confirm if I am correct? Regarding the former, as far as I have read, the "mappings" lists -> addresses are stored just in the database, so if we run some kind of procedure or task like vacuum which will lock exclusively tables, or want anyway to have the database stopped for a cold backup or whatever, Mailman willl not work, that is, again the mails addressed to the distribution lists will not be delivered. Will you please confirm this point, too? Really wish we had a testing environment to have been able to check this ourselves and not bothering others, but unfortunately we lack it, and we need to provide an answer as soon as possible. Thanks a lot for your time. Best regards.

5 9

Installing mailman3 from Ubuntu 20.04 repository
by Andy Cravens Aug. 24, 2021

Aug. 24, 2021

I’m testing Mailman3 on Ubuntu 20.04 and installing the packages from the default Ubuntu repo. I’m not sure I’ll perform the install this way once we move to production. I don’t know what group is responsible for keeping the Mainlam3 package in the Ubuntu repository up to date but I’d like to find out how committed that groups is to keeping the package current. We patch often and it would be convenient if the Mailman3 package is kept updated and current. If there is going to be some significant lag time I may decide to install manually when we go to production. Any thoughts on this? — Andy

3 2