Mailman 3 February 2019 - 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

Regarding aquaintance with community and source code
by Satbir Singh Ghai 06 Apr '19

06 Apr '19

Hello, I am Satbir Singh, a sophomore pursuing B.Tech in Information and Communication Technology at DA-IICT. I am a full stack web developer proficient in Django Framework. I want to contribute to Mailman. I am aiming for GSoC 2019. I have previously contributed to open source organizations and really excited to contribute in this project. I am new to this organization please help me to get started! Thanking you Satbir Singh

2 2

GSoC deadlines approaching fast!
by Stephen J. Turnbull 27 Feb '19

27 Feb '19

Hey all We need to decide if we're going to go under the PSF umbrella or if we want to go standalone. The real advantages to the standalone are two tickets (most expenses paid by Google) to the Mentor Summit, and the $500/student gift to Mailman. But it's more work and lower chance of acceptance. For PSF, we need to have project and idea pages up by Monday IIRC. I think Google's deadline is a couple days later. Steve

3 5

(Maybe) misconfigured docs.mailman3.org DNS & SSL
by Ye Xiaoxing 27 Feb '19

27 Feb '19

Dear Mailman Developers, TL; DR: Please change the CNAME record of *docs.mailman3.org <http://docs.mailman3.org>* from gnu-mailman.readthedocs.org to *readthedocs.io <http://readthedocs.io>*. I would like to raise the awareness that https://docs.mailman3.org is having a wrong SSL certificate due to DNS misconfigure. I once saw the Mailman 3 project in GSoC orgs page, and since I have configured mailman before I would like to know about the ideas, I click on the docs link. Wow, not secure. Since the prompt tells me it is using *.readthedocs.org, I dig into the doc of RTD (https://docs.readthedocs.io/en/latest/custom_domains.html) and it tells it support custom domain SSL with some limitations. So, `dig docs.mailman3.org`, got you, an old (may not wrong?) record. Because the link is already published on GSoC, I don't know if it is possible to change from https to http. So the better way might be support https :). Regards, Xiaoxing Ye

3 7

New to the community.
by Shubham Chauhan 27 Feb '19

27 Feb '19

Hello everyone, congratulations for getting selected for GSoc '19. I'm new to this organisation. I wanted to know if there is any other platform where we could connect? Thank you.

2 1

GSoC 2019
by saurabh singh 27 Feb '19

27 Feb '19

Hi Everyone, My name is Saurabh and I am new to open source development . I want to contribute to Mailman but I am confused how to exactly do it. It would be really helpful if anyone could guide me. Yours sincerely, Saurabh

2 1

MailMan Core Project
by NAYAN KHANNA 26 Feb '19

26 Feb '19

Myself Nayan Khanna. Currently, I'm a 2nd year student at BITS Pilani pursuing Bachelors of Engineering in Computer Science and Integrated Msc. Mathematics. I was exploring the projects of Mailman and was highly impressed by some of them. I have been into Web Development from the past 2 years and have worked a lot on Django and Flask. Apart from these, I have a good programming command in C, C++ and Python, and know MySQL and DBMS concepts well. Been into Web Development, I have also worked on HTML, CSS, JS, AngularJS. Being more of a Back End Developer, I have worked on System Administration and Web Hosting through Nginx+Gunicorn. I love exploring new things and this is something which keeps me going. I really look forward to spend my summer contributing to MailMan projects while being a GSoC candidate for the org. I would feel lucky if I could find a mentor who can guide me on getting started with my contributions.

2 1

Error when creating new user or resetting password
by Kamran Soomro 19 Feb '19

19 Feb '19

Hi, I am running mailman 3 using the docker images created by Abhilash. Whenever I try to create a new user or reset password for an existing user, I get the error shown in the screenshot. The only thing I can see in docker logs is "POST /accounts/password/reset/ HTTP/1.0" 500 1102. Any suggestions on how to debug this? –Kamran

3 2

Mailman Core 3.2.1 release coming out soon
by Abhilash Raj 11 Feb '19

11 Feb '19

I am working on cutting out a release for Mailman Core, 3.2.1, soon. Most probably by end of this week. If you have anything small you really want to get into this release, please ping me, I'd prefer if we don't put anything huge. I'll cut out an -rc1 release EOD today. We are going to move to more of SemVer[1] approach and avoid having to bump major versions (which, in our case, is minor version) if we don't need to. We will keep on bumping minor versions till we really need to bump major version due to backwards incompatibility reason. This would also help us make more point releases that downstreams can upgrade to, without having to worry about bumping major versions. We don't really break API everytime when bumping major versions, which is slightly confusing and hard to keep track of. This should also help us not worry too much about backporting fixes to old release branches. We will continue to release minor versions, till we have to bump major, after which the old version will be unmaintained. But in history of Mailman 3, we only had to break compatibility once with REST API change with 3.1 release. Finally, I'll keep the release codename of 3.2.0 series and keep 'Tom Swayer' reserved for the next major version bump, whenever we end up doing that. [1]: https://semver.org/ -- thanks, Abhilash Raj (maxking)

1 0