From: Grant Taylor via COFF <coff@tuhs.org>
To: coff@tuhs.org
Subject: [COFF] Re: Status of classiccmp.org?
Date: Wed, 15 Jun 2022 09:37:46 -0600 [thread overview]
Message-ID: <a93b6224-e9dd-2be0-8a40-ca232ffcab42@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20220615051421.GA8328@tau1.ceti.pl>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On 6/14/22 11:14 PM, Tomasz Rola wrote:
> Ah. I too am missing a "noise" coming from that direction. A noise,
> well, a buzz, of bees always repairing their hardware, nothing
> negative.
I think that it will be interesting to see how much email makes it
through once services are brought back on line.
I've always retained mail for two weeks before giving up. Not as may
people do so for as long any more.
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]
next prev parent reply other threads:[~2022-06-15 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 22:16 [COFF] " Warren Toomey via COFF
2022-06-14 22:27 ` [COFF] " Jason T
2022-06-15 5:14 ` Tomasz Rola
2022-06-15 15:37 ` Grant Taylor via COFF [this message]
2022-06-21 3:59 ` Tomasz Rola
2022-06-21 5:12 ` Grant Taylor via COFF
2022-06-22 21:03 ` Grant Taylor via COFF
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=a93b6224-e9dd-2be0-8a40-ca232ffcab42@spamtrap.tnetconsulting.net \
--to=coff@tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).