Mailman 3 June 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 10 Jan '17

10 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

Re: [Mailman-Developers] GSOC:Populating two default styles
by Barry Warsaw 25 Jun '16

25 Jun '16

On Jun 24, 2016, at 03:14 AM, Harshit Bansal wrote: >I was trying to populate the two default styles in the database. For >this purpose, I was trying to use ConfigurationUpdatedEvent as used in >the earlier style manager but I am recieving following error: [...] >AttributeError: No section or category named db. > >It seems that the database layer hasn't got initialized by the time >this event was fired. Is there any way of fixing this or any other way >using which I can populate the database when mailman starts? That's right. Getting the initialization sequence correct is pretty tricky, and it's true that the configuration subsystem is initialized before the database connection is created. If you think about it, it has to be this way since there are settings in the config files that control how the database is set up. What I think this means for you is that you can't use the ConfigurationUpdatedEvent to set up your stylets until the database is set up. Unfortunately, right now there aren't any events fired when initialization is completely, but just the other day Aurelien and I sketched out an event-based plugin mechanism for better HK integration, and one of the things I realized we needed was some additional event notification for the various stages of initialization. Right now, your best hope is to use the [mailman]post_hook which gets run during initialize_3() and is guaranteed to be run after both the configuration subsystem and the database connection is set up. Eventually the pre_hook and post_hook will be deprecated because they aren't really set up well for plugins, and we'll have events for the various phases of initialization, so you could register a handler for one of those events. If you decide to keep the ConfigurationUpdatedEvent handler (e.g. because you want to do other stylet things if the configuration changes once the system is up and running), just check for the existence of the config.db attribute, or catch the AttributeError. If the attribute is missing, you know the ConfigurationUpdatedEvent is too early for your purposes. Hope that helps. -Barry

1 0

GSOC:Populating two default styles
by Harshit Bansal 23 Jun '16

23 Jun '16

Hi, I was trying to populate the two default styles in the database. For this purpose, I was trying to use ConfigurationUpdatedEvent as used in the earlier style manager but I am recieving following error: Traceback (most recent call last): File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/testing/layers.py", line 87, in setUp initialize.initialize_1(INHIBIT_CONFIG_FILE) File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/core/initialize.py", line 118, in initialize_1 mailman.config.config.load(config_path) File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/config/config.py", line 102, in load self._post_process() File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/config/config.py", line 125, in _post_process notify(ConfigurationUpdatedEvent(self)) File "/home/harshit/Drive1/dev/Mailman/env/lib/python3.4/site-packages/zope.event-4.1.0-py3.4.egg/zope/event/__init__.py", line 31, in notify subscriber(event) File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/model/styletmanager.py", line 105, in handle_ConfigurationUpdatedEvent getUtility(IStyletManager).populate() File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/harshit/Drive1/dev/Mailman/mailman/src/mailman/config/config.py", line 87, in __getattr__ return getattr(self._config, name) File "/home/harshit/Drive1/dev/Mailman/env/lib/python3.4/site-packages/lazr.config-2.1-py3.4.egg/lazr/config/_config.py", line 513, in __getattr__ raise AttributeError("No section or category named %s." % name) AttributeError: No section or category named db. It seems that the database layer hasn't got initialized by the time this event was fired. Is there any way of fixing this or any other way using which I can populate the database when mailman starts? Thanks, Harshit Bansal

1 0

Hyperkitty set up
by ADITI GUPTA 22 Jun '16

22 Jun '16

Hello, I am trying to connect hyperkitty to mailman. I have cloned and set up mailman-hyperkitty and made changes in the mailman_hyperkitty.cfg and mailman.cfg files. But, still I am unable to see anything in hyperkitty(except the login page).I have injected mails to a list using mailman inject -f email.txt test(a)example.net but couldn't see anything there except the login page. "No archived lists yet" is shown there. I checked the MailingList model in hyperkitty through command line and found that it is empty. Regards, Aditi

1 0

Re: [Mailman-Developers] Begginer Level Bugs
by Mark Sapiro 21 Jun '16

21 Jun '16

On 06/21/2016 01:39 AM, Nischay Singh wrote: > I read the guidelines on the website and found that the bugs are classified > for beginners. Can someone please tell me where to look for such bugs. Go to <https://gitlab.com/groups/mailman/issues> and look for issues tagged 'beginner friendly'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Begginer Level Bugs
by Nischay Singh 21 Jun '16

21 Jun '16

Hi all! This is Nischay. I'm new to the open source community. Looking forward to actively contributing to mailman. I read the guidelines on the website and found that the bugs are classified for beginners. Can someone please tell me where to look for such bugs. Thank you! -- Nischay Singh Student B.E.(Hons) Computer Science BITS Pilani

1 0

Re: [Mailman-Developers] GSoC project - Implement module to process ARC headers
by Stephen J. Turnbull 19 Jun '16

19 Jun '16

Aditya Divekar writes: > So should a new conversation be started with Mark for > our request? I/we need to find out exactly what we need. We may want to do this through email-test.python.org (no-existent, for example, python.org is the relevant part, or maybe a private domain of someone's), but we have to be careful that it doesn't conflict with other uses. > That sounds good! The `mail` keyword gave an idea - > `emailauthentication` I think that would need to be shortened, but mailauth would work and has a good rhythm. :-) Of course it may be "taken". > I had read on the arc list that an OpenARC implementation was being > developed by Murray Kucherawy. So I suppose that we may have the > news of it being released on the list soon. Yes, but Murray's OpenDKIM is a C library, and I expect OpenArc is too. I don't think we should be using a C library because we're not an MTA, and I suspect it will be making assumptions (eg, availability of SPF) that we shouldn't. In any case, the more independent implementations the better. Steve

2 1

Re: [Mailman-Developers] GSoC project - Implement module to process ARC headers
by Stephen J. Turnbull 18 Jun '16

18 Jun '16

Aditya Divekar writes: > So if we have a domain name associated with the ip, I'll go ahead > and make the TXT records. Else, we'll have to create a new one. > I'm not aware of any way to avoid this. Let me know if you are > aware of any :) Ah, that's a problem. I don't have control of the DNS yet. We'd need to interact with Mark. Anyway it's too late for this one, there were procedures to be taken earlier in the week. I'll get you on the arc-interop list, there should be another one in the summer at the pace they've been going. > Yes, I went ahead and made the changes. Good! > I have a separate module 'arcpy' installed in my python > dist-packages now which is basically the refactored 'dkimpy' > package. I don't think its the best of names since it doesn't give > the idea of presence of DKIM signing/verifying features. Any ideas > for the same? Not really. Keywords that might be useful aside from ARC, DKIM, and DMARC: mail, post, verify, track, key, sign, identity. Ah -- one brainstorm -- kimpy = "key identified mail.py". As far as words go, you could just keep dkimpy, too, since ARC depends on domain keys for its semantics, as well as on DKIM for its signing protocol. "adkimpy"? Lots of double meanings there: Aditya, ARC, augmented, domain, divikar. :-) I was surprised by the news, but Google also chose dkimpy for its implementation of ARC. I haven't had time to look at it, but maybe early next week (not publicly licensed, sorry, no URL). Steve

2 1

GSOC: Progress, community review and blog post
by Anirudh Dahiya 18 Jun '16

18 Jun '16

Hi My Gsoc project Message queue based email archiver has progressed quite well. The detailed progress and journey had been documented by me in this blog post - http://codefullofsummer.blogspot.in/ Also, I would like to share my work and ask for community review - https://gitlab.com/anirudhdahiya9/RabbitMQMessageQueueArchiver/tree/pubMQAr… https://gitlab.com/anirudhdahiya9/mailman/tree/MQArchiver Regards Anirudh Dahiya (irc spark)

1 0