Mailman 3 - Mailman-Developers

Custom feature request - ripe ncc - archive expires
by Marco van Tol 18 Oct '24

18 Oct '24

Hi there, Hopefully you're the right contact to ask this. Please let us know who else to send the email to if not. We're interested in the development of a feature in mailman3 where we can configure it to automatically expire/remove threads in/from the archive older than x number of days. We can discuss the details, including financial compensation for the development effort, once we get further into this. For now I'm looking for the right person to talk to about this. Is there a way forward for this? Thank you so much in advance! Marco van Tol RIPE NCC

3 11

Mailman Core release
by Abhilash Raj 01 Oct '24

01 Oct '24

Hey Everyone! I am pleased to announce new release of Mailman Core 3.3.10. This includes both bug fixes and new features. A full list of changes can be found at the usual location[1]. This release includes a Breaking change and nntp runner no longer starts automatically in the default release. You can easily enable the runner by updating your `mailman.cfg`. See the release notes[1] for details on how. This release can be downloaded from PyPI[2] or using `pip install mailman==3.3.10`. For those interested in package signatures, both the source tarball and built wheel are available in Gitlab releases[3] along with their signatures. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://pypi.org/project/mailman/ [3]: https://gitlab.com/mailman/mailman/-/releases/v3.3.10 -- thanks, Abhilash Raj (maxking)

1 0

New Mailman web package releases
by Abhilash Raj 22 Sep '24

22 Sep '24

Hello Everyone, I have just released Postorius 1.3.13 and Hyperkitty 1.3.12. These can be downloaded from PyPI: https://pypi.org/project/HyperKitty/1.3.12/ https://pypi.org/project/postorius/1.3.13 Note that due to some mistakes on my part, last 2 releases for Postorius & Hyperkitty were yanked since their builds uploaded to PyPI weren't correct due to some mis-configurations migrating from setuptools to pyproject.toml (with pdm) based package configuration. So, when updating from last installed versions, please look at the changelogs from older versions too for both these packages. Their changelogs are available in the usual places: https://docs.mailman3.org/projects/postorius/en/latest/news.html https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Since PyPI doesn't accept signatures anymore, I have uploaded packages and their signatures to Gitlab releases in their respective repositories too. A note for people using my signature for verification: I had to extend my gpg key's validity, so you'll need to refresh my public keys to validate the signature this time. -- thanks, Abhilash Raj (maxking)

2 2

Mailman3 replaces [ with =?utf-8?q?=5B, why?
by Alessandro Vesely 30 May '24

30 May '24

Hi all, I've seen these Subject: lines being changed using utf-8 quoted-printable encoding for every non-alnum character. The message has: X-Mailman-Version: 3.3.9rc4. Of course, doing so breaks DKIM signatures, and I'm trying to understand in what cases it is advisable to revert the encoding in order to verify the signature. Does Mailman 3 always and unconditionally behave like that or what does it depend on? TIA for any hint Best Ale -- P.S. I'm curious to see how this Subject: is going to be encoded by Thunderbird. Original-Subject: Mailman3 replaces [ with =?utf-8?q?=5B, why?

2 1

Application for the google summer of code
by tahertadpatri＠gmail.com 30 Mar '24

30 Mar '24

Hi this is taher I am new to open source. want to contribute to mailman3 postorius for the idea of Enhanced Subscription Management UI for Postorius I locally setup the postorius I just need little guidance here is my proposed idea. https://docs.google.com/document/d/1zFvZe7G2roW6Jz07Mxg7o3mZtgUlRl_niI-5IzC…

1 0

Help on Gitlab
by Daniel Azubuine 27 Mar '24

27 Mar '24

Hello everyone, I'm new here, and i just forked the mailman core repo and made a contribution. I pushed my changes to gitlab, and then i get an error that pipeline failed. This pipeline ran on the contents of the merge request's source branch, not the target branch. How do i go about this

4 6

Introduction, FOSDEM, scaling down, latency, OpenPGP support
by Justus Winter 04 Mar '24

04 Mar '24

Hello everyone :) I want to introduce myself, I'm Justus, I have worked on GnuPG in the past and am now working on Sequoia-PGP, and I'm running two Mailman installations in a resource constrained shared hosting environment. I'd like to contribute a little to Mailman, and I'd like to better understand how the Mailman project is doing nowadays. I have gotten a bugfix merged in the past, but I now have what I think is a fairly uncontroversial cleanup merge request that has neither been merged nor has it gotten comments. - https://gitlab.com/mailman/mailman/-/merge_requests/1158 As FOSDEM is around the corner, are any of you going to be there and are up for a chat? Besides cleanups and bugfixes, there are three things I'd like to do: - Improve Mailman to better scale down to small installations - Improve latency of messages - Implement OpenPGP support Here are the things I did so far: - https://gitlab.com/mailman/mailman/-/merge_requests/1094 - https://gitlab.com/mailman/mailman/-/issues/1050 - https://gitlab.com/mailman/mailman/-/merge_requests/1166 - I have Mailman running with runners in threads instead of processes, but that is in a proof-of-concept stage at this point and needs some cleaning up (I understand that Mailman is a GNU project that wants copyright assignments, and I have done that in the past for other GNU projects, and would be happy to do that for Mailman, but at the same time I feel like putting up *any* barrier to contributing is unfortunate.) Best, Justus

4 10

Review requested for some merge requests
by Stephen J. Turnbull 06 Jan '24

06 Jan '24

Reply-To set to Mailman Developers. Please check that your replies go there. Or you can comment on MRs directly if you have a GitLab login. I have three merge requests pending: [1] https://gitlab.com/mailman/mailman/-/merge_requests/1159 [2] https://gitlab.com/mailman/mailman/-/merge_requests/1160 [3] https://gitlab.com/mailman/mailman/-/merge_requests/1161 [1] fixes the logging initialization bug that prevented the `smtp` log from rotating properly, and maybe some others. I don't think it needs user review because it's a pure bugfix, but if you're curious and take a look, and you think it needs better documentation let me know. [2] adds a configuration variable `lmtp_max_size`. This is user-visible, so review of the documentation in docs/mta.rst and config/mailman.cfg for clarity and readability would be appreciated. [3] adds postfix-pgsql support for use of the PostgreSQL database to route Mailman traffic. It's really most useful in an edge case (migration of 10,000+ list Mailman 2 instances), but it's theoretically attractive on the principle of "single source of truth", and possibly for implementing a "microservices" style cloud instance (it eliminates the need for Mailman and Postfix to share a file system). Besides opinions on the value of the general idea I have two specific questions: - Postfix docs recommend not looking up domains in the database to reduce load on the database server. But on a dedicated Mailman system, you're going to be looking up pretty much everything twice anyway (once to check for local recipient and once to fetch the transport), and my experience so far is that this isn't a big load on Postgres, and it's not a drag on list traffic distribution. Should I implement domain lookup in Postgres? Should it be optional if the lists are being looked up in Postgres? - The current patch completely disables generation of the postfix_lmtp alias file, even for the `mailman aliases` command. Should I implement an option to force generation of the files for documentation (and maybe a backup in a very rare and contorted situation where Mailman can see Postgres but Postfix can't)? Thanks, Steve

1 0

Re: [Mailman-Users] Updated Drupal user mailman register module (announcement)
by Russell Clemings 05 Dec '23

05 Dec '23

Willing to consult, but I don't know that I will ever be able to do the Mailman3 port myself, or have a reason to, unless cPanel updates to Mailman3 (not holding breath on that eight-year-old feature request). The module is not that complicated for Mailman2. You create and manage lists via the Mailman web pages. The module just maintains tables of lists and subscribers and creates Drupal forms for (1) users to manage their subscriptions, and (2) admins to make lists available and manage their subscribers. Mailman3 I suspect would require a lot more work. https://www.drupal.org/project/user_mailman_register On Mon, Dec 4, 2023 at 9:45 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Russell Clemings writes: > > > Because I needed it for a project, I've just updated the "user mailman > > register" module for Drupal 9/10. > > Thank you for the work and for letting us know about it! > > Yes, IWBNI "somebody" would do the Mailman 3 port, and if you're > thinking about it, feel free to get in touch with us (and are you able > to consult on such a project even though you can't work on it at the > moment, Russell?) > > Since that would be Mailman 3, the appropriate venue for discussion of > such a project is mailman-developers(a)python.org, not this list. > Reply-To set. > > -- =============================================== Russell Clemings <rclemings(a)gmail.com <russell(a)clemings.com>> ===============================================

1 0

Fwd: (Custom) Plugins: Proper file path(s) for adding a handler?
by Thomas Ward 29 Oct '23

29 Oct '23

I originally sent this to the mailman3 list, but got no reply all day, suggesting that perhaps this might have not been the best place to send this message to. So, sending it to the mailman-developers list, which is more tech/devel oriented. Primarily, my goal here is to figure out how to add handlers via a plugin, but there's no documentation for it, so I'm looking for more information. Worst case, I can probably add my handlers and pipelines as direct files in the venv inside Mailman's paths for the PyPI packages, but I'd like to avoid that if possible and just add an extra plugin. Thomas -------- Forwarded Message -------- Subject: (Custom) Plugins: Proper file path(s) for adding a handler? Date: Mon, 23 Oct 2023 11:07:53 -0400 From: Thomas Ward <teward(a)thomas-ward.net> To: mailman-users(a)mailman3.org I want to add a custom handler that implements customized thread IDs in the system. I already have the DB logic worked out, but the documentation for plugins is NOT clear on how to define a handler in a plugin, nor does the example plugin in the documentation on Gitlab have any custom handlers. I'm looking to add a custom handler so that the private pipeline for threaded-subject-list can use thread-subject (the custom handler) instead of subject-prefix (builtin). I'm unclear how to add this properly in a plugin that would be read properly by Mailman, though. Any tips on the filestructure needed for the Python code/plugin package in order to properly be set up and work? Thomas

3 2