From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] mailing list issues
Date: Tue, 08 Jun 2021 20:43:02 -0400 [thread overview]
Message-ID: <F85E8565-B17B-4A51-9271-5130B6D0E614@stanleylieber.com> (raw)
In-Reply-To: <15d99d40-eda7-4253-a439-4aedade77700@sirjofri.de>
On June 8, 2021 3:41:59 PM EDT, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>
>08.06.2021 20:11:28 Stanley Lieber <sl@stanleylieber.com>:
>
>> messages arrive out of order. messages arrive late. messages don't
>> arrive at all.
>>
>> I see a lot of stuff like:
>>
>> 1ess Jun 8 14:10:41 delivery '/net.alt/dns' does not exist ([known
>> good hostname])
>
>I know this error very well as I noticed it some time ago. I don't know
>exactly what causes it, afaik /net.alt is asked when /net/dns isn't
>available (which is never the case on my machine). So I assume the error
>message is misleading.
>
>The messages are then stored in /mail/queue for the next time, which
>might be the cause for the wrong order of messages.
>
>In my experience this happens a lot and under uncertain circumstances.
>Even if both servers are 9front/upas and dns records are set up properly
>the error can happen.
>
>Most of the time I was personally able to ignore them, sending messages
>again if they aren't sent. But that's only on my private server.
>
>sirjofri
>
pretty much yes, this exactly. because we have a large number of subscribers (over 700), things get quite jumbled up.
sl
prev parent reply other threads:[~2021-06-09 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 18:11 Stanley Lieber
2021-06-08 19:07 ` Julien Blanchard
2021-06-08 20:31 ` Stanley Lieber
2021-06-08 23:00 ` Toby
2021-06-08 19:41 ` sirjofri
2021-06-09 0:43 ` Stanley Lieber [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F85E8565-B17B-4A51-9271-5130B6D0E614@stanleylieber.com \
--to=sl@stanleylieber.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).