From: Warren Toomey via COFF <coff@minnie.tuhs.org>
To: coff@tuhs.org
Subject: [COFF] Oops, re hello to COFF
Date: Sat, 14 May 2022 15:37:44 +1000 [thread overview]
Message-ID: <20220514053744.GA3895@minnie.tuhs.org> (raw)
All, if you got a strange 'hello' message on the COFF mailing list,
my apologies. I have mailman3 set up on the new "minnie" machine,
and I am going to also set up a mailman2 instance.
The idea is that mailman3 will do the normal list processing and have
its own archive using the Hyperkitty software. But mailman2 will be
subscribed to the list, so mail can be also archived using the old
pipermail software. That way, I can import the existing TUHS and COFF
mailing list archives and augment them, rather than lose them entirely.
I thought I'd deleted all the COFF subscribers on the new "minnie"
system, but I can see in the logs that some test e-mail might have
escaped.
Cheers, Warren
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next reply other threads:[~2022-05-14 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 5:37 Warren Toomey via COFF [this message]
2022-05-14 7:59 ` Grant Taylor via COFF
2022-05-14 23:03 ` Warren Toomey via COFF
2022-05-15 16:25 ` Grant Taylor via COFF
2022-05-14 8:08 ` Ralph Corderoy
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=20220514053744.GA3895@minnie.tuhs.org \
--to=coff@minnie.tuhs.org \
--cc=coff@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).