Mailman 3 December 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 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

Mailman 3.1 beta coming soon
by Barry Warsaw 13 Dec '16

13 Dec '16

Hello Mailman 3 users and developers! It's been a long slog but I think we are finally ready to begin the release process for Mailman 3.1. I am pretty happy about the state of the Core, and Florian is going to do some more integration testing with HyperKitty and Postorius. We still have a few issues and a merge proposal or two to address, but I am planning to spin a beta of Core this weekend to facilitate testing. Here is the Core's 3.1 milestone page: https://gitlab.com/mailman/mailman/milestones/2 If your favorite issue or merge request isn't on that list, please do get in touch. Otherwise it will be deferred to 3.2. I'm also not entirely promising I'll get to all of these; I really want to release 3.1 in 2016 so if we run out of time, it will get deferred. Here's the project-wide list of 3.1 issues: https://gitlab.com/groups/mailman/issues?scope=all&state=opened&utf8=%E2%9C… and merge requests: https://gitlab.com/groups/mailman/merge_requests?scope=all&state=opened&utf… Except that HyperKitty isn't on this list. Please do test whatever you can and let us know how it goes. Cheers, -Barry

6 12

Contributing to Mailman Core
by Nikhil Rayaprolu 09 Dec '16

09 Dec '16

Hello, I would like to contribute to mailman core . Can any one mentor me by picking some issues in core application which could make me understand the code structure. and also guide me through understanding the core module. I made two merge requests to postorius and read the documentation of maiman along with videos on mailman architecture by barry warshaw. Thank You -Nikhil Rayaprolu

1 0

Re: [Mailman-Developers] Whoosh Error during installation of hyperkitty
by Simon Hanna 06 Dec '16

06 Dec '16

On 12/06/2016 01:18 PM, Nikhil Rayaprolu wrote: > Thank you Simon, > your solution to the previous issue has solved it but unfortunately a > new error has arisen something like "Filter Error at /hyperkitty/ > /bin/sh: 1: sassc: not found" > > -Nikhil Rayaprolu When you follow a guide, please read the whole guide. There is a section included that instructs you to install a sass compiler. Which one you can install depends on the your OS. And please don't post pictures. You should include a text-only full trace. You can use images if you want to highlight some graphic issue... > > On 6 December 2016 at 17:21, Simon Hanna <simon.hanna(a)serve-me.info > <mailto:simon.hanna@serve-me.info>> wrote: > > On 12/06/2016 10:15 AM, Nikhil Rayaprolu wrote: > > I tried installing hyperkitty ,following the doc > > https://hyperkitty.readthedocs.io/en/latest/development.html > <https://hyperkitty.readthedocs.io/en/latest/development.html> . > but on > > opening the localhost:8000 on browser. > > NoReverseMatch at / >

1 0

Re: [Mailman-Developers] Whoosh Error during installation of hyperkitty
by Simon Hanna 06 Dec '16

06 Dec '16

On 12/06/2016 10:15 AM, Nikhil Rayaprolu wrote: > I tried installing hyperkitty ,following the doc > https://hyperkitty.readthedocs.io/en/latest/development.html . but on > opening the localhost:8000 on browser. > NoReverseMatch at / > > Reverse for 'hyperkitty.views.index.index' with arguments '()' and > keyword arguments '{}' not found. 0 pattern(s) tried: [] > > what would be causing the problem? Apply this patch until it gets merged into master https://gitlab.com/mailman/hyperkitty/merge_requests/42

2 1

Re: [Mailman-Developers] Error during installation of postorius
by Simon Hanna 06 Dec '16

06 Dec '16

On 12/06/2016 11:37 AM, Nikhil Rayaprolu wrote: > I tried installing the postorius , and on logging in I am facing an error > "SMTPRecipientsRefused at /accounts/login/" > what would be causing the problem? > on reading the docs I found that we should add the settings of postfix in > mailman.cfg file.but even on adding the settings , problem persist. > Thank You > -Nikhil Rayaprolu You are trying to send actual mail through postfix, and postfix can't send it because something is wrong about the address. If you are just trying to get a development setup up and running use the python builtin smtp server instead. "sudo python -m smtpd -n -c DebuggingServer localhost:25"

1 0

Error during installation of postorius
by Nikhil Rayaprolu 06 Dec '16

06 Dec '16

I tried installing the postorius , and on logging in I am facing an error "SMTPRecipientsRefused at /accounts/login/" what would be causing the problem? on reading the docs I found that we should add the settings of postfix in mailman.cfg file.but even on adding the settings , problem persist. Thank You -Nikhil Rayaprolu

1 0

Re: [Mailman-Developers] Whoosh Error during installation of hyperkitty
by Mark Sapiro 06 Dec '16

06 Dec '16

On 12/02/2016 11:55 PM, Nikhil Rayaprolu wrote: > Hello I am new to the Mailman community and on my try to contribute for > Mailman,I started installing all packages . For Hyperkitty I followed > https://hyperkitty.readthedocs.io/en/latest/development.html . Everything > went fine without any errors but on accessing the hyperkitty on my browser > , it shows me an error stating "A server error occurred. Please contact > the administrator." > and on the terminal the last 3 lines shows > > File > "/home/nikhil/dev/mailman/venv2/local/lib/python2.7/site-packages/django_haystack-2.5.1-py2.7.egg/haystack/backends/whoosh_backend.py", > line 30, in <module> > raise MissingDependency("The 'whoosh' backend requires the installation > of 'Whoosh'. Please refer to the documentation.") > MissingDependency: The 'whoosh' backend requires the installation of > 'Whoosh'. Please refer to the documentation. As it says at <http://hyperkitty.readthedocs.io/en/latest/development.html#setting-up-the-…>, "HyperKitty’s default configuration uses the Whoosh backend, so if you want to use that you just need to install the Whoosh Python library." pip install Whoosh -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Broken Gitlab Remote
by Simon Hanna 05 Dec '16

05 Dec '16

Hi, Just a quick warning: Do not use the online merge conflict resolver of GitLab. It can break your remote copy of the repository in a way that you can't fix yourself. And it looks like GitLab staff is not actually helping... I broke my Postorius remote https://gitlab.com/gitlab-com/support-forum/issues/1114 be careful, Simon

1 0