X-Original-To: alpine-infra@lists.alpinelinux.org Received: from smtp.alpinelinux.org (unknown [147.75.101.119]) by lists.alpinelinux.org (Postfix) with ESMTP id CB816F84F64 for ; Sat, 20 Apr 2019 06:17:35 +0000 (UTC) Received: from mail-wr1-f41.google.com (mail-wr1-f41.google.com [209.85.221.41]) (Authenticated sender: clandmeter@alpinelinux.org) by smtp.alpinelinux.org (Postfix) with ESMTPSA id 4E2607817BE for ; Sat, 20 Apr 2019 06:17:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alpinelinux.org; s=smtp; t=1555741054; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=k6sbNeFOL3+uBJNpgOB1U61Q2RKWh0MmHpfvl2OL5Vs=; b=lsR0yXtYQ9TTNvv1JInTQIBc1bZ4wc3moK9PknIG/W1NXVEEQAIwCTBZc44fx33MjKigt7 F8gGg9u3UORr5TXNKoJXhz1rj6SFm5wwqKUEmnHEjgGztbpvXWmumUwCHw3goSaU7NFvKf LA6Bf9yfCD6GqziIZgBVC8DKKl7br2E= Received: by mail-wr1-f41.google.com with SMTP id k17so9179134wrx.10 for ; Fri, 19 Apr 2019 23:17:34 -0700 (PDT) X-Gm-Message-State: APjAAAWvSX2V3FV/EoCJCjmL3dldjHoGePUgSAKK1BRVE9mP+V2UeoXl Ec9TU7rZ/YKWTd7bBl9owh15K5tAKUv3Q49zlXM= X-Google-Smtp-Source: APXvYqzWgblR+g/53XFyaZ3DSCJEx9sMjBHGAUybUT1pE8emf7eXUir9Mavqz8PBJKRGit5z6xYLx0hor+jLGL08MH0= X-Received: by 2002:a5d:52ce:: with SMTP id r14mr5860024wrv.224.1555741053599; Fri, 19 Apr 2019 23:17:33 -0700 (PDT) MIME-Version: 1.0 References: <20190411151205.GA28895@homura.localdomain> In-Reply-To: <20190411151205.GA28895@homura.localdomain> From: Carlo Landmeter Date: Sat, 20 Apr 2019 14:17:22 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Mailing lists overhaul updates To: Drew DeVault Cc: Alpine Linux Mirrors , Natanael Copa , Nathan Angelacos Content-Type: multipart/alternative; boundary="000000000000dcc7a50586f03055" --000000000000dcc7a50586f03055 Content-Type: text/plain; charset="UTF-8" Hi! Sorry that i didn't have time earlier to reply your email. I'm still on my business trip but i'll be back after next week. Nathan, Do you have any concerns about this migration? On Thu, 11 Apr 2019 at 23:12, Drew DeVault wrote: > Hiya! Been working on setting up lists.sr.ht for Alpine over the past > few days, and I think everything's in place. To summarize, Carlo set up > the listserv container for me to work in, and I installed & configured > the necessary software there. There were a number of upstream changes > required, but the rub is: > > - Old hyperkitty archives can be imported > - Old hyperkitty web archive URLs can be redirected to the new archives > - Old mlmmj subscriptions can be imported > - The posting addresses have changed, but redirects were put in place so > the old ones still work > > Thanks a lot for your time and help setting this up. It is highly appreciated. I know we haven't always been easy to deal with, but i think you understand the reasoning. > If you want to play with the result, check out > https://lists2.alpinelinux.org. If you want an account, reach out to me > for an invite (registrations are closed to the public) - > ddevault@freenode or via email is fine. Incoming emails are wired up > but I didn't import subscribers, so feel free to post a few test emails > if you want (if you Cc me, I can go delete them from the archives > later). > I didn't really have time to test it in depth, i will do that after next week. >From what i've seen until now i like, and you seem to care about our concerns which is super nice. > > On the listserv box, there's a README at /home/ddevault going over some > of the technical details, including notably the credentials for the > "alpine" meta-user which has ownership over the lists. Future > improvements to the upstream project should eliminate the need for this > weird meta-user and clean things up a bit. > Looking forward for that change. > > I've done a full end-to-end test of all of the features and migration > details, and I believe everything is in good working order. The > remaining work-items are: > > 1. Finish configuring the new lists > a. Create & configure the lists on lists2.alpinelinux.org > b. Import the archives > c. Import the subscribers > d. Create the hyperkitty redirects for nginx > (These procedures are outlined in detail in the README) > 2. Cut over DNS for lists2.a.o -> lists.a.o > a. Update nginx config on listserv > b. Update /etc/sr.ht/config.ini on listserv > c. Update postfix transport db on smtp.a.o > 3. Backfill any emails & subscriptions in the archive that came in > during the migration process > > Let's do that after next week. I'll ping you on IRC. P.S. I think you are referring to hypermail instead of hyperkitty. Again, thanks a lot! -carlo --000000000000dcc7a50586f03055 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi!
Sorry that i didn't hav= e time earlier to reply your email.
I'm still on my business = trip but i'll be back after next week.

Nathan,= Do you have any concerns about this migration?

<= /div>
O= n Thu, 11 Apr 2019 at 23:12, Drew DeVault <sir@cmpwn.com> wrote:
Hiya! Been working on setting up lists.sr.ht for Alpine over = the past
few days, and I think everything's in place. To summarize, Carlo set up=
the listserv container for me to work in, and I installed & configured<= br> the necessary software there. There were a number of upstream changes
required, but the rub is:

- Old hyperkitty archives can be imported
- Old hyperkitty web archive URLs can be redirected to the new archives
- Old mlmmj subscriptions can be imported
- The posting addresses have changed, but redirects were put in place so =C2=A0 the old ones still work


Thanks a lot for your time and help se= tting this up. It is highly appreciated.
I know we haven't al= ways been easy to deal with, but i think you understand
the reaso= ning.
=C2=A0
If you want to play with the result, check out
https://lists2.alpinelinux.org. If you want an account, reach out = to me
for an invite (registrations are closed to the public) -
ddevault@freenode or via email is fine. Incoming emails are wired up
but I didn't import subscribers, so feel free to post a few test emails=
if you want (if you Cc me, I can go delete them from the archives
later).

I didn't really have time t= o test it in depth, i will do that after next week.
From what i&#= 39;ve seen until now i like, and you seem to care about our
conce= rns which is super nice.
=C2=A0

On the listserv box, there's a README at /home/ddevault going over some=
of the technical details, including notably the credentials for the
"alpine" meta-user which has ownership over the lists. Future
improvements to the upstream project should eliminate the need for this
weird meta-user and clean things up a bit.

<= div>Looking forward for that change.
=C2=A0

I've done a full end-to-end test of all of the features and migration details, and I believe everything is in good working order. The
remaining work-items are:

1. Finish configuring the new lists
=C2=A0 =C2=A0a. Create & configure the lists on lists2.alpinelinux.= org
=C2=A0 =C2=A0b. Import the archives
=C2=A0 =C2=A0c. Import the subscribers
=C2=A0 =C2=A0d. Create the hyperkitty redirects for nginx
=C2=A0 =C2=A0(These procedures are outlined in detail in the README)
2. Cut over DNS for lists2.a.o -> lists.a.o
=C2=A0 =C2=A0a. Update nginx config on listserv
=C2=A0 =C2=A0b. Update /etc/sr.ht/config.ini on listserv
=C2=A0 =C2=A0c. Update postfix transport db on smtp.a.o
3. Backfill any emails & subscriptions in the archive that came in
=C2=A0 =C2=A0during the migration process


Let's do that after next week. I&#= 39;ll ping you on IRC.

P.S. I think you are referr= ing to hypermail instead of hyperkitty.

Again, tha= nks a lot!

-carlo

--000000000000dcc7a50586f03055--