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

Unclear usage of `member = ISubscriptionManager(mlist).register(…)`
by Дилян Палаузов 26 Feb '22

26 Feb '22

Hello, I am trying to understand the source code. My reading is, that interfaces/subscriptions.py:class ISubscriptionManager.register always returns a 3-tuple and the last element of the tuple is a member object, or None. This coincides with the implementation in app/subscriptions.py.SubscriptionManager.register . cli_synmembers.py:add_members() contains: member = registrar.register( subscriber, pre_verified=True, pre_approved=True, pre_confirmed=True, send_welcome_message=welcome_msg)[2] member.preferences.delivery_status = delivery_status member.preferences.delivery_mode = delivery_mode return and commands/cli_addmembers.py:add_members() contains member = registrar.register( subscriber, pre_verified=True, pre_approved=True, pre_confirmed=True, invitation=invite, send_welcome_message=welcome_msg)[2] if member is not None: member.preferences.delivery_status = delivery_status member.preferences.delivery_mode = delivery_mode return So my question is: when regirstar.register returns a tuple, the last argument of which is a members, why do the above snippets store the result in a variable called `member`? How are the set preferences set to member handled further, as my reading is that the variable just disappears, immediately after member.preferences is set? Greeting Дилян

3 2

How to recreate Issue #973 in mailman-core
by Suyash Singh 06 Feb '22

06 Feb '22

Greetings everyone, I am new to the repository of Mailman and was looking for open source projects that used Django and came across this amazing open source. I hope to learn a lot about Django and Linux. I have started a development environment and am starting to read the documentation. I picked up issue #973 because it seemed like a easy issue to fix. Link to Issue: https://gitlab.com/mailman/mailman/-/issues/973 1) I am unable to recreate the problem. As I can't find the API url and how do I access them in my development environment. I tried the using the command "mailman shell" which is referred to in the documentation for debugging. and after holding a message and handling it. I get the following error: >>> handle_message(mlist, 1, Action.discard) >>> handle_message(mlist, 1, Action.discard) Traceback (most recent call last): File "<console>", line 1, in <module> File "/home/suyashsingh/Desktop/mailman/mailman/src/mailman/app/moderator.py", line 113, in handle_message key, msgdata = requestdb.get_request(id) TypeError: cannot unpack non-iterable NoneType object 2) How can I start http://localhost:9001/ on my local machine as currently its not working. What is the port 9001 used for?

3 2