From nobody Fri Mar 24 22:06:45 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PjxBh2kc6z41CN2 for ; Fri, 24 Mar 2023 22:06:52 +0000 (UTC) (envelope-from doug@safeport.com) Received: from freeport.safeport.com (freeport.safeport.com [147.160.157.114]) by mx1.freebsd.org (Postfix) with ESMTP id 4PjxBg6T4bz3nxv for ; Fri, 24 Mar 2023 22:06:51 +0000 (UTC) (envelope-from doug@safeport.com) Authentication-Results: mx1.freebsd.org; none Received: from bucksport.safeport.com (bucksport.safeport.com [147.160.157.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by freeport.safeport.com (Postfix) with ESMTPS id AB63D51D0CC; Fri, 24 Mar 2023 18:06:45 -0400 (EDT) Date: Fri, 24 Mar 2023 18:06:45 -0400 (EDT) From: Doug Denault To: Odhiambo Washington cc: Pete Wright , questions@freebsd.org Subject: Re: List managers [Was: Link usability] In-Reply-To: Message-ID: References: <3faa3481-abe3-47cd-f273-2658db42a5bc@gmail.com> <11239785ba0531583f29189b133ceafdcded8aad.camel@blues-softwares.net> <5f1028aadd42bcbd89c62e843fc59798c52a0f36.camel@blues-softwares.net> <9B5F5E1E-555D-4FA8-AFBE-EBBD3A8A7045@nimnet.asn.au> <6eaa6e1f-af45-41f8-a5d7-2f03eb4f456a@freebsd.org> <20230321192209.giqsnhqbl7ben6vk@beesty.loosely.org> <7e683c8f-0bb4-74c8-386e-5c4dff5f0804@nomadlogic.org> <34bfdc5d-47e7-f2dc-9560-d5c39f34bbca@safeport.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1596476994-1679695605=:87440" X-Rspamd-Queue-Id: 4PjxBg6T4bz3nxv X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6405, ipnet:147.160.157.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1596476994-1679695605=:87440 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 24 Mar 2023, Odhiambo Washington wrote: > On Fri, Mar 24, 2023 at 5:10?PM doug wrote: > On Tue, 21 Mar 2023, Pete Wright wrote: > > > > > > > On 3/21/23 12:22, possessor.assizer305@aceecat.org wrote: > >> On Tue, Mar 21, 2023 at 07:49:11PM +1100, Ian Smith wrote: > >> > >>> Ah, right.  Yet another consequence of the regressive move from > >>> mailman plus pipermail to mlmmj is loss of clickable links in the > >>> archived messages.  Duh! > >> Out of curiosity, what was the rationale for the move? > >> > >> My opinion: > >> Mailman has its warts but it's ubiquitous and well suited for > >> a world where almost everything has to be done in the browser > >> for $REASONS. > >> > > my understanding is that mailman was tied to python2, and the next version of > > mailman (v3 iirc) that supports python3 is incompatible with the previous > > version.  i think it also had a bunch of other shortcomings/issues.  so i > > suspect the lift to use mlmmj was easier than moving to mailman v3. > > > > i agree its an unfortunate situation, but its i think it would be > > irresponsible to rely on python2 for such critical infrastructure. > > > Boo on the mailman project. There is a conversion utility that takes care > of the syntax changes. The only maajor changes I hit were the MySQL, and a > couple of DNS modules. In something as complex as mailman I am sure there > was more but relative to just maintaining something that complex well > within there Python knowledge I would assume. > > > I have run Mailman2 since 2005. I am currently running Mailman3.Mailman2 > relied on Python2.7. Mailman3 relies on Python3. There is a migration > script for Mailman2 to Mailman3. The installation for Mailman3 is better > done in a Python Virtual Environment. Being a FressBSD SysAddmin since I > encountered FreeBSD in 1997, I can authoritatively say that it is very > easy to migrate. And IF anyone needs assistance to migrate their Mailman2 > lists to Mailman3, I am willing to hold their hands. Perhaps I should > document the whole process. It is quite easy. The only challenge I have > faced is the startup script for controlling Mailman3, but I have a > rudimentary one that works. I am running Mailman3 on FreeBSD 13- RELEASE, > if it matters. I tried Sympa, but waah. Never again. If anyone has > questions, I am willing to respond to them. All of them. If you have been > running Mailman2, the move to Mailman3 is the most painless!! > Thanks for the information. So I change my boo to boo on the list maintainers if the fallout is as described. As I use pine following links is somewhat problemactic for me anyway. Nice to know the mailman folks were not remiss/lazy. _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 --0-1596476994-1679695605=:87440--