From owner-freebsd-ports@freebsd.org  Thu Apr 30 13:18:16 2020
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id AF8172BC702
 for <freebsd-ports@mailman.nyi.freebsd.org>;
 Thu, 30 Apr 2020 13:18:16 +0000 (UTC)
 (envelope-from freebsd@gregv.net)
Received: from aurora.gregv.net (aurora.gregv.net [192.111.144.138])
 by mx1.freebsd.org (Postfix) with ESMTP id 49CbY40F5wz4k7t;
 Thu, 30 Apr 2020 13:18:15 +0000 (UTC)
 (envelope-from freebsd@gregv.net)
Received: by aurora.gregv.net (Postfix, from userid 1001)
 id 7DC3A763; Thu, 30 Apr 2020 09:18:15 -0400 (EDT)
Date: Thu, 30 Apr 2020 09:18:15 -0400
From: Greg Veldman <freebsd@gregv.net>
To: Kurt Jaeger <pi@freebsd.org>
Cc: "@lbutlr" <kremels@kreme.com>, FreeBSD <freebsd-ports@freebsd.org>
Subject: Re: mail/mailman v3?
Message-ID: <20200430131815.GA1068@aurora.gregv.net>
References: <f800ba2bddccd78d5a1cb4e674b0c0f9@udns.ultimatedns.net>
 <A5CB67A4-D096-4E08-8FD1-E50EAA25691D@kreme.com>
 <20200430015916.GM39563@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200430015916.GM39563@home.opsec.eu>
User-Agent: Mutt/1.12.1 (2019-06-15)
X-Rspamd-Queue-Id: 49CbY40F5wz4k7t
X-Spamd-Bar: ++++
Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none;
 spf=none (mx1.freebsd.org: domain of freebsd@gregv.net has no SPF policy when
 checking 192.111.144.138) smtp.mailfrom=freebsd@gregv.net
X-Spamd-Result: default: False [4.98 / 15.00]; ARC_NA(0.00)[];
 FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3];
 MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[gregv.net];
 AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.98)[0.975,0];
 TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[];
 NEURAL_SPAM_LONG(1.00)[1.000,0]; R_SPF_NA(0.00)[];
 RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[];
 R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[];
 ASN(0.00)[asn:31863, ipnet:192.111.144.0/20, country:US];
 MIME_TRACE(0.00)[0:+];
 IP_SCORE(1.10)[ipnet: 192.111.144.0/20(1.94), asn: 31863(3.62),
 country: US(-0.05)]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2020 13:18:16 -0000

On Thu, Apr 30, 2020 at 03:59:16AM +0200, Kurt Jaeger wrote:
> There are many thousand links to the freebsd pipermail archives,
> and invalidating all those links sounds like a serious loss of institutional
> memory.
> 
> Is there a way to cope with that ? Some sort of
> lookup 'old link' -> 'new link' ?

Internally, the Mailman archives are just a bunch of
script-generated flat HTML and TXT files.  The only Mailman
specific thing is the bit of logic that gates access to a
private archive with a credential check.  For public archives
(which if my understanding is right, most Mailman-managed
FreeBSD lists are) there should just be a line somewhere in
your HTTPD config that aliases pipermail/ to
<Mailman_inst_dir>/archives/public/.

So no matter what you switch to if/when Mailman2 dies, it
should be fairly trivial to preserve the current archives in
a read-only state at their current URLs.  Even private ones,
assuming you replace the Mailman gatekeeper with something
else (perhaps access control in your HTTPD itself).

-- 
Greg Veldman
freebsd@gregv.net