Mailman 3 - Mailman-Developers

GSOC 2023 mentors
by Stephen J. Turnbull 27 Feb '23

27 Feb '23

Hi everybody We still have no mentors for GSOC 2023. Last chance to sign up (with the Python Software Foundation org) is Feb 25. - You don't need to be a Mailman core dev or a Python guru. - Generic mail geeks welcome. - Code spelunking (ie, "grepping for error messages") is very desirable. - Some Python, obviously. - Experience using and preferably administering Mailman. - Opinions about existing bugs and new features a must, of course! ;-) Requires a couple hours a week, somewhat irregularly, from secondary mentors (you), more like 5-10 from primary mentor (me, and you if the bus factor comes into play). Anybody interested, let me know. If you have questions about it, please respond on-list so others can see. Steve

2 3

New year releases!
by Abhilash Raj 04 Jan '23

04 Jan '23

Hello Everyone, Happy new year! I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.8 [1] 2. Postorius 1.3.8 [2] 3. Hyperkitty 1.3.7 [3] 4. Mailmanclient 3.3.5 [4] 5. Django-mailman3 1.3.9 [5] 6. Mailman-hyperkitty 1.2.1 [6] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. Thanks to all the contributors for making this release possible! If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html -- thanks, Abhilash Raj (maxking)

1 0

Preventing abuse of postorius
by Phil Budne 02 Dec '22

02 Dec '22

Apologies in advance if this isn't the right place to ask. Almost every day I find outgoing emails from postorius stuck in my outbound mail queue. It seems like the anonymous_subscribe route is being used to send mail to unwitting targets. I'd rather not be operating a relay being used to DDoS people's mailboxes. Any suggestions on out of the box solutions? I know captcha's and such are imperfect, and a losing battle, but as an Internet old-timer (I was at the first IETF meeting), I feel obligated to at least try to contribute to a solution; I'm a Python programmer, but not a Djangoist. Thanks, Phil

3 3

New Mailman Core Release
by Mark Sapiro 15 Nov '22

15 Nov '22

We are pleased to announce the release of Mailman core 3.3.7. It is published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ The change log is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… - please note the `BREAKING CHANGE` documented there and due to our now using SQLAlchemy >-1.4. Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies (aiosmtpd) not supporting 3.10 yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Mailman Core Dutch translation in progress
by Michael Smith 14 Nov '22

14 Nov '22

Hi all, I used to run Mailman 2 a while ago for some Dutch speaking volunteer groups in Belgium. But that has since stopped. Mailman 2 had support for Dutch. Now I'm getting back into hosting mailing lists for another group of volunteers so I spun up Mailman 3. To my surprise switching to 'nl' for Dutch did nothing and after investigating I noticed there's no 'nl' folder in mailman's messages folder. It looks like the original Dutch translation from Mailman 2 was not ported over to Mailman 3. I've since found out that the translation can be done through https://hosted.weblate.org/projects/gnu-mailman/mailman/nl/ and so I have started the process there. It will take me a while longer to complete it but I'm definitely motivated to do so. I'm using the Dutch .po file from the source code of the latest Mailman 2 version as a guide. I just wanted to post this here in case anyone had remarks about this. How likely is it to see version bump / Mailman 3 release once a Dutch translation is complete? Or will there be no separate release for new locales? No problem anyway, I can patch the Dutch into my local installation when I'm done and I figure out how to do that :) Kind regards Michael

2 1

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

Code formatting tools for Mailman project
by Abhilash Raj 31 Oct '22

31 Oct '22

Hey Everyone, I am trying out some of the code formatting tools on Mailman repos to help reduce some efforts in development. The tools I am trying out is blue[1] and isort[2] to format code and imports. We've been using isort on some repos, but am planning to expand that to all projects. I am also adding a new tox command `tox -e format` that should run the appropriate commands locally for users to run. The choice of tool, blue in this case, was mostly motivated by the design choices that align closest with Mailman's as Barry is a co-owner of the tool and authored Mailman's style guide as well. If there are any issues with these tools, please let me know or feel free to open an issue on the project and ping me there. I've started off with Postorius[3], but will expand further to other projects. Core will probably be updated towards the last. [1]: https://blue.readthedocs.io/en/latest/# [2]: https://pycqa.github.io/isort/index.html [3]: https://gitlab.com/mailman/postorius/-/merge_requests/734 -- thanks, Abhilash Raj (maxking)

2 5

New Mailman Releases
by Abhilash Raj 26 Oct '22

26 Oct '22

Hi, I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of changelogs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 -- Something weird is going on with the page missing the bullets. [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies not support 3.10 yet (aiosmtpd). Thanks to all the contributors for making this release possible and apologies on my end for delayed releases. If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ -- thanks, Abhilash Raj (maxking)

1 0

Bug in 2.1.29 when hitting one button and then another in the confirm page
by Andrea Monaco 20 Oct '22

20 Oct '22

I visited the confirm page to leave a mailing list, then by mistake I clicked "Cancel and discard", I pressed ESC almost immediately and then "Unsubscribe". A page appeared saying that I hit a bug. Maybe the software state becomes inconsistent in that case? Andrea Monaco

2 1

ARC user options
by Alessandro Vesely 14 Sep '22

14 Sep '22

Hi, There is a thread about ARC sealing in bind-users[*]. They're applying ARC signatures, although they run Mailman 2. The last message hypothesizes a user option like so: *From munging*: Set this option to /Disabled/ to receive messages with the original From: line intact. Keep in mind that disabling this option will fail DMARC, so keep it enabled unless your MTA either doesn't check DMARC or accepts ARC overrides. It doesn't seem difficult to implement. It requires trusting the users, though. Would Mailman implement something like it? Why? Why not? Best Ale -- [*] https://lists.isc.org/pipermail/bind-users/2022-September/106612.html

2 12