- Mailman-users - lists.mailman3.org

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

Finding a mailman3 installation description that works
by ralf.wiegand＠tena-sda.org April 1, 2020

April 1, 2020

WE are currently using mailman2. I have the task to setup and install a maiman3 server. Postfix is installed and working. Can anybody point me to a link where the actual installation is described using RHEL 7 or RHEL 8. This will be a hardened DISA compliant server, so I am trying to avoid installing compilers and tools that are not part of the standard RHEL 7 repos. Thank You, Best regards, Ralf Wiegand

3 4

Mailman3 moving to new server, not able to establish SMTP connection
by Andrew Hodgson March 28, 2020

March 28, 2020

Hi, Whilst we are all stuck in doors I have started a project to move Mailman3 from a Docker installation to a new server using a Python venv. Old server was Debian Jessie and the new one is Buster. Using Exim with stock config. Everything seems to be going ok but mail isn't delivering (cannot connect to SMTP server). I have /opt/mailman which I did chown -R list:list mailman.cfg has following MTA settings: [mta] incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 I wrote a Systemd unit which starts Mailman from the venv and started up Mailman once I got Postgres sorted so it would create the necessary files in the var directory structure. One thing I noticed and had to fix is that it doesn't creat the directories for existing lists, and the Exim config examples out there check for the existance of those directories to identify whether the address exists. I created those anyway and set ownership perms as before. Once I fixed that I sent a test message to the owner address and that routed correctly and the headers indicated the message was sent back to localhost by Mailman. However I can't get it to route a list message, here is a log showing the start of the Mailman master processes and me sending a test message from Outlook (so incoming mail is routing ok): Mar 28 16:03:20 2020 (21877) Master started Mar 28 16:03:32 2020 (21889) lmtp runner started. Mar 28 16:03:32 2020 (21896) virgin runner started. Mar 28 16:03:32 2020 (21887) command runner started. Mar 28 16:03:32 2020 (21890) nntp runner started. Mar 28 16:03:32 2020 (21886) bounces runner started. Mar 28 16:03:33 2020 (21892) pipeline runner started. Mar 28 16:03:33 2020 (21888) in runner started. Mar 28 16:03:33 2020 (21895) retry runner started. Mar 28 16:03:34 2020 (21894) rest runner started. [2020-03-28 16:03:34 +0000] [21894] [INFO] Starting gunicorn 20.0.4 [2020-03-28 16:03:34 +0000] [21894] [INFO] Listening at: http://127.0.0.1:8001 (21894) [2020-03-28 16:03:34 +0000] [21894] [INFO] Using worker: sync [2020-03-28 16:03:34 +0000] [21963] [INFO] Booting worker with pid: 21963 Mar 28 16:03:34 2020 (21885) archive runner started. [2020-03-28 16:03:34 +0000] [21965] [INFO] Booting worker with pid: 21965 Mar 28 16:03:34 2020 (21897) digest runner started. Mar 28 16:03:36 2020 (21891) out runner started. Mar 28 16:04:25 2020 (21888) ACCEPT: <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com> Mar 28 16:04:26 2020 (21885) HyperKitty archived message <AM0PR08MB39085771D0E2D9114FDE8E83AFCD0(a)AM0PR08MB3908.eurprd08.prod.outlook.com> to https://lists.hodgsonfamily.org/hyperkitty/list/blind-sysadmins@lists.hodgs… [28/Mar/2020:16:04:26 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org HTTP/1.1" 200 445 "-" "GNU Mailman REST client v3.3.0" Mar 28 16:04:27 2020 (21891) Cannot connect to SMTP server localhost on port 25 [28/Mar/2020:16:04:27 +0000] "GET /3.0/lists/blind-sysadmins(a)lists.hodgsonfamily.org/config HTTP/1.1" 200 2595 "-" "GNU Mailman REST client v3.3.0" [28/Mar/2020:16:04:27 +0000] "GET /3.0/users/andrew(a)hodgson.io HTTP/1.1" 200 439 "-" "GNU Mailman REST client v3.3.0" Now in the out queue I have this: root@elrond:/opt/mailman# ls -la /opt/mailman/var/queue/out total 32 drwxrwx--- 2 list list 4096 Mar 28 16:34 . drwxr-xr-x 14 list list 4096 Mar 28 13:25 .. -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.2412584+390ab148e589108ed9e849445e5e90410f69def3.bak -rw-rw---- 1 list list 11152 Mar 28 16:34 1585413255.4891446+75bde47331619263b05f582c28ceb85a13bb5265.pck.tmp There is no connection attempt in the Exim log from Mailman and I can connect to localhost:25. This is a dualstack machine and I was wondering whether we had any IPV6 issues (I had an issue with Gunicorn and Nginx routing traffic due to this earlier that I had to sort), but as owner addresses are working I don't know what is different on that. Any suggestions? Thanks. Andrew.

1 1