From nobody Fri Mar 24 14:10:34 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 4Pjkd864NKz41cY5 for ; Fri, 24 Mar 2023 14:10:36 +0000 (UTC) (envelope-from doug@safeport.com) Received: from fledge.watson.org (fledge.watson.org [147.160.157.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "A1-48603", Issuer "A1-48603" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pjkd71mvgz47FF for ; Fri, 24 Mar 2023 14:10:35 +0000 (UTC) (envelope-from doug@safeport.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=fail (mx1.freebsd.org: domain of doug@safeport.com does not designate 147.160.157.40 as permitted sender) smtp.mailfrom=doug@safeport.com; dmarc=none Received: from fledge.watson.org (doug@localhost [127.0.0.1]) by fledge.watson.org (8.16.1/8.16.1) with ESMTPS id 32OEAYMD017272 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 24 Mar 2023 14:10:34 GMT (envelope-from doug@safeport.com) Received: from localhost (doug@localhost) by fledge.watson.org (8.16.1/8.16.1/Submit) with ESMTP id 32OEAYHd017269; Fri, 24 Mar 2023 14:10:34 GMT (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Fri, 24 Mar 2023 14:10:34 +0000 (UTC) From: doug Reply-To: doug@safeport.com To: Pete Wright cc: questions@freebsd.org Subject: Re: List managers [Was: Link usability] In-Reply-To: <7e683c8f-0bb4-74c8-386e-5c4dff5f0804@nomadlogic.org> Message-ID: <34bfdc5d-47e7-f2dc-9560-d5c39f34bbca@safeport.com> 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> 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="621616949-1957973882-1679667034=:45353" X-Spamd-Result: default: False [-1.07 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; CTYPE_MIXED_BOGUS(1.00)[]; R_SPF_FAIL(1.00)[-all]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.971]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; MIME_TRACE(0.00)[0:+,1:+]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:6405, ipnet:147.160.157.0/24, country:US]; R_DKIM_NA(0.00)[]; HAS_REPLYTO(0.00)[doug@safeport.com]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; HAS_XAW(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; DMARC_NA(0.00)[safeport.com]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Pjkd71mvgz47FF X-Spamd-Bar: - 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. --621616949-1957973882-1679667034=:45353 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT 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. --621616949-1957973882-1679667034=:45353--