From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZHtSp5fBmz32yq for ; Wed, 19 Mar 2025 15:50:02 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZHtSl1PLwz32p7 for ; Wed, 19 Mar 2025 15:49:59 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZHtSk30TNz5cD for ; Wed, 19 Mar 2025 15:49:58 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1742399398; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jr3Yj/tzOQmuwEO0aUnl8gv2DjY73t8xTL0eHRtTZQ8=; b=r3lx52xr4N8g6kkxNooopvarq5Q4DZ8dENGnsvXb+NgCFls9Lf0SmKCg8zTxzHWWZexrAy mbUMtqZXaDJTpjCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1742399398; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jr3Yj/tzOQmuwEO0aUnl8gv2DjY73t8xTL0eHRtTZQ8=; b=uyunhmq0RzPkow/iSaQpIcQvDXw07jHKoKtx5WmgqHBvbZsSVoZT+l+338BIaAXXUjtum0 Jt8+iHT4DemTZHgSQ7ysFPyrvMAKwBT+UX7qMh45e7HsuiZecDVPtpatgxbZwYcR28vv91 tKI3tKT84E912ZNaBEnxPHDB3DjON4hA1/uKQlnk5I+N9f+KwLxYeKI0/RpPLoxhY4nKZJ SZX5s4BvKH6NkDHFM1466woNBGaXDvtMwd8Fd8xCw8w7PZOZ6esH7v4gTtanwYaWD7gPKl URw+wEH9pbFTZLk6SwwPsQ75nAQUHeVPtwnc6JHtCFoAJwhGTQVOyL9lfuRXZA== From: Michael Tremer Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Migration of lists.ipfire.org to mlmmj & public-inbox Date: Wed, 19 Mar 2025 15:49:57 +0000 References: <57E6F5D7-9A3D-4291-8DB6-A50FA90CC0F0@ipfire.org> To: "IPFire: Development-List" In-Reply-To: <57E6F5D7-9A3D-4291-8DB6-A50FA90CC0F0@ipfire.org> Message-Id: <9EACA6CF-1CB7-466A-BAB5-68DF34E6C50D@ipfire.org> Hello everyone, A quick update on this=E2=80=A6 So far, no new problems have been reported back to me on this, which is = good news. Emails seem to be making their way to all recipients a lot = faster now and the server is using significantly less resources now. I have therefore removed all sorts of traces of Mailman 3 from the = system which concludes the entire migration. One last thing on my list was to fix any kinds of redirects. This has = also been implemented now, but with the caveat that we cannot do this = for Mailman 3 as the message ID in the URL is hashed. Public-inbox on = the other hand requires the raw message ID. There is a way to index all = emails and keep a table with the hashes somewhere, but that is simply = too much work for very few people to benefit from. I also think that we = have not been using Mailman 3 for long enough that there should be too = many links around. For Mailman 2, we can however redirect all emails which is the vast = majority of links that I could find. -Michael > On 10 Mar 2025, at 11:31, Michael Tremer = wrote: >=20 > Hello everyone, >=20 > I wanted to inform you that lists.ipfire.org = has been migrated from mailman 3 to mlmmj [1] = and public-inbox [2]. This change was necessary due to long-standing = issues with Mailman, including excessive resource usage and reliability = concerns. >=20 > This email is already (and hopefully) reaching you over the new = software. If you have not been able to receive this and other emails, = please let me know. Everything else should pretty much be working = without any further problems or changes. >=20 > Why all of this? >=20 > Mailman 3 seems to have a lot of problems that have been causing a lot = of time to be dealt with. Although we have some workarounds in place = here or there, they are neither pretty, nor do they help us to process = emails swift and properly. The huge colossus that mailman 3 has become = due to its split into multiple micro services has not only been pain for = us. >=20 > Therefore I started looking for alternatives. However, email does not = seem to be considered very cool any more. So there is a lot of = commercial products that try to re-invent it, but actually behind those = large lists that we have in the open source community, there seems to be = one single software that is the chosen solution: mlmmj. Although I = don=E2=80=99t know how to pronounce this name, it is a really neat piece = of software. Super small. Written in C. Actively maintained again. And = it can shift a lot of emails very fast. However, it does not have any = kind of web UI. Which we don=E2=80=99t even need. >=20 > But I would like a public archive that can be searched through easily. = That is implemented using another piece of software called public-inbox. = All emails that go through the lists are being passed to public-inbox, = indexed and can be viewed on the web in the old place: >=20 > https://lists.ipfire.org/ >=20 > My outstanding issue right now is simply making old links that pointed = to mailman 2 and 3 work. I think we might have the problem that they = won=E2=80=99t. But that will have to be a story for another day=E2=80=A6 >=20 > All the best, > -Michael >=20 > [1] https://mlmmj.org/ > [2] https://public-inbox.org/