- Mailman-users - lists.mailman3.org

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

Uncaught runner exception
by Wolfgang Bock April 7, 2020

April 7, 2020

Hello, I need your help. I got a "Uncaught runner exception: invalid literal for int() with base 10:" Referring to a discussion in Sept. 2019 with Manos Pitsidianakis "Cannot connect to SMTP server localhost on port 25" I did following: stop both postfix and mailman 3 services. Deleted all files in the /var/lib/mailman3/queue directories. Restarted both services. With following configurations: (extracts): /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: Tried with 127.0.0.1/localhost/server ip or FQDN=servername smtp_port: (got a "cannot connect to SMTP Server on port 25") so I let this item empty ... smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 configuration: python:mailman.config.postfix /var/log/postfix/mail.info Apr 6 00:02:22 ... postfix/postfix-script[31407]: starting the Postfix mail system Apr 6 00:02:22 ... postfix/master[31409]: daemon started -- version 3.4.8, configuration /etc/postfix Apr 6 00:03:09 ... postfix/smtpd[31462]: connect from mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... policyd-spf[31468]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=80.241.56.161; helo=mout-p-103.mailbox.org; envelope-from=[mail address]; receiver=<UNKNOWN> Apr 6 00:03:09 ... postfix/smtpd[31462]: D29FE138023E: client=mout-p-103.mailbox.org[80.241.56.161] Apr 6 00:03:09 ... postfix/cleanup[31471]: D29FE138023E: message-id=<6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: from=<[mail address]>, size=2811, nrcpt=1 (queue active) Apr 6 00:03:25 ... postfix/smtpd[31462]: disconnect from mout-p-103.mailbox.org[80.241.56.161] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Apr 6 00:03:25 ... postfix/lmtp[31481]: D29FE138023E: to=<[list address]>, relay=127.0.0.1[127.0.0.1]:8024, delay=16, delays=16/0.01/0/0.1, dsn=2.0.0, status=sent (250 Ok) Apr 6 00:03:25 ... postfix/qmgr[31411]: D29FE138023E: removed /var/log/mailman3/mailman.log Apr 06 00:02:12 2020 (31148) Master started Apr 06 00:02:13 2020 (31158) rest runner started. Apr 06 00:02:13 2020 (31150) archive runner started. Apr 06 00:02:13 2020 (31159) retry runner started. Apr 06 00:02:14 2020 (31161) virgin runner started. Apr 06 00:02:14 2020 (31154) lmtp runner started. Apr 06 00:02:14 2020 (31155) nntp runner started. Apr 06 00:02:14 2020 (31153) in runner started. Apr 06 00:02:14 2020 (31151) bounces runner started. Apr 06 00:02:15 2020 (31157) pipeline runner started. Apr 06 00:02:15 2020 (31152) command runner started. Apr 06 00:02:15 2020 (31162) digest runner started. Apr 06 00:02:16 2020 (31156) out runner started. Apr 06 00:03:26 2020 (31153) ACCEPT: <6a504834-123a-60f6-3a0e-494623b74523(a)mailbox.org> Apr 06 00:03:26 2020 (31156) Uncaught runner exception: invalid literal for int() with base 10: '' Apr 06 00:03:26 2020 (31156) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 77, in deliver agent = BulkDelivery(int(config.mta.max_recipients)) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 50, in __init__ super().__init__() File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 45, in __init__ config.mta.smtp_host, int(config.mta.smtp_port), Any hints how to solve the problem?? Regards Wolfgang

2 4

Protocol version
by David Krantz April 5, 2020

April 5, 2020

Hi. I have the following displayed when I look at the "System Information" in Postorius: Mailman Core Version GNU Mailman 3.3.0 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.7.6 (default, Dec 19 2019, 23:49:42) [GCC 5.4.0 20160609] What surprises me is the protocol version. I have tried to set the protocol version to 3.1 in mailman core (which should be the latest according to the documentation) and restarting both core and web but that gives no effect. Normally I have not had any protocol version defined. Everything seems to work just fine but something is strange, either the documentation, my setup or mailman/postorius. // David

1 1

Postorius confirmation mails shown in uwsgi-error.log but not sent
by Ralph Seichter April 4, 2020

April 4, 2020

I have struggled for hours but cannot seem to figure it out. After registering new user accounts in Postorius, the "confirm your address" emails don't get sent via SMTP (my MTA does not even log connection attempts), but their content is displayed in uwsgi-error.log. I think I disabled developer mode in Core and Postorius: $ mailman conf | grep devmode [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s $ grep ^DEBUG settings.py DEBUG = False Users can subscribe via list-join(a)domain.tld, including confirmations. Account registration using the WebUI works as well, it's just the emails that don't get sent. What am I missing, I wonder? -Ralph

3 10