From: Tomasz Rola <email@example.com>
To: Grant Taylor via COFF <firstname.lastname@example.org>
Subject: [COFF] Re: Status of classiccmp.org?
Date: Tue, 21 Jun 2022 05:59:39 +0200 [thread overview]
Message-ID: <20220621035938.GA23036@tau1.ceti.pl> (raw)
On Wed, Jun 15, 2022 at 09:37:46AM -0600, Grant Taylor via COFF wrote:
> 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.
As you might know, when the target does not receive email, sender will
try to send it to backup receiver(s), here:
$ dig classiccmp.org MX
; <<>> DiG 9.16.27-Debian <<>> classiccmp.org MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27228
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;classiccmp.org. IN MX
;; ANSWER SECTION:
classiccmp.org. 1799 IN MX 10 mx2.ezwind.net.
classiccmp.org. 1799 IN MX 10 mx1.ezwind.net.
and from this:
I infer that the actual date when email will get dumped to /dev/null
depends on settings of relevant mail servers (MTAs) - either sending one
or backup receiver. If there is a way to get those value remotely by
talking to the server, I have not yet dug it up, nor looked.
I assume it might be about two weeks in case of classiccmp and each
email author should be notified when his email fails to reach a
recipient. So, we will see (experiment by doing nothing...),
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home **
** directory. And then the C programmer became enlightened... **
** Tomasz Rola mailto:email@example.com **
next prev parent reply other threads:[~2022-06-21 3:59 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
2022-06-21 3:59 ` Tomasz Rola [this message]
2022-06-21 5:12 ` Grant Taylor via COFF
2022-06-22 21:03 ` Grant Taylor via COFF
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).