Mailman 3 October 2016 - Mailman-Developers

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

Translation
by Simon Hanna 10 Jan '17

10 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

GNU Mailman Architectural Patterns & Quality Attributes for Research
by Stephen J. Turnbull 31 Oct '16

31 Oct '16

Hi Michael, Did you ever get an answer to this request? I broke a bunch of ribs on the 14th and have been pretty useless for the last two weeks, but now I have a chance to catch up on correspondence of less than "life or death" importance. Regards Steve Michael Skeen writes: > Hello GNU Mailman Community, > > > I am part of an undergraduate research group focusing on software > architecture patterns and quality attributes at Utah Valley University. We > recently analyzed the work published on GNU Mailman in the Architecture of > Open Source Applications <http://aosabook.org/en/index.html> (AOSA) and > referenced it in a paper we presented at the 13th Working IEEE/IFIP > Conference on Software Architecture (WICSA), as attached. As a part of our > continuing research we wish to validate our architectural analysis for GNU > Mailman with the current developers. > > > We would like to know if we are missing any patterns or quality attributes > that may have been included in GNU Mailman, or if there are any we listed > that aren’t used. Any additional comment on these topics you might have > would also, of course, be welcome. > > > We believe we found the following software architectural patterns in this > application: > > > * Pattern Name | Is This Found in the Architecture? (yes / no / don't know) > | Comments (optional)* > > Client Server Layers Master and Commander Pipes and Filters Shared > Repository Simple Repository > > Other? > > > We also identified the following quality attributes: > > > * Attribute Name | Is This Found in the Architecture? | Comments (optional)* > > Scalability Extensibility Performance Portability Reliability > > Other? > > > For your convenience, we have a complete list below of the patterns and > quality attributes we referred to when conducting our research. To clarify, > we are specifically studying architectural patterns, rather than design > patterns such as the GoF patterns. > > > Architectural Patterns Considered > > Quality Attributes Considered > > Active Repository > > Scalability > > Batch > > Usability > > Blackboard > > Extensibility > > Broker > > Performance > > Client Server > > Portability > > Event System > > Flexibility > > Explicit Invocation > > Reliability > > Implicit Invocation > > Maintainability > > Indirection Layer > > Security > > Interceptor > > Testability > > Interpreter > > Capacity > > Layers > > Cost > > Master and Commander > > Legality > > Microkernel > > Modularity > > Model View Controller > > Robustness > > Peer to Peer > > > Pipes and Filters > > > Plugin > > > Presentation Abstraction Control > > > Publish Subscribe > > > Reflection > > > Rule-Based System > > > Shared Repository > > > Simple Repository > > > State Based > > > Virtual Machine > > > > Please respond by October 25th, if possible. > > Thank you for considering our request, and for your continued work on GNU > Mailman. > > > Sincerely, > > > Michael Skeen, with > > Erich Gubler, > > Danielle Skinner, > > Brandon Leishman, > > Neil Harrison, Ph.D. (advisor) > > > Reference: Neil B. Harrison, Erich Gubler, Danielle Skinner, "Software > Architecture Pattern Morphology in Open-Source Systems",WICSA, 2016, 2016 > 13th Working IEEE/IFIP Conference on Software Architecture (WICSA), 2016 > 13th Working IEEE/IFIP Conference on Software Architecture (WICSA) 2016, > pp. 91-98, doi:10.1109/WICSA.2016.8 > > ---------------------------------------------------------------------- > PDF: external: PID4110571 (Morphology).pdf, PDF [fetch] > > ---------------------------------------------------------------------- > _______________________________________________ > 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/turnbull.stephen… > > Security Policy: http://wiki.list.org/x/QIA9

2 1

Re: [Mailman-Developers] Hyperkitty 1.0.3 doesn't have add_user_to_mailman function
by Mark Sapiro 30 Oct '16

30 Oct '16

On 10/30/2016 03:30 PM, Leon wrote: > Thank you. I have followed the > instruction(https://wiki.list.org/DOC/Mailman%203%20installation%20experien… > . urls.py, production.py and settings_local.py have been changed. I > got an ImportError. What did you do that produced this error? If it was in response to a command, exactly what command? And if you have installed in a virtualenv, was the virtualenv active when you gave the command? > Traceback (most recent call last): > > File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run > > self.result = application(self.environ, self.start_response) > > File > "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/contrib/staticfiles/handlers.py", > line 63, in __call__ > > return self.application(environ, start_response) > > File > "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/core/handlers/wsgi.py", > line 170, in __call__ > > self.load_middleware() > > File > "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/core/handlers/base.py", > line 50, in load_middleware > > mw_class = import_string(middleware_path) > > File > "/opt/mailman/mailman-bundler/eggs/Django-1.8.15-py2.7.egg/django/utils/module_loading.py", > line 26, in import_string > > module = import_module(module_path) > > File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module > > __import__(name) > > ImportError: No module named middleware > -- 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: [Mailman-Developers] Hyperkitty 1.0.3 doesn't have add_user_to_mailman function
by Mark Sapiro 30 Oct '16

30 Oct '16

On 10/27/2016 11:55 AM, Leon wrote: > Latest mailman-bundle, Hyperkitty==1.0.3, python-social-auth==0.2.21. > > https://gitlab.com/mailman/mailman-bundler/blob/master/mailman_web/producti… > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/mailman.py > > Im trying to implement a custom authentication backend by following a > tutorial. In the tutorial, the > version of hyperkitty is actually 1.0.4, and the whole thing works well. > However, it didn't work on top of 1.0.3. I can find this function in > commit 1755122c > https://gitlab.com/mailman/hyperkitty/commit/1755122c708abc96933142ca77dd0f… HyperKitty and Postorius have switched from using Persona and SocialAuth to using Django Allauth. Mailman bundler is not yet compatible with this. at a minimum you need to also install django-mailman3 and make config changes. See <https://wiki.list.org/x/17891998> for potentially helpful stuff. Also note, rather than posting a png screenshot of an error screen, it's much better to just copy/paste the text. And when mentioning that you are following a tutorial, it would help us if you provide a link to it so we can see what it says. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Hyperkitty 1.0.3 doesn't have add_user_to_mailman function
by Leon 27 Oct '16

27 Oct '16

Latest mailman-bundle, Hyperkitty==1.0.3, python-social-auth==0.2.21. https://gitlab.com/mailman/mailman-bundler/blob/master/mailman_web/producti… https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/mailman.py Im trying to implement a custom authentication backend by following a tutorial. In the tutorial, the version of hyperkitty is actually 1.0.4, and the whole thing works well. However, it didn't work on top of 1.0.3. I can find this function in commit 1755122c https://gitlab.com/mailman/hyperkitty/commit/1755122c708abc96933142ca77dd0f… -- Best wishes, Leon

1 0

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

25 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

Re: [Mailman-Developers] Setting up installation to test own changes
by Mark Sapiro 25 Oct '16

25 Oct '16

On 10/24/2016 07:00 AM, Ana Cutillas wrote: > > we at Systers had a student over summer work on some features and we would > like to put those in a server and do some testing. > > I was thinking of using the mailman bundler and then changing the source > files (she only did changes to postorius). Would that work? Or should we do > it differently? The recommended development setup is at <https://wiki.list.org/DEV/SetupDevEnvironment>. Mailman bundler is not recommended because it doesn't install the current development branches. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Issue recording VCR tapes in Postorius.
by Mark Sapiro 24 Oct '16

24 Oct '16

I have started a branch to expose the pending domain.alias_domains attribute in Postorius. I haven't yet done anything with tests, but I did the basic modifications and created <https://gitlab.com/mailman/postorius/merge_requests/186>. Of course, this merge failed CI because "create_domain() got an unexpected keyword argument 'alias_domain'". So I need to record a new tape and modify the test. So my problem is I can't record any tapes. My "tox -e record" attempts fail with tracebacks like the attached. It appears the virtualenv in .tox/record is a Python 3.5 virtualenv and Python 3.5 doesn't have a urllib2 module. Why is tox creating this as a Python 3 virtualenv? All the others it creates for Postorius are Python 2.7. I've even tried "tox -e record --force-dep 'python <=2.7'" but that doesn't help. Does anyone know what I need? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2