From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] transient dns errors cause smtp failure
Date: Sat, 6 Feb 2021 11:24:20 +0100 [thread overview]
Message-ID: <CAFSF3XMqTzzEUg7yuRyUp-N8-wAz=bfBrouXfVJGd87Fap0cog@mail.gmail.com> (raw)
In-Reply-To: <AA6C8542-852B-49E9-8AA9-404ADB99FF96@stanleylieber.com>
these 3 messages here all arrived in less than 3 minutes \o/
On 2/6/21, Stanley Lieber <sl@stanleylieber.com> wrote:
> On February 6, 2021 1:17:11 AM EST, ori@eigenstate.org wrote:
>>Quoth Stanley Lieber <sl@stanleylieber.com>:
>>> example:
>>>
>>> /mail/queue/none/E.808879:smtp: '/net.alt/dns' does not exist
>>> (net!a-b.xyz)
>>>
>>> how/why might this be happening?
>>>
>>> note: i don't use /net.alt at all.
>>>
>>> sl
>>>
>>
>>I think dial just uses /net.alt if /net fails,
>>and the error includes the last thing it tried.
>>
>> /net => nope, try /net.alt
>> /net.alt => nope, couldn't dial on /net.alt
>>
>>other than /net.alt appearing in the error message,
>>are things working as expected?
>>
>>
>
> subjectively the list has seemed fine to me over the past couple days, but
> still getting reports of (sometimes very) delayed receipt of messages for
> others subscribed to the list. checked one complainer in the logs and found
> 19 E files all with this error. same for some other (known good) domains.
>
> presently i have runq cranked to -n 80 with no immediately observable ill
> effects.
>
> sl
>
next prev parent reply other threads:[~2021-02-06 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 1:59 Stanley Lieber
2021-02-06 6:17 ` ori
2021-02-06 7:19 ` Stanley Lieber
2021-02-06 10:24 ` hiro [this message]
2021-02-06 15:03 ` sirjofri
2021-02-06 16:41 ` sirjofri
[not found] <1B74CAEE535895AEA8BD0EFB600EF335@hog>
2021-02-07 16:53 ` Stanley Lieber
2021-02-09 15:58 ` kvik
2021-02-09 16:41 ` Stanley Lieber
2021-02-10 15:24 ` Stanley Lieber
2021-02-10 16:30 ` ori
2021-02-17 23:14 ` sl
2021-02-17 23:55 ` ori
2021-02-19 6:54 ` cinap_lenrek
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='CAFSF3XMqTzzEUg7yuRyUp-N8-wAz=bfBrouXfVJGd87Fap0cog@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).