April 2020 - Mailman-users - lists.mailman3.org

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

Loads of postgres requests: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" ...
by Gilles Filippini April 9, 2020

April 9, 2020

Hello, I run a small mailman3 server (6 lists, less than 100 users), and I can't access anymore to the administration web page for one of these lists: > Something went wrong > Mailman REST API not available. Please start Mailman core. The other lists seems OK. Looking at the postregsql logs I see a full load of these requests (4 to 5 per second!): LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2020-04-09T07:57:37.828200+00:00'::timestamptz) LIMIT 1 Any clue appreciated. Many thanks in advance, _g.

2 2

Re: Uncaught runner exception
by Wolfgang Bock April 9, 2020

April 9, 2020

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 8

Outgoing STMP services? IP reputations?
by Seth Seeger April 7, 2020

April 7, 2020

Hello everyone, Forgive me if this is the wrong list. I’m curious to hear what users are doing for MM3 hosting and what you are using for outgoing services. I am hosting a Mailman3 installation for a community that I am part of, and we have 6 lists which generated 136,000 outgoing emails last month. I’m currently hosting this on a 2-core 4GB RAM EC2 (t3a.medium) instance at Amazon. I went with Amazon because their outgoing email relay (SES) is free for the first 62,000 emails/month. (I didn’t do my homework - I thought that would be plenty!) I’d much rather be hosting on Linode, since their setup is waaaaay simpler and easier to understand. I went with an SMTP service so that I wouldn’t have to deal with managing an IP address reputation…. (Any other SMTP relay service besides the Amazon SES/hosting would cost >$80/month.) Do you use an SMTP relay service? Do you just send directly from your VM’s IP address? Do you have trouble with getting black listed? What have you done about your IP address reputation? Is DKIM and SPF enough to get past an IP address without an established reputation? Thank you! Seth

3 2