From: Grant Taylor via COFF <firstname.lastname@example.org>
Subject: [COFF] Re: Status of classiccmp.org?
Date: Mon, 20 Jun 2022 23:12:01 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]
On 6/20/22 9:59 PM, Tomasz Rola wrote:
> As you might know, when the target does not receive email, sender
> will try to send it to backup receiver(s), here:
That's the idea. At least in an ideal world. Sadly, I've experienced
too many ... less than ideal installations.
> ;; ANSWER SECTION:
> classiccmp.org. 1799 IN MX 10 mx2.ezwind.net.
> classiccmp.org. 1799 IN MX 10 mx1.ezwind.net.
Those are actually two equal weight peer MXs. There's nothing
differentiating one as primary and backup. The "10" would need to be
different between the two records.
> 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.
In an ideal world, messages would never be dumped to /dev/null. Per RFC
-- the bible of interoperability on the Internet -- messages should
never be lost. Instead, such ultimate undeliverables situations should
be reported to the (purported) sender.
> 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'm not aware of anything in the SMTP protocol that is applicable for
getting such information. Sometimes it can be inferred by observing
I did receive such a Delivery Status Notification (a.k.a. DSN) from
mx1.ezwind.net five days after I sent a message to cctalk.
> 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...),
Yep. Hence "inferred by observing". ;-)
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]
next prev parent reply other threads:[~2022-06-21 5:11 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
2022-06-21 5:12 ` Grant Taylor via COFF [this message]
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).