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
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
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.
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.comEmwd.com
Hello,
is there a opportunity to avoid django fake users?
Because of it is not stopping, further and further fake users are subscribing.
Would be nice to have a possibility to stop this.
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]
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
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. ;-)
