We are currently testing latest mailman suite (w/Postorius 1.3.3) and notice that that the the API call /3.1/lists/listname.domain/roster/member failed when using "Unsubscribe all" on Postorius for a large list (~15000 members). Not sure whether the issue has been already reported or not.
I am currently running Mailman 3 with version 3.3.1 and in built
postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with
default values. I am almost running 2000 lists with 128 GB RAM and 24 Cores
on a single VM and on which all the mailman 3 components are running.
It is observed for most of the lists having members more than
500 is displaying "Mailman REST API not available. Please restart Mailman
Core" message on the postorius window and on running the CURL command over
REST API of Mailman it is reaching the time limit 30 seconds and showing
the below error.
*curl: (52) Empty reply from serverNo JSON object could be decoded*
The same behavior is observed on browsing the held messages for
few lists either through the browser or through CURL and REST API.
How to resolve this issue ? What other details I can provide to
make you get an idea ?
Thanks & Regards,
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. ;-)
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.
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.
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]
+cc: mailman-usersmailman3.org for more visibility.
On Sat, Jan 16, 2021, at 2:20 PM, Ruth Ivimey-Cook wrote:
> 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.]
> 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 on how to do that.
> > : 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/
Abhilash Raj (maxking)
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?
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.