Mailman 3 March 2021 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett Nov. 7, 2022

Nov. 7, 2022

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

Interest to contribute under Mailman for GSoC 2021
by Aditya Komaravolu March 31, 2021

March 31, 2021

Respected Developers, I am Aditya Komaravolu (Gitlab profile: https://gitlab.com/Aditya-Komaravolu), a second year student pursuing Bachelor of Technology from Vidya Jyothi Institute of Technology, India. I have done a few small contributions to the organization and I am confident enough that I will be able to contribute in a better way by learning from the mentors/developers of the organisation. GSoC is a very good opportunity to learn, bind and code with the community. I am very much interested to participate in GSoC 2021 for Mailman as a student. I would love to work for the project "Improved UI for Subscription Management " given in ( https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021). I really want to know what I should be learning to contribute/move in the direction of this project. Any support from your end would be highly appreciated ! Thank you, Aditya.

1 0

Interest to participate in GSoC under mailman
by Shubhank Saxena March 31, 2021

March 31, 2021

Respected Mailman Developers My name is Shubhank(https://gitlab.com/shubhank-saxena). I am a final year engineering undergraduate from India. I am interested to participate in GSoC 2021 under Mailman. I have gone through the instructions provided by the organisation, and have got one of my MR reviewed and merged in the Mailman Core. I have now started to write a proposal in the same direction and I was wondering how can I start the discussion regarding the Mailman Core projects that are given on the webpage ( https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021). I am interested in the project "Support for REST Callbacks in Core". Also, is the IRC channel active? I did not see any conversations happening so I was wondering if the mode of communication has shifted strictly to the mailing list? Thank you for your time!

2 2

Question about GSoC SPAM
by Steven Chen March 30, 2021

March 30, 2021

Dear Mailman Developers, This is Steven1677(https://gitlab.com/Steven1677) on GitLab. I want to contribute to the mailman3 project as a GSoC student. I am starting to write my proposal for GSoC. I wonder whether our personal information will go public if we send the proposal to the this mail list? I fully understand that applying for GSoC requires such information, but I think the personal contact information (like phone number, email addresses) should be only available to the members of the developer team instead of the whole internet. Hence, I am asking whether the whole proposal (including the basic information of the student) should be sent to this mail list? Regards, Steven1677

3 4

Mailman, postfix and docker
by costavitorino＠gmail.com March 28, 2021

March 28, 2021

Hi all I'm upgrading a mailman2 installation to mailman3. And I using a docker implementation, created by me and not Maxking's implementation. Everything is installed and is served correctly. I have created a postfix container that relays emails to a smtp server, and I can send emails by telnet from it. When I create a new thread in Hyperkitty, I receive an error from postfix container that the user (mailing list name) is not found. And I believe that is obvious because the aliases db are not accessible by postfix. So, my questions are: - Is there a way to share aliases db between containers(different hosts) of mailman and postfix? I thought about sharing volumes but I'm not quite sure if it's the best solution - I've seen: virtual_alias_maps = mysql:/etc/postfix/virtual/existing_aliases.cf, var/lib/mailman/data/virtual-mailman to add in postfix main.cf. Is it possible to do the same thing to aliases and transport_maps? And if so, how to set it in mailman configuration, because this is for mailman I've seen this thread: https://mail.python.org/archives/list/mailman-developers@python.org/thread/… And it seams kind or less the same situation. Does anyone have an idea or can give some pointers in how to accomplish this? Kind regards, Emanuel

5 7

Allow to post in developers list
by Ankit Punia March 28, 2021

March 28, 2021

I want to contribute to mailman. So I request you to allow me to post in developers list so I can communicate with other contributors and understand to product better.

2 1

Mailman Core 3.3.4 is now out
by Abhilash Raj March 21, 2021

March 21, 2021

Hey Everyone, I am pleased to announce that Mailman Core 3.3.4 is now out. Because of incompatibility with the new version of a downstream library (SQLAlchemy), this release add is setting 1.3.x as the max supported version of SQLAlchemy. Even though it comes soon after 3.3.3, it has a lot of bug fixes and new features. Some notable ones are: * Email -join command now supports subscribing as digests with digest=<no|mime|plain> options being honored. * For anonymous lists, Mailman will filter all the headers except a few that can be configured using a new config option. * Mailman can do max_size checks on filtered message rather than original message (which might be larger before being filtered) * Previously deprecated --add, --del and --sync options from `mailman members` command are now removed. Their alternatives are `addmembers`, `delmembers` and `syncmembers` subcommands. * If configured, Mailman will add a report about content filtering. A complete change log is available here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… This release is available via PyPI: https://pypi.org/project/mailman/3.3.4/ You can install or upgrade using: ``` $ pip install --upgrade mailman ``` Thanks to all the contributors who helped with this release! -- On behalf of Mailman Core Team Abhilash Raj

1 0

CI CD test failure
by hrs 2203 March 19, 2021

March 19, 2021

Hi everyone, I am facing some issues with the pipeline. While creating docs for issue #442 of mailman core, I updated my local master branch with the mailman/mailman, created a separate branch on my local machine and created a .rst file for BanManager Documentation. I tested the docs building locally and it worked fine, all tests passed. When I pushed the code for the merge request, the pipeline passed for docs and qa, but failed for all other tests. I have tried many things but I can't understand why the tests are failing even though I have only created a new file and changed nothing else. https://gitlab.com/mailman/mailman/-/issues/442 Looking forward to your feedback ------------ Hrishabh Pandey

2 1

Unable to create new thread in Local development Enviroment
by Prashant Pandey March 19, 2021

March 19, 2021

Hi, This is Prashant Pandey, I am willing to contribute to Mailman3 as a GSOC student. I have some doubts about the dev environment. I set up the local dev environment using https://docs.mailman3.org/en/latest/devsetup.html this doc and I used my forked repos instead of the main repository. All the apps working fine but when I am creating a new thread using Hyperkitty it says ("The message has been sent successfully.") but I did not get this message on the list as shown in the screenshot. I also tried with separate docs but they didn't help me. My question is: 1. Is there any another doc for setting up the local environment? 2. Is mailman core works in the development mode? I am attaching my debug logs.

3 4

Unable to create a thread in local dev environment
by Prashant Pandey March 18, 2021

March 18, 2021

When I am creating a thread using "Start a new thread in hyperkitty", after typing the subject and message it says "The message has been sent successfully." but after this, it does not show in the list discussion. Please advise and suggestions to setup it properly.

3 2