October 2023 - Mailman-users - lists.mailman3.org

Simple ubi8/mailman3 container image
by Jered Floyd 17 Oct '23

17 Oct '23

Abhilash maintains a very complete and well-documented container deployment for Mailman 3, but when I was setting up my environment a few months ago I wanted to build on top of RHEL 8 as well as use a database instance shared across multiple applications. So I ended up creating a bare-bones container image that suited my needs and was closer to just doing a simple local install, but keeping the isolation, reproducibility, and rollback benefits of running as a container. I've been meaning to polish it up and share in case it is useful to others, but finally recognizing that I likely won't get to that soon I've just put it on GitHub here: [ https://github.com/jeredfloyd/mailman-container | https://github.com/jeredfloyd/mailman-container ] Doing a "podman build" of this should result in a container image that is very much like the result of doing a venv install. This uses the Red Hat Universal Base Image (UBI), which can be freely redistributed, gets upstream security updates, and is eligible for support on a paid RHEL subscription. --Jered

1 0

ATT00001.txt file in Outlook users
by pau.baiges＠csuc.cat 17 Oct '23

17 Oct '23

Hello, Users who have Outlook receive an attached txt file with the name ATT00001.txt when they receive an email from a mailman3 list. Is there a way to stop it from sending this file? Thank you so much

2 1

Post installation issues (recipients refused) with Exim4 in a virtual host environment
by Kyriakos Terzopoulos 17 Oct '23

17 Oct '23

Hi, I have set up (I believe successfully) and configured the following in a Virtualhost environment (with HestiaCP): - A record for lists.mydomain.com - Venv - Mailman core - Mailman web (run migrate, collectstatic, compress, compilemessages) Postorius - gunicorn, hyperkitty - Nginx - SMTP exim4 conf I can see Posrorius and I have logged in and created my first mailing list: [image: Screenshot 2023-10-11 at 10.57.31 AM.png] My issue is that even though I have subscribed to my list as you can see above, I am not receiving the confirmation email. I get a "recipients refused" error. The smtp log for mailman is as follows: Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> recipients refused: {' kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu>\nUnrouteable address\nSender verify failed')} Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> smtp to testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 seconds Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> post to testlist(a)myproject.eu from testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu, 1667 bytes, 1 failures Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> delivery to kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification failed for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu>\nUnrouteable address\nSender verify failed' I have used the configuration for exim that is here <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> and I have also tested with the alternative approach that is documented in there. ------ Debug info follows: First, here is my installation directory: [image: image.png] The following are the services that are running successfully (albeit with some warnings): ------ *Mailman:* ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-10-05 12:32:08 EEST; 28min ago Process: 1563357 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Main PID: 1563364 (python3) Tasks: 18 (limit: 9255) Memory: 929.7M CPU: 22.818s CGroup: /system.slice/mailman3.service ├─1563364 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg ├─1563370 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─1563371 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─1563372 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─1563373 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─1563374 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 ├─1563375 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─1563376 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─1563377 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─1563378 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─1563379 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─1563380 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 ├─1563381 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 ├─1563382 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ├─1563420 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 └─1563421 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 Oct 05 12:32:07 hestia. mydomain.eu systemd[1]: Starting GNU Mailing List Manager... Oct 05 12:32:08 hestia. mydomain.eu mailman[1563357]: Starting Mailman's master runner Oct 05 12:32:08 hestia. mydomain.eu mailman[1563357]: Generating MTA alias maps Oct 05 12:32:08 hestia. mydomain.eu systemd[1]: *mailman3.service: Can't open PID file /opt/mailman/venv/master.pid (yet?) after start: Ope*> Oct 05 12:32:08 hestia. mydomain.eu systemd[1]: Started GNU Mailing List Manager. *Note the above warning for the master.pid file. However the file exists and is writeable* ------ *Mailman web service* ● mailmanweb.service - GNU Mailman Web UI Loaded: loaded (/etc/systemd/system/mailmanweb.service; disabled; vendor preset: enabled) Active: active (running) since Thu 2023-10-05 12:51:46 EEST; 9min ago Main PID: 1578503 (gunicorn) Tasks: 2 (limit: 9255) Memory: 67.2M CPU: 753ms CGroup: /system.slice/mailmanweb.service ├─1578503 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application └─1578505 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application Oct 05 12:51:46 hestia.mydomain.eu systemd[1]: Started GNU Mailman Web UI. Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! *WARNING: configuration file should have a valid Python extension*. Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! *Another warning above, however the service is starting normally.* ------ *Django Qcluster* ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; disabled; vendor preset: enabled) Active: active (running) since Thu 2023-10-05 12:51:40 EEST; 10min ago Main PID: 1578463 (mailman-web) Tasks: 8 (limit: 9255) Memory: 101.2M CPU: 30.915s CGroup: /system.slice/qcluster.service ├─1578463 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578465 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578466 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578467 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578468 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578469 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578470 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings └─1578471 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings Oct 05 12:51:40 hestia. mydomain.eu systemd[1]: Started HyperKitty async tasks runner. Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578463]: 09:51:40 [Q] INFO Q Cluster washington-solar-muppet-alanine starting. Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578466]: 09:51:40 [Q] INFO Process-1:1 ready for work at 1578466 Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578467]: 09:51:40 [Q] INFO Process-1:2 ready for work at 1578467 Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578468]: 09:51:40 [Q] INFO Process-1:3 ready for work at 1578468 Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578469]: 09:51:40 [Q] INFO Process-1:4 ready for work at 1578469 Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578470]: 09:51:41 [Q] INFO Process-1:5 monitoring at 1578470 Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578465]: 09:51:41 [Q] INFO Process-1 guarding cluster washington-solar-muppet-alanine Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578465]: 09:51:41 [Q] INFO Q Cluster washington-solar-muppet-alanine running. Oct 05 12:51:41 hestia.mydomain.eu mailman-web[1578471]: 09:51:41 [Q] INFO Process-1:6 pushing tasks at 1578471 ------ Nginx (hestia CP virtual hosts) server { listen 1.2.3.4:80; server_name lists.mydomain <http://lists.mydomain.com>.eu; location /static/ { alias /opt/mailman/venv/web/static/; } location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } ------ Happy to share my other mailman or EXIM4 configuration files if needed. Thanks in advance. Kyriakos ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Content-Type: image/png Name: =?UTF-8?B?U2NyZWVuc2hvdCAyMDIzLTEwLTExIGF0IDEwLjU3LjMx4oCvQU0ucG5n?= Replaced multipart/alternative part with first alternative.

3 8

Setting up on ubuntu server 22.04
by Kyriakos Terzopoulos 15 Oct '23

15 Oct '23

Hi guys, I have an Ubuntu 22.04 server running on a Hetzner machine, with HestiaCP (Exim4) on it. I cannot for the life of me start the service of mailman3 core. Following the installation tutorial I have tried with the venv approach and I am having the following issues: 1) It is not clear to me whether the mailman configuration should be outside venv (and outside the mailman shell). 2) For the above reason I have created a config file: /etc/mailman3/mailman.cfg and the mailman3 service outside venv. When starting the service I get the following: ImportError: cannot import name 'path' from 'importlib_resources' (/opt/mailman/venv/lib/python3.10/site-packages/importlib_resources/__init__.py) I've set up the database, the mailman user and the virtual environment. I know I am missing something here (e.g. Python version? other dependencies?). In general would it be better or/and easier to set this up on a new machine in my Hetzner cloud e.g. on Debian which seems to have packages of mailman available? Thanks in advance for all your help. Kyriakos

5 12

Memory usage cgroup and free -m
by golden_rock＠hotmail.com 12 Oct '23

12 Oct '23

Hi, Currently the mailman3 cgroup slice uses up to 875MB: Control Group Tasks %CPU Memory Input/s Output/s system.slice/mailman3.service 16 0.1 875.3M - - Is 875MB a normal expected amount, or more than expected? To confirm that this is truly used and not "cached", I use the new Available column from the "free -m" output, which is the pre-computed available memory for a new process, added in recent years. The output of free -m under the Available column when mailman3 is running is : 161 MB When I stop the mailman service, the output of free -m Available column goes up to: 1071 MB Showing that the 875MB previously were not available for release for new processes. If I start mailman service again, the output of free -m Available column goes back to : 325MB and will be reducing gradually over time. I looked around on posts, documentation and others, but didn't find guides related to reducing RAM usage, is that a possibility or is this memory usage expected?

2 1

Archive search failing on one list
by Mark 12 Oct '23

12 Oct '23

Hi, I have several lists all happily running with private archives. They all use the one domain name. A new list was added recently and although mail delivery and archiving are fine, this new list's search function is failing. For example, on searching for the word "Derbyshire" (which is mentioned in one of the archived messages) the results page displays: "Sorry no email could be found for this query." The logs show: +++++++++++++++++++++++++++++++++++++ /var/log/mailman3/web/mailman-web.log +++++++++++++++++++++++++++++++++++++ [pid: 1156|app: 0|req: 55/55] 2001:8004:5310:2405:ce66:5ff:41fc:60db () {76 vars in 1537 bytes} [Sat Sep 23 23:57:43 2023] GET /mailman3/hyperkitty/search?mlist=LISTNAME-1%40DOMAIN.COM&q=Derbyshire => generated 13752 bytes in 3188 msecs (HTTP/1.1 200) 5 headers in 164 bytes (1 switches on core 0) 23:57:51 [Q] INFO Process-1:1 processing [rebuild_mailinglist_cache_for_month] 23:57:51 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_recent] 23:57:51 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month mlist = MailingList.objects.get(name=mlist_name) File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get raise self.model.DoesNotExist( hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList matching query does not exist. +++++++++++++++++++++++++++++++++++++ On all the other lists, which all have successful search results, the logs shows examples like so (searching for "Farnborough") ... ************************************* [pid: 1156|app: 0|req: 486/486] 2001:8004:5310:2405:ce66:5ff:41fc:60db () {76 vars in 1531 bytes} [Sun Sep 24 00:38:24 2023] GET /mailman3/hyperkitty/search?mlist=LISTNAME-2%40DOMAIN.COM&q=Farnborough => generated 141638 bytes in 11039 msecs (HTTP/1.1 200) 6 headers in 333 bytes (1 switches on core 0) ************************************* ... which seems to be pretty much the same but with out the "MailingList.DoesNotExist" error. Any clues on where I should be looking to fix this would be gratefully received. Thanks, Mar

3 9

impossible to administrate *.com emails
by testeur 10 Oct '23

10 Oct '23

Hi, I don't understand why this problem ! In the web interface, i can't administrate email finishing with ".com" (ex : gmail.com, hotmail.com, etc) I obtain : "Forbidden You don't have permission to access this resource." did i miss something in the web configuration ? Regards, PG testeur

2 2

Alias for a list name
by Lars Bjørndal 08 Oct '23

08 Oct '23

I've migrated a list from mm 21 to mm 3 sucessfully. The mm 21 runs on domains managed by Postfix as virtual alias domains. That way it was possible to alias a shorter name for a list to the list name. To run mm 3 through Postfix, I use local_recipient_maps and transport_maps. What I want to achieve, is alias medlem(a)list.saf-org.no to saf-medlem(a)list.saf-org.no I tried to put medlem(a)list.saf-org.no: saf-medlem(a)list.saf-org.no and get the following error when running newaliases: postalias: warning: /etc/aliases, line 231: name must be local Is it possible to do this aliasing in a simple way? Thanks, Lars

2 6

OIDC (was: username)
by Jörg Schulz 07 Oct '23

07 Oct '23

The most recent version of Django-allauth has some nice changes, it's now straightforward to include oidc. Just include SOCIALACCOUNT_EMAIL_AUTHENTICATION=True ## This allows existing users to login MAILMAN_WEB_SOCIAL_AUTH = [ "allauth.socialaccount.providers.openid_connect"] in settings.py and use the Django admin to configure the socialauth.... While it is _possible_ to add things like ---- SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "mm3", "name": "TheNameThat shows up in the button", "client_id": "configuredID", "secret": "yourOIDCproviderGivesItToYou", "settings": { "server_url": "https://keycloak.wherever.com/realms/yourRealm/.well-known/openid-configura…", "token_auth_method": "client_secret_basic", }, } ] } } ---- I think it's preferable to do that within the Django Admin Gui. Does anybody dare to include this info in the documentation, or are we afraid the next django_allauth breaks things again (this time: Keycloak has been replaced by openid_connect)? -------- Weitergeleitete Nachricht -------- Betreff: Re: [MM3-users] Re: username Datum: Wed, 13 Sep 2023 07:34:35 +0000 Von: info(a)joergschulz.de An: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Hi, probably you are looking for https://django-allauth.readthedocs.io/en/latest/index.html and https://github.com/lokeish/django-all-auth-and-keycloak-integration but https://github.com/pennersr/django-allauth/commit/ab704687f438c06fd23e72bce… will be helpful once implemented. Am 12. September 2023 um 05:54 schrieb "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp <mailto:turnbull.stephen.fw@u.tsukuba.ac.jp?to=%22Stephen%20J.%20Turnbull%22%20%3Cturnbull.stephen.fw%40u.tsukuba.ac.jp%3E>>: bryan.kartzman(a)yu.edu writes: > Just to let you know, there is a maintained SAML2 plugin available > on github (https://github.com/grafana/django-saml2-auth) that I was > able to install and get to work with AZURE SSO. There are multiple ways to solve this problem. My employer wanted a host-wide solution so they chose Shibboleth. Some day I'll go out and collect the ones I can find and document them (in summary form: source site, recency of stable version, recency of maintenance, etc). Steve

1 0

username
by bryan.kartzman＠yu.edu 06 Oct '23

06 Oct '23

Where is the username that a user uses to login on the postorius web page stored? I checked the postgres table public.user and while the display name is there, the username is not. I can't find it anywhere in the database.

3 9