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

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

Is it possible to use Postorius alongside the legacy interface?
by Joe Corneli Jan. 1, 2021

Jan. 1, 2021

Hello, I wonder if it's possible for users to choose between the new Postorius interface and the old text-based interface? Some users might prefer the text-based interface (e.g., for accessibility or just familiarity); others may prefer the new interface (which does look quite snazzy!). But, I didn't find any documentation about switching between the two. Joe

2 1

Help regarding GSoC 2021
by Aditya Komaravolu Dec. 23, 2020

Dec. 23, 2020

Hello Sir/Ma'am, I am a Second Year Artificial Intelligence Undergraduate at Vidya Jyothi Institute of Technology,Hyderabad,Telangana,India. I am really interested to contribute and work on open source projects for Python organisation and want to be a part of GSoC 2021 under Python Organisation. I am interested to work in the areas of Machine learning and Python development. Ironically I have no knowledge regarding the contribution process. Please help me to become an active contributor and help me be a part of Google Summer of Code 2021. Regards, Aditya Komaravolu.

2 1