Mailman 3 September 2016 - Mailman-Developers

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

08 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

Translation
by Simon Hanna 11 Jan '17

11 Jan '17

Hi, I just completed setting up the Mailman 3 projects on zanata.org They can be found here: https://translate.zanata.org/project/view/mailman https://translate.zanata.org/project/view/postorius https://translate.zanata.org/project/view/hyperkitty I'm hesitating to ask people to translate because zanata is really slow and I'm afraid of scaring people away from translating mailman in the future :D Anyhow, I'm writing to ask for your opinions. What do you think about zanata? Maybe you can try translating a couple of things and report how you feel about it. I stumbled across a few other open source solutions: https://translatewiki.net http://pootle.locamotion.org/ https://demo.weblate.org/ This mediagoblin issue discussed some alternatives when they switched away from transifex. https://issues.mediagoblin.org/ticket/913 There seems to be a pootle server run by gnu itself. https://chapters.gnu.org/pootle/ What do you think? Simon

4 9

Docker files for mailman
by Simon Hanna 18 Nov '16

18 Nov '16

Hi, I started working on docker files for Mailman. I created three repositories: - https://github.com/simonsmiley/postorius-docker Holds the files needed to create a postorius container - https://github.com/simonsmiley/mailman-docker Holds the files needed to create a core container - https://github.com/simonsmiley/mailman-compose Holds docker-compose files that greatly simply the process of running the containers * The mailman repo currently lacks documentation * Currently no emails can be sent. I still have to figure out what the best way is... * Hyperkitty will be added next (together with a complete "bundler" install) I pushed two images to the docker hub. Their names are thelinuxguy/postorius and thelinuxguy/mailman I created two organizations mailman on docker hub and gnu-mailman on github https://github.com/gnu-mailman https://hub.docker.com/u/mailman/ I know we shouldn't use github, but there is no way around github/bitbucket for automated builds on docker hub. I post here to inform you about the docker images and I also to ask if I'm allowed to keep these two organizations and move my images/repos there. I'll happily give push/owner access to additional people if requested. The repositories could be mirrored to the gitlab mailman group, sadly the process doesn't work the other way round just yet. In case this request gets denied, I'll just remove the organizations and let the images be "unofficial". cheers, Simon

2 1

Request to process merge requests faster
by Simon Hanna 26 Oct '16

26 Oct '16

Hi, I know all core devs are volunteers, and no one is maintaing the Mailman projects full-time, but it's a little frustrating to have your merge request open for a couple of months without any/much reaction to it... I try to keep my merge requests up to date and conflict-free, but having to do this for a couple of months, while there is no clear reason why it's not merged yet, is a little demotivating. In Postorius there have been (and there still are) merge requests by new contributors that were probably abandoned, because quite some time has passed since their creation... Simon

4 3

[X-POST] Regarding invition for Dev sprint of Pycon India
by Jaysinh Shukla 09 Sep '16

09 Sep '16

Respected Member, Dev Sprint is the best way to collaborate/guide other contributors physically rather than over IRC / email. We invite this community to join and hack for whole 3 days during the conference. Programmers are dreaming of contributing but they are unable to just because of lacking guidance. It will be a proud moment to mentor participants for whole three days and encourage them to be the active contributor for the project. Large contributing guidelines are always hard to digest. CFP is already started. We invite you to submit a proposal [here](https://in.pycon.org/cfp/dev-sprint-2016/proposals/). Schedule for Dev sprint [Pycon India, New Delhi](https://in.pycon.org) * Day-I: 23rd September 2016 - Full day * Day-II: 24th September 2016 - 5.00 PM to 9.00 PM * Day-III: 25th September 2016 - 5.00 PM to 9.00 PM Note: If you are reading this mail and you believe referring interested contributors will help to represent project well, feel free to drop me a mail. I will try to invite them individually. Many Thanks!

1 0