From: Eric Wong <e@80x24.org>
To: Manos Pitsidianakis <manos@pitsidianak.is>
Cc: meta@public-inbox.org
Subject: Undelivered replies [was: [PATCH] imap: use spec compliant continuation request]
Date: Wed, 26 Jun 2024 03:32:52 +0000 [thread overview]
Message-ID: <20240626033253.M17106@dcvr> (raw)
In-Reply-To: <fng6h.6mcfasdnlqei@pitsidianak.is>
Btw, I'm getting this error for your address:
<manos@pitsidianak.is>: Host or domain name not found. Name service error for
name=mail.nessuent.xyz type=AAAA: Host not found
$ host -t mx pitsidianak.is
pitsidianak.is mail is handled by 10 mail.nessuent.xyz.
The Received: header in your messages says mail.nessuent.net, not .xyz
prev parent reply other threads:[~2024-06-26 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 12:26 [PATCH] imap: use spec compliant continuation request Manos Pitsidianakis
2024-06-25 17:52 ` Eric Wong
2024-06-25 18:40 ` Manos Pitsidianakis
2024-06-26 3:32 ` Eric Wong [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240626033253.M17106@dcvr \
--to=e@80x24.org \
--cc=manos@pitsidianak.is \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).