- Mailman-users - lists.mailman3.org

Easiest way to install a new mailman3 deployment?
by ieso＠johnwillson.com Jan. 18, 2021

Jan. 18, 2021

So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time. I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner. A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test. The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front. Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?) Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-)

15 25

Mailman 3 Installation
by bruce.dubbs＠gmail.com Jan. 17, 2021

Jan. 17, 2021

I am trying to set up Mailman 3 on a new server. So far I have run: pip3 install Django==3.1.5 pip3 install postorius pip3 install Hyperkitty pip3 install mailman pip3 install uwsgi All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? I think I can follow the instructions to set up postfix. In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. I would appreciate advice or a pointer to where I can figure this out. Thanks. -- Bruce

4 5

New release candidates for Postorius and Hyperkitty
by Abhilash Raj Jan. 17, 2021

Jan. 17, 2021

Hey Everyone, Happy new year to everyone! I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! These include both new features and bug fixes. Complete change log for each components: Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst These releases require Mailman Core 3.3.2 and Python 3.6+. Since these are pre-releases, you can install them using: $ pip install --pre --upgrade postorius hyperkitty Or you can also specify the exact versions: $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. [1]: https://docs.mailman3.org/en/latest/translation.html -- thanks, Abhilash Raj (maxking) On behalf of GNU Mailman Team

1 1

subscribing to any list is not possible
by r.woithe＠callassoftware.com Jan. 17, 2021

Jan. 17, 2021

Hello, after i solved the qcluster error with a new installation i have still an error with subscribing. It is not possible to subscribe to any list via email or web-interface. The mass subcribtion as admin via the web-interface is possible and the unsubscribing also. But i can not get any error messages in any log file, nothing. Also the django users are fine, django users can subscribe without a problem. But subscribing to any list is not possible via the web-interface, with the error message "A Server Error occured please conntact the Administrator",also subscribing via email is not possible(mail.log is fine the mail is delivered), but there is no additionally error message in any log file. System: ubuntu 20.04.01 Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.0 Mailman Core Python Version 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0]

2 4

Re: New release candidates for Postorius and Hyperkitty
by Abhilash Raj Jan. 16, 2021

Jan. 16, 2021

+cc: mailman-usersmailman3.org for more visibility. On Sat, Jan 16, 2021, at 2:20 PM, Ruth Ivimey-Cook wrote: > Hi, > > Is there a recommended method for upgrading an existing, running, server > from Python 3.6 to 3.8, especially in such a way as to enable downgrade > if something breaks? It depends on how did you install Mailman. If you installed using virtualenv, you can create another virtualenv and install new versions, that use the same configuration and switch between new and old versions, > > [When I upgraded a server distribution without enough preparation, it > broke mailman3 because I lost python3.6, and getting it working again > needed a lot of work to reinstall it without zapping needed state.] > > Regards > > Ruth > > > On 16/01/2021 20:38, Abhilash Raj wrote: > > Hey Everyone, > > > > Happy new year to everyone! > > > > I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! > > > > These include both new features and bug fixes. Complete change log for each components: > > > > Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > > > Since these are pre-releases, you can install them using: > > > > $ pip install --pre --upgrade postorius hyperkitty > > > > Or you can also specify the exact versions: > > > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > > > Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. > > > > If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. > > > > [1]: https://docs.mailman3.org/en/latest/translation.html > > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > > -- thanks, Abhilash Raj (maxking)

1 0

Subscription request cannot be moderated: 404 Not Found
by Eric Broens Jan. 16, 2021

Jan. 16, 2021

For one of our mailinglists we also have a problem with accepting a subscription request. When Clicking "Accept", we get a 404 Not found error. See the attached screenshot. Is there a way to solve this? Best Regards,Eric

2 8

Mailman 'requests' API call timeout when there are a number of pending members
by Alan So Jan. 15, 2021

Jan. 15, 2021

We are currently testing latest mailman suite and notice that the requests API call will timeout if there are a number of pending requests. Since the latest Postorious allow unchecking Pre confirm and Pre approved during mass subscribe, our support staff tried to add large number of email addresses to the list. We then found that we cannot click into the list from the web UI to administer it and an error message showing that "Mailman REST API not available. Please start Mailman core." Further checked that the requests API call failed to complete when we click the list on the web interface. Looks like the UI should not try to load all the pending members just for the sake of showing the number of pending requests. Of course in normal situations, there should not be that many pending requests.

2 1

Re: Mails for 1 specific mailinglist not being send and looping in out queue
by Eric Broens Jan. 14, 2021

Jan. 14, 2021

In my mailclient it looks like the LF's have been removed. I'll attach the log extracts to make them better readable. Best Regards, Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote: ----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail. The mailman3 error log show that there is a connection failure to port 25. A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail. Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail. Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either. For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue? Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 3

Header Filter madness
by Brian Carpenter Jan. 14, 2021

Jan. 14, 2021

I have a client whose header filters seemed to have stop working. No matter what I try, it seems none of their header filters are being applied. Other lists on the same server that use header filters, are working fine. This particular header is the subject header. I can duplicate their problem but only with their list. If I create the exact same header on a test list using the exact same subject line, the header filter does its job (moderate). Just not with this one list. -- Brian Carpenter Harmonylists.com Emwd.com

2 7

The future is here?
by ieso＠johnwillson.com Jan. 9, 2021

Jan. 9, 2021

In my quest to figure out how even us idiots can successfully install a mailman3 server, I keep looking ways to reduce the process to the simplest possible set of instructions. So far, I haven't been doing very well with that, but I've been learning a ton. In particular, while I still haven't got a fully functioning mailman3 server yet, someone pointed me, off list, to Ansible, which I wasn't aware of before and which has completely blown me away by its power and simplicity. For those who aren't aware of it, it's an agentless, multi-platform automation technology. For our purposes, it replaces "how to install mailman3" guides with a single script that aims to actually do the entire thing for you. One of the particularly interesting points is that you can write complex scripts/data structures (or 'collections') that allow for a single collection to cover a broad range of use cases, such as [this person's](https://github.com/rivimey/) exim Ansible collection, which covers 3 very different use cases from a private domain email relay up to a full multi-domain email handler with IMAP integration. I haven't quite got the mailman3 one working yet, but I've just started playing with it. Here are some pointers in case anyone else is interested in trying, and I'd be very interested in whether or not I'm actually the last person to discover this technology, and if one of these solutions succeeds in delivering mailman3 "out of the box". 1. [Install Ainsible](https://docs.ansible.com/ansible/latest/installation_guide/intro_…, make sure you're on at least version 2.9, if not 2.10. Some distributions are still on 2.7, which is not compatible with more recent collections. The "Galaxy" collection is apparently only tested on Debian 10. 2. Pick your mailman3 Ansible collection of choice and install it (https://galaxy.ansible.com/ucr/mailman3, or https://github.com/rivimey/ansible-mailman3) Command to install official collection - ansible-galaxy install ucr.mailman3 3. Write playbook.yml with key variables (mailman3 example below) _________________________ mailman3-playbook.yml _________________________ - hosts: mailman3 vars: mailman3_domain: example.com # It will install and create a certificate using certbot, its nignx plugin and http validation (Public IP required). If false, it will install a self sign cert mailman3_install_certbot: true # install and create certificate # secrets, please change them mailman3_secret_key: "change_secretkey" mailman3_rest_api_pass: "change_api_pass" mailman3_archiver_key: "change_archiver_key" mailman3_db_pass: "change_db_pass" mailman3_web_db_pass: "change_web_db_pass" mailman3_web_admin_pass: "change_web_admin_pass" roles: - ucr.mailman3

6 13