- Mailman-users - lists.mailman3.org

Changing web access
by Ralf Wiegand April 22, 2020

April 22, 2020

Hello Members, I am testing mailman3 in a test environment. python manage.py runserver Performing system checks... System check identified no issues (0 silenced). April 22, 2020 - 14:13:57 Django version 2.2.12, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C. tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 6497/python tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 6404/python How can I change this to have access from any host on my local network. The server running mailman3+hyperkitty+postorius is a rhel7 server without a GUI interface. I also need to give access to our developer on the same subnet. Thank You, Best regards, Ralf Wiegand

3 5

Can't open PID file after start.
by Torge Riedel April 22, 2020

April 22, 2020

Hi, today there were some package upgrades on my server for python3. Just to be safe I did a "systemctl restart mailman" afterwards. Calling "systemctl status mailman" gave me the following output: mailman.service - GNU Mailing List Manager Loaded: loaded (/opt/mailman/core/mailman.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-04-22 07:01:30 CEST; 6s ago Process: 24178 ExecStop=/opt/mailman/core/bin/mailman.sh stop (code=exited, status=0/SUCCESS) Process: 24180 ExecStart=/opt/mailman/core/bin/mailman.sh start (code=exited, status=0/SUCCESS) Main PID: 24182 (python3) Tasks: 13 (limit: 2335) CGroup: /system.slice/mailman.service ├─24182 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg ├─24185 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=archive:0:1 ├─24186 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=bounces:0:1 ├─24187 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=command:0:1 ├─24188 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=in:0:1 ├─24189 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=lmtp:0:1 ├─24190 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=nntp:0:1 ├─24191 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=out:0:1 ├─24192 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=pipeline:0:1 ├─24193 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 ├─24194 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=retry:0:1 ├─24195 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=virgin:0:1 └─24196 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=digest:0:1 Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file /opt/mailman/var/master.pid (yet?) after start: No such file or directory Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. Should I treat the PID message as an info or is it an error and something is now broken? The file is there (content is 24182) and timestamp is from the time where I restarted mailman. Best Torge

2 2

Different Mail Domain Cause Key Error
by Brian Carpenter April 22, 2020

April 22, 2020

I have a client that requires his list address to be list(a)domain.com. But since he is using domain.com for an external website, he has to access his list via Postorius using list.domain.com. So here is what I did: Django Admin Add Site: list.domain.com Add Mail Domain: domain.com (Site selected is list.domain.com) Postorius Add Domain: Mailhost is domain.com. Web Host is list.domain.com (list.domain.com) I have list.domain.com listed in the allowed hosts in settings_local.py. I even added domain.com there as well. When I try to access Postorius using list.domain.com I get a "An error occurred while processing your request." message and the logs shows the dreaded: ``` 'Internal Server Error: /mailman3/lists/ KeyError at /mailman3/lists/ 'file' ``` Did I miss a step here? Thanks, Brian

3 6

MM3 gateway errors and frequent reboot needs
by hansen＠rc.org April 22, 2020

April 22, 2020

We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? Please advise. PS: My old MM2 installation could (and did) run without any help. Not so with MM3.

4 3

Mailman Core 3.3.1 release
by Abhilash Raj April 19, 2020

April 19, 2020

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

1 0

Extract posts into mbox file
by Andrew Bernard April 18, 2020

April 18, 2020

Where are the posts stored in the database? What tables? How would on go about exporting them into mbox format for the complete set?

3 2

Recommended way to backup a mailman3 instance
by Gilles Filippini April 18, 2020

April 18, 2020

Hi, I'd like to schedule periodic backup for our mailman3 instance. Are there recommended ways for doing this without down times? Thanks in advance, _g.

4 12

Is a directory: '…/mailman/templates'
by Stefan Tatschner April 14, 2020

April 14, 2020

hey folks, I am struggling with my mailman server for quite some time now. I am on 3.3 and the out runner cannot sent emails any more. According to this issue [1] I found out--by logging the exception as well--, that mailman has this problem: Mar 31 09:34:51 2020 (71057) ACCEPT: <c1e4aa1be5b61c289c69a66a6d55565333d5a35b.camel(a)rumpelsepp.org> Mar 31 09:34:52 2020 (71079) Cannot connect to SMTP server 127.0.0.1 on port 25: [Errno 21] Is a directory: '/usr/lib/python3.8/site-packages/mailman/templates' What the hell is going on here? ☹︎ any ideas what's wrong? The runner doesn't try to connect to postfix, since it fails with a strange template error. Stefan [1]: https://gitlab.com/mailman/mailman/-/issues/514

5 6

Mailman Core 3.3.1rc1 release
by Abhilash Raj April 10, 2020

April 10, 2020

Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. -- thanks, Abhilash Raj (maxking)

2 1

SMTPAuthenticationError at /accounts/login/
by mmasoudf＠aaas.org April 9, 2020

April 9, 2020

I have setup the stack according to: Mailman Suite Documentation. Release 3.3 PDF file. I configured EMAIL_HOST_USER and EMAIL_HOST_PASSWORD in Django settings.py. I could not find the place that I might configure it for Postfix and , sort of logically, I get the following error: SMTPAuthenticationError at /accounts/login/ I can see that it tries the user name and password I configured in settings.py (EMAIL_HOST_USER , EMAIL_HOST_PASSWORD). When I try to access the site through the web. I can login as admin, but not as any other user. I am running the site on AWS and to be able to use AWS mail-servers I have to define following parameter for AWS: smtp_sasl_password_maps which points to a hash for AWS 'ACCESS KEY ID' and 'SECRET ACCESS KEY' Any idea is highly appreciated.

3 2