From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alrua-x1.borgediget.toke.dk (alrua-x1.borgediget.toke.dk [IPv6:2a0c:4d80:42:443::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 4B6DF3B29D; Sun, 13 Jul 2025 12:47:54 -0400 (EDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 5E4761B8A86D; Sun, 13 Jul 2025 18:47:49 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: bloat@lists.bufferbloat.net, cake@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net, codel@lists.bufferbloat.net, ecn-sane@lists.bufferbloat.net, libreqos@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net, nnagain@lists.bufferbloat.net, rpm@lists.bufferbloat.net, starlink@lists.bufferbloat.net X-Clacks-Overhead: GNU Terry Pratchett Date: Sun, 13 Jul 2025 18:47:49 +0200 Message-ID: <87ms9811hm.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain X-Mailman-Approved-At: Sun, 13 Jul 2025 12:52:02 -0400 Subject: [NNagain] Migrating the Bufferbloat mailing lists X-BeenThere: nnagain@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: =?utf-8?q?Network_Neutrality_is_back!_Let=C2=B4s_make_the_technical_aspects_heard_this_time!?= List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2025 16:47:54 -0000 Hi folks I am about to initiate a migration of the Bufferbloat mailing lists off of Dave's old Linode server an onto my own mail server. In the process, the list backend will be switched from the old Mailman2 instance to an up to date Mailman3 installation, and the archive backend will be switched to a public-inbox based archive. The mailing lists in the To field of this email are the active lists which will be migrated, and no action is necessary for you to continue to be subscribed. All other lists currently hosted at lists.bufferbloat.net will have their archives migrated for posterity, but won't be setup to receive new email. I am sending this email before initiating the migration. Once the mail has been flushed from the mailing list queue, I will shut down the mail server daemon on the old server, and initiate the archive and DNS migration. After the migration is complete, I will send another notification email to let you all know the migration has been completed. Meaning that if you receive this email, but not the follow-up notification, that could indicate a delivery issue. In which case, please do let me know (off-list!), but please allow a day or so for everything to flush out. See you on the other side! -Toke