From: Warren Toomey via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] TUHS web server has changed
Date: Fri, 6 May 2022 07:26:30 +1000 [thread overview]
Message-ID: <20220505212630.GA19111@minnie.tuhs.org> (raw)
In-Reply-To: <f08b6e95-f707-dd23-e0bc-e20df91cc2f7@spamtrap.tnetconsulting.net>
On Wed, May 04, 2022 at 11:54:25AM -0600, Grant Taylor via TUHS wrote:
> I'm curious what your thoughts / plans are on migrating email.
> I /think/ that TUHS (and presumably COFF) is using Mailman 2.x which I
> believe is dependent on Python 2.x. Are you going to be migrating to
> Mailman 3.x / Python 3.x? Or are you going to go a different direction?
Firstly, thanks to you all for your thanks! I announced minnie as an ftp
site on comp.archives back in May 1991, so she must be one of the longest
continually operating Internet sites.
Yes, I plan on moving to Mailman 3.x. I'm hoping that I can import the raw
TUHS mbox (currently 130Mbytes). This, unfortunately, will break the hyperlinks
in the current mail archive at https://minnie.tuhs.org/pipermail/tuhs/
Anyway, first I've got to get SPF, DKIM and friends set up :-)
Cheers, Warren
next prev parent reply other threads:[~2022-05-05 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 2:08 Warren Toomey via TUHS
2022-05-04 13:27 ` Clem Cole
2022-05-04 19:37 ` Mary Ann Horton
2022-05-05 0:52 ` Dave Horsfall
2022-05-05 5:43 ` Andy Kosela
2022-05-05 5:57 ` Grant Taylor via TUHS
2022-05-05 20:48 ` Dave Horsfall
2022-05-04 17:54 ` Grant Taylor via TUHS
2022-05-05 21:26 ` Warren Toomey via TUHS [this message]
2022-05-05 23:42 ` Gregg Levine
2022-05-06 2:38 ` Grant Taylor via TUHS
2022-05-06 2:52 ` Warner Losh
2022-05-06 4:32 ` Kenneth Goodwin
2022-05-07 16:13 ` Patrick Audley via TUHS
2022-05-09 16:12 ` Grant Taylor via TUHS
2022-05-09 17:55 ` Kenneth Goodwin
2022-05-09 19:22 ` Richard Salz
2022-05-09 19:57 ` Grant Taylor via TUHS
2022-05-09 18:37 ` Danil Smirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220505212630.GA19111@minnie.tuhs.org \
--to=tuhs@minnie.tuhs.org \
--cc=tuhs@tuhs.org \
--cc=wkt@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).