From: John Murphy <me@jtm.cx>
To: 9front@9front.org
Cc: sl@stanleylieber.com
Subject: Re: [9front] Unreliable delivery
Date: Thu, 15 Jul 2021 10:07:03 -0400 [thread overview]
Message-ID: <20210715100703.44159bde@x1c.home.jtm.cx> (raw)
In-Reply-To: <D6CEB0A4-BD34-4347-BD2B-B25DF5E3535C@stanleylieber.com>
On Wed, 14 Jul 2021 21:20:03 -0400
Stanley Lieber <sl@stanleylieber.com> wrote:
> you're not the only one. list delivery is currently a shambles owing
> transient send failures to known good hosts. messages seem to
> (eventually) get through.
If it's any help, it looks like 1ess.inri.net is sending some invalid
SMTP command. I'm seeing a bunch of these 500 errors being returned
on my mail server:
result="500 5.5.1 Invalid command: Command unrecognized"
I've turned on SMTP tracing, and can send more info if its helpful.
Just need to wait for another email to come through.
next prev parent reply other threads:[~2021-07-15 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 23:50 Jonas
2021-07-14 23:59 ` Kurt H Maier
2021-07-15 1:20 ` Stanley Lieber
2021-07-15 14:07 ` John Murphy [this message]
2021-07-15 14:54 ` ori
2021-07-16 14:50 ` John Murphy
2021-07-16 18:06 ` sl
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=20210715100703.44159bde@x1c.home.jtm.cx \
--to=me@jtm.cx \
--cc=9front@9front.org \
--cc=sl@stanleylieber.com \
/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).