Mailman-Developers January 2017

mailman-developers@python.org

10 participants
19 discussions

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

Re: [Mailman-Developers] Mailman 3 Dockerfile
by Simon Hanna 27 Jan '17

27 Jan '17

On 26 January 2017 17:32:48 GMT+01:00, Stephan Wehner <stephanwehner(a)gmail.com> wrote: >I've been working with the Dockerfile at > >https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > >for setting up Mailman 3. > >The page doesn't say who to contact. > >Is this mailing list a good place to ask questions about where I'm >stuck? > >Stephan I guess you can ask here. I wrote a couple of docker files that were mainly intended for testing/demoing. It really depends on what you want to do with the containers and how (if) you want to deploy them. I still haven't figured out a way to connect Mailman to an "outside" postfix. Please note that mailman-bundler currently doesn't produce a usable environment. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

2 2

Re: [Mailman-Developers] Mailman 3 Dockerfile
by Terri Oda 27 Jan '17

27 Jan '17

Well, my name is all over it so I'm not sure it's true that there's no more obvious contact person than this list... But this list is the correct place, yes. :) I think we have a few better dockerfiles out in the community now, so maybe folk who've set them up would like to chime in? Terri On January 26, 2017 8:32:48 AM PST, Stephan Wehner <stephanwehner(a)gmail.com> wrote: >I've been working with the Dockerfile at > >https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > >for setting up Mailman 3. > >The page doesn't say who to contact. > >Is this mailing list a good place to ask questions about where I'm >stuck? > >Stephan >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers(a)python.org >https://mail.python.org/mailman/listinfo/mailman-developers >Mailman FAQ: http://wiki.list.org/x/AgA3 >Searchable Archives: >http://www.mail-archive.com/mailman-developers%40python.org/ >Unsubscribe: >https://mail.python.org/mailman/options/mailman-developers/terri%40toybox.ca > >Security Policy: http://wiki.list.org/x/QIA9

2 1

Mailman 3 Dockerfile
by Stephan Wehner 26 Jan '17

26 Jan '17

I've been working with the Dockerfile at https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile for setting up Mailman 3. The page doesn't say who to contact. Is this mailing list a good place to ask questions about where I'm stuck? Stephan

1 0

Re: [Mailman-Developers] About Mailman 3.1 release date
by Barry Warsaw 13 Jan '17

13 Jan '17

Hi Ruben, On Jan 13, 2017, at 04:08 PM, Ruben Ibanez wrote: >From our organization we are really looking forward for the coming 3.1 >release of Mailman as we would like to migrate our current Mailman 2.1. We >are looking that in your git page >https://gitlab.com/mailman/mailman/milestones/2 the progress is at 98%, so we >hope it will be ready in the coming days. Great! I should point out this this milestone technically only describes Core. A potentially more comprehensive overview for the entire suite is at: https://gitlab.com/groups/mailman/milestones/31?title=3.1 but TBH, I'm not sure whether Postorius and HyperKitty are as slavishly focused on milestoning as I am for Core. ;) >Regarding this, when the new 3.1 version is finished, will it be in a 'Beta' >phase, or directly a public release? Beta 2 of Core is already available on PyPI: https://pypi.python.org/pypi/mailman/3.1.0b2 >In the case of being a Beta release, do you know an estimate time of when it >will became fully released? The last major feature for 3.1 Core is done (DMARC mitigation) so we just have a few more minor issues to pick off. Mark Sapiro is already running all the git HEADs on lists.mailman3.org so we're essentially testing integration in production already. We need to concentrate on finishing Postorius and HyperKitty (and mailmanclient, but that should be easy). It doesn't look like a ton of work, but it probably could use some well-placed help here and there. I can't give you an ETA, but once Core is at 100% milestone, I'll release it as an RC, and then jump over to the other projects to help. I do think we're close enough for folks to start using it in anger, and more importantly, providing feedback, bugs, and code. Cheers, -Barry

1 0

About Mailman 3.1 release date
by Ruben Ibanez 13 Jan '17

13 Jan '17

Dear Mailman Developers, >From our organization we are really looking forward for the coming 3.1 release of Mailman as we would like to migrate our current Mailman 2.1. We are looking that in your git page https://gitlab.com/mailman/mailman/milestones/2 the progress is at 98%, so we hope it will be ready in the coming days. Great! Regarding this, when the new 3.1 version is finished, will it be in a 'Beta' phase, or directly a public release? In the case of being a Beta release, do you know an estimate time of when it will became fully released? Many thanks! Regards, RI ------------------------------------------------------------------ Aurora Technology B.V. for ESA - European Space Agency Ruben Ibanez Computer Engineer / System Analyst Sciops technical IT Unit - SITU Data and Engineering Division Operations Department, Directorate of Science European Space Astronomy Centre (ESAC) European Space Agency (ESA) Camino bajo del Castillo s/n, Urb. Villafranca del Castillo P.O. Box 78 - 28691 Villanueva de la Cañada, Madrid, Spain ribanez(a)sciops.esa.int | www.esa.int | T +34 91 81 31 518 ------------------------------------------------------------------ ----- This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.

1 0

Developer Introduction
by Abhishek Shrivastava 13 Jan '17

13 Jan '17

Namaste Developers! I am Abhishek Shrivastava, from India. After lurking around in the mailman list for over a year now, I want to start contributing to the project. I'd love to get involved with mailman core and postorius. Currently I am setting up my development environment and going through the mailman architecture document http://aosabook.org/en/mailman.html. I am also looking through the issue tracker for beginner friendly bugs to fix. Regards, Abhishek Shrivastava

1 0

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

Re: [Mailman-Developers] Reg: Writing tests for Mailman modules
by Barry Warsaw 08 Jan '17

08 Jan '17

On Jan 07, 2017, at 07:38 PM, Siddhartha Gairola wrote: >To get familiar with the code I wiould like to write some tests for mailman. >Which module should I get started with? Also some prototypes for writing >tests would be helpful. One of the most useful things for Core would be to help boost coverage. Many of the core modules are covered at 100% but a lot of them aren't. Right now the test suite is gated at 93% overall, but you can see that some are dismal at < 90% (even 40% in one case!). I will gladly work with anybody who wants to help boost coverage toward the eventual goal of 100% coverage. Untested code is broken code! The best way to see coverage information is to run this with a checkout of Core: % tox -e py35-cov Adjust if necessary if you don't have Python 3.5 installed (i.e. py36-cov and py34-cov are also available). I'm very happy to answer questions about how to write tests, the testing infrastructure, etc. either here on this mailing list or on IRC. Cheers, -Barry

1 0

Reg: Postorius Issue 127
by Stephen J. Turnbull 07 Jan '17

07 Jan '17

Siddhartha Gairola writes: > So this is what we have to implement for postorius - > "if the post is from a moderated member, the moderator has a checkbox to > clear the member's moderation when accepting the post." Right. > But I am not too sure how to get this done. I guess it would require > modifying some controller. > If I could get some assistance on this, I would be grateful. Postorius is implemented as a Django application, and Django uses a modified MVC model. So you should be prepared for all of model (model), view (template), and controller (view) to be involved (in parens Django terms, outside MVC terms, somewhat stretched as necessary in Django). Model: since the user's moderation bit is already set, it must be present. Since you're just asked to clear it, which is a normal operation for bits, probably no change to model is needed. Template: implements checkbox formatting. Needs change. View: implements checkbox toggling and communication with model. Needs change. To find template, go to template directory (use find(1) or GUI equivalent on your platform), look through templates to find moderation page(s) (there may be more than one). To find code, grep through views for one which invokes that template. Don't promise this will get you what you want, but that's the way I would start. Gotta do other work now, back tomorrow evening (> 06:00 UTC). Steve

2 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 January 2017