Mailman 3 - Mailman-Developers

GSoC for working professionals
by Christopher 23 Mar '22

23 Mar '22

Hi everyone Nice to meet you all! I am interested in GSoC 2022 and I discovered that Mailman might be one of the interesting projects I would like to contribute to. However, I am not a student, but I am working as a software engineer full time (10-6 on weekdays). I would like to start contributing to open source projects and stumbled upon GSoC which I thought it's a great opportunity to get started. If I am able to churn out 14.5 hours of work per week (by working on the weekends) across 12 weeks (summing up to 175 hours), do I stand a chance to be accepted as a GSoC participant? Thanks, Christopher Chong

3 6

--- in DMARC From: rewritings
by Дилян Палаузов 22 Mar '22

22 Mar '22

Hello, the DMARC Mitigation action “Replace From: with list address” is evaluated in mailman/handlers/dmarc.py:munged_headers(). In the case, where From: is a non-member email address, without display part, which non-member may post, this happens: realname = email realname = re.sub(r'@([^ .]+\.)+[^ .]+$', '---', realname) with _.using(mlist.preferred_language.code): via = _('${realname} via ${mlist.display_name}') display_name = str(Header(via, mlist.preferred_language.charset)) value = [('From', formataddr((display_name, mlist.posting_address)))] In short, if a@b is a non-member, who may post to mailing list “E <c@d>”, and b is DMARC-protected, the final distrubuted email will have From: "a--- via E <c@d>" Reply-To: a@b compare to the IETF mailing lists, which would send: From: <a=40b@d> where a and b are from a@b, d is from c@d The bottom of https://answers.uillinois.edu/illinois/page.php?id=86787 describes the mitigariton options offered by Sympa: display name From: User Name <listName(a)lists.illinois.edu> display name and e-mail From: “User Name” (userEmail(a)address.com) < listName(a)lists.illinois.edu > email “via Mailing List” From: “User Name” (userEmail(a)address.com via listName Mailing List) <listName(a)lists.illinois.edu> name “via Mailing List” From: “User Name” <listName(a)lists.illinois.edu> (the website likely means:) From: “User Name via listName” <listName(a)lists.illinois.edu> As can be seen, the other MLMs do not replace domains with --- . I find ugly the --- , inserted by mailman. In my real-world case the From: is aaa(a)example.org, the ML name is aaa(a)l.example.org (localname is the same, the domains are different). The result is: From: aaa--- via Aaa <aaa(a)l.example.org> So there is twice trippe-A and @example.org disappeared. Mentioning twice AAA in the display name in this case really has to added value. That said, I propose removing now the line realname = re.sub(r'@([^ .]+\.)+[^ .]+$', '---', realname) and in the future offer as options: From: User Name <listName(a)lists.illinois.edu> From: “User Name” (userEmail(a)address.com) < listName(a)lists.illinois.edu > From: “User Name” (userEmail(a)address.com via listName Mailing List) <listName(a)lists.illinois.edu> From: “User Name via listName” <listName(a)lists.illinois.edu>

3 6

GSoC - Support for REST Callbacks in Core
by Christopher 21 Mar '22

21 Mar '22

Hi guys, I am interested in this project "Support for REST Callbacks in Core", can I know more details about it? Thanks, Christopher Chong

1 0

Creating an event catching plugin
by Дилян Палаузов 11 Mar '22

11 Mar '22

Hello, can you point me to existing, open-source mailman plugins? I want to write a plugin, which fires on all subscriptions, unsubscriptions and configuration changes. This code: def subscribe_events(e): print('EVENT', e) @implementer(IPlugin) class SievePlugin: def __init__(self): print('XXX') zope.event.subscribers.append(subscribe_events) def post_hook(self): print('YYY') zope.event.subscribers.append(subscribe_events) prints: XXX EVENT x(a)example.org joined zzz.udoma.bapha.be EVENT ab c <mm(a)example.org> joined zzz.udoma.bapha.be or XXX EVENT x(a)example.org left zzz.udoma.bapha.be on `mailman addmembers/mailman delmembers`. But it does not trigger a UnsubscriptionEvent or SubscriptionEvent. Greetings Дилян

2 4

New MM3 plugin: mailman_sieve
by Дилян Палаузов 11 Mar '22

11 Mar '22

Hello, I have published a new Mailman 3 plugin at https://mail.aegee.org/cgit/mailman_sieve/tree/ . It generates for each mailing list a Sieve script. When the Sieve script is evaluated during the SMTP dialog, it would reject some emails, which otherwise would be bounced by Mailman. Less bounces means less backscatters and better IP reputation. For the record, I do the evaluation of the Sieve scripts during the SMTP dialog with https://mail.aegee.org/cgit/aegee-milter . Since the latter is not documented yet, you cannot use it. The mailman_sieve plugin is not useful, unless you have software to evaluate the Sieve Scripts during the SMTP dialog. This is a very first version, which does what it is supposed to do. Some optimizations are possible, like not including the subscriber addresses in the Sieve scripts for announce-only mailing lists. I am not good at writing setuptools configuration. Neither do I understand the mailman system very good right now, creating possibly shorter scripts. But the plugin is there to keep by IP reputation good! See https://mail.aegee.org/cgit/mailman_sieve/tree/README.md . My reading of the mm3 source code is that there is no event triggered, when the mailing list configuration changes, like adding a new moderator, or switching the announce-only status. In the lack of such event triggers, the Sieve scripts are not updated. When the code improves, the plugin could be published in PyPi or in mailman/contrib . Greetings Дилян

2 1

GNU Mailman in Google Summer of Code 2022!
by Stephen J. Turnbull 10 Mar '22

10 Mar '22

Hi all, We are participating in Google Summer of Code 2022 (GSoC) under the Python Software Foundation (PSF). We did apply as a separate organization, but didn't get in. Many thanks to the PSF's GSoC organization for picking us up at the last minute! You can find our ideas page at https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202022, and item on the PSF ideas page under https://python-gsoc.org/ideas.html (which isn't so interesting about Mailman, but you can check out who else is under the PSF banner there). Discussion and development of project ideas will take place on mailman-developers(a)python.org. If you have a developed idea not already listed that you're willing to discuss and advocate, and you're willing to grab the template (last item on our ideas page on list.org) and fill it out, please post it to mailman-developers(a)python.org. (This a deliberate hoop-jumping exercise to filter in "serious" ideas.) You can put more weight on it by expressing interest in mentoring the project, and even more by actually volunteering! ;-) If you have a half-baked idea, and/or you want to get input from other Mailman users, of course you should feel free to discuss it on mailman-users(a)mailman3.org. We *might* pick it up from there, even if it's just a drive-by post with little support from the list members. But no promises about that, most of our attention will go to mailman-developers. If you feel some idea should get more love, polish it a little and post that to mailman-developers (don't cross-post, please). Again, we'd love to have more mentors, including backup mentors. We currently only have two mentors. Although we're both core developers, and I'm on an academic schedule and can devote plenty of time to the student during the summer, not so for Abhilash. Volunteering at this stage is not a promise to do more than look at student proposals. You would only be asked to look at the proposals, and volunteer as mentor for that project if you have interest and some level of knowledge to contribute to it. Even if you're a site admin with little Python programming experience, vetting interns' brainstorms about list admin-visible features and holding their hands until the "pros from Dover" arrive is quite helpful in making the student feel at home in our community. Many students are shy about blogging and communicating about their projects to the community -- just talking to them about their project and suggesting that they blog what they told you is helpful. Coding skills and knowledge of some part of the Mailman 3 code base are most welcome, of course, but you can make your mentor role what you want it to be. Regards, Steve

1 0

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

Regarding willing to contribute to the organization.
by Sanket Varpe 28 Jan '22

28 Jan '22

Hello, This is Sanket Varpe, a final year CS student at PICT, Pune. I am looking to make contributions to open source projects. I have multiple internship experiences as a backend developer where I architected and implemented backend of cloud based applications. I am experienced in Javascript, Node.js, Python, Django etc.I went through mailman projects and found them very interesting. I went through their issues but as I am little new to this area I got confused seeing a lot of issues and how to choose one.But if given a small task/issue or project/new idea to work on at starting would be very great and i'll definitely make good contributions. Would like to discuss more if possible. Looking forward to hearing from you. Thank You.

2 1

Mailman 2.1.39 Release
by Mark Sapiro 13 Dec '21

13 Dec '21

I am pleased to announce the release of Mailman 2.1.39. This is a bug fix release. It fixes https://bugs.launchpad.net/mailman/+bug/1954694 This addresses two issues. The fix for CVE-2021-42097 was case sensitive and should not be. The fix for CVE-2021-44227 introduced a potential NameError in logging. This could cause a user's changes to the option's page to not be accepted and perhaps cause a `We hit a bug` response if the user visited the page with a mixed- or upper-case email address For those who just want a patch one is attached to the bug report. As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1 branch from the GNU Mailman project. There has been some discussion as to what this means. It means there will be no more releases from the GNU Mailman project containing any new features. There may be future patch releases to address the following: i18n updates. security issues. bugs affecting operation for which no satisfactory workaround exists. Mailman 2.1.39 is the ninth such patch release. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.39 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0