Mailman-Developers June 2020

mailman-developers@python.org

4 participants
7 discussions

before next release: disable backscatter in default installation
by Jo Rhett 07 Nov '22

07 Nov '22

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman works". We also object to having to teach people how to fix their mailman installations because it's not documented in the current manual. This is *exactly* like Sendmail 14 years ago. We didn't accept it then, and Sendmail fixed the problem. RESOLUTION: Mailman default installation should not backscatter in a default configuration. 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup. 2. Discard or hold messages from non-subscribers by default. I would think that it would be perfectly reasonable to have documentation on how to enable the 1980s-style -request / -subscribe etc aliases. However this documentation should have a note that this is against the AUP of nearly every network provider, and enabling it will likely cause them to get listed in various blacklists as a backscatter source. FYI: I know that this goes against the instincts of many old-time mailing list advocates here. But after dealing with a 10k/hour backscatter DoS my tolerance for this problem is understandably limited. Yes, it was a sweet day back in the 1980s. I was running a mailing list server and several UUCP gateways at the time, so I remember them well. But those days are past, and we need to deal with the reality of today. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

21 168

Mailman 2.1.34 released
by Mark Sapiro 26 Jun '20

26 Jun '20

I am pleased to announce the release of Mailman 2.1.34. This is a minor bug fix release and has updates to the Spanish i18n. See the attached README.txt for details. As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1 branch from the GNU Mailman project. There has been some discussion as to what this means. It means there will be no more releases from the GNU Mailman project containing any new features. There may be future patch releases to address the following: i18n updates. security issues. bugs affecting operation for which no satisfactory workaround exists. Mailman 2.1.34 is the fourth such patch release. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.34 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: Facing error while building mailman
by kelly.close＠lrewater.com 20 Jun '20

20 Jun '20

Hi! Would you be able to elaborate on "fixing my /etc/environment file to set the correct proxy thing..." ? I think I may be running into the same issue - have addressed all the other suggestions I can find for troubleshooting the 403 Forbidden error and still getting it. Thanks! ~Kelly

2 1

Affinity Mailman has reached beta status
by Brian Carpenter 18 Jun '20

18 Jun '20

Dear Mailman Developers Affinity Mailman is our new admin interface for Mailman 3 and we intend to use it to replace Postorius. It has been under development for about 3 months now and it recently reached beta. Calling For Beta Testers Now that Affinity is in beta, we are looking for list admins to help us beta test it. We are interested in getting some feedback and feature requests from beta users. If you are interested in helping us test out Affinity and get a sneak peek of the future of Mailman administration, then email me at brian_carpenter(a)emwd.com <mailto:brian_carpenter@emwd.com?subject=Affinity%20Beta&body=I%20am%20interested%20in%20Beta%20Testing%20Affinity> and I will begin the process of setting you up with an Affinity Mailman admin account and provide 2 test lists to use for beta testing purposes. While I am at it: Empathy Is Now Under Development "So what in the world is Empathy? I mean really - first Affinity and now Empathy?" That is correct. We figured if we are going to replace the default admin UI (Postorius) for Mailman 3, we might as well replace the default forum/archive UI (Hyperkitty) for Mailman 3. With Empathy, we are bringing a beautiful and user-friendly experience for those who wish to use Mailman 3 as a modern forum. We want Empathy to bring a true community like approach to the use of Mailman 3 via a browser. It will supplement the mailing list feature of Mailman 3 with an easy to use online forum. So Mailman 3 users will get the best of both worlds: a modern mailing list app AND a modern forum app. Empathy can also be used to display your list threads (archives) in an easy-to-read manner, and those threads can be categorized by tags and will be searchable. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

2 1

django-mailman3 1.3.4 bugfix release
by Abhilash Raj 05 Jun '20

05 Jun '20

Hey everyone, There was a critical bug reported yesterday which would cause users to get 404 pages instead of their list options page. Upon investigation, it was found that the bug was related to bumping of Mailman Core's API version to 3.1 in django-mailman3 1.3.3 release. Because this bug can cause problems accessing several pages in web interface, we have a quick bugfix release for you. If you have already upgraded to 1.3.3 and don't wish to do another upgrade/restart, you have an option to run the command below to avoid the bug: $ python manage.py clear_cache -a This should invalidate the cache entries which cause the 404 bug. The new release is available through PyPI at: https://pypi.org/project/django-mailman3/1.3.4/ The changelog is available at: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, as usual, you can update to the new release using pip: $ pip install django-mailman3==1.3.4 -- thanks, Abhilash Raj (maxking)

1 0

Disable Postorius
by Brian Carpenter 02 Jun '20

02 Jun '20

In our development work of Affinity, we are testing out the use of Hyperkitty. HK requires gunicorn but we can't get gunicorn to start because it is looking for a module name Postorius. I have Postorius commented out in settings_local.py and settings.py. Gunicorn still won't start. How can we start gunicorn without the need for having Postorius installed? -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

2 2

New releases
by Abhilash Raj 02 Jun '20

02 Jun '20

Hi Everyone, I am pleased to announce new stable releases for: - Postorius: 1.3.3 Changelog: https://docs.mailman3.org/projects/postorius/en/latest/news.html#id1 Download: https://pypi.org/project/postorius/1.3.3/ - Hyperkitty: 1.3.3 Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#id1 Download: https://pypi.org/project/HyperKitty/1.3.3rc1/ - Mailmanclient: 3.3.1 Changelog: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Download: https://pypi.org/project/mailmanclient/3.3.1/ - Django-mailman3: 1.3.3 Changelog: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Download: https://pypi.org/project/django-mailman3/1.3.3 Python 3.6+ and Django 2.0+ is supported for all of them. Django 3.0 support for Hyperkitty requires manually upgrading a dependency (django-haystack>=3.0b2, once a stable version of this has been released, it shouldn't require manually upgrading). There are tons of bug-fixes across the board and some new features. Biggest visible change is switch to Bootstrap 4, which has been long pending for us. Bootstrap 4 completely changes the CSS grid model using the new Flexbox. There might be some small changes or breakages when using on mobile. Please report such issues to us via Gitlab! Some other notable changes are in Postorius, which includes many more list settings exposed include content filtering settings, bounce processing (which was added in the previous release of Mailman Core) settings and some other ones. Settings page is also slightly different with all the sections on the vertical menu on left instead of horizontal tabs. You can now also specify a reason when rejecting held messages. There was also a gnarly bug, which caused the name of some members to be the string "None". For the longest time, I couldn't figure out the reason for it, but it ended up being a simple fix in mailmanclient's json serialization of display_name, which would result in Python's None value being passed as string "None" to Mailman's API for subscription. There is also better support for filtering visible lists based on the current vhost, which I see a few people are already waiting for from mailman-users list. A full changelog has been added to each project in the top. -- thanks, Abhilash Raj (maxking)

1 1

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers June 2020