From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] mailing list issues
Date: Tue, 08 Jun 2021 16:31:53 -0400 [thread overview]
Message-ID: <C50E3D13-75D0-4A7B-BB74-5DD3CB9E96EA@stanleylieber.com> (raw)
In-Reply-To: <C0673D8E-0FC1-41C6-85B8-05490FF10AFD@typed-hole.org>
On June 8, 2021 3:07:10 PM EDT, Julien Blanchard <julien@typed-hole.org> wrote:
>
>> Le 8 juin 2021 à 20:37, Stanley Lieber <sl@stanleylieber.com> a écrit :
>>
>> 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])
>>
>> in the logs.
>>
>> sl
>
>Not sure it can help (I don’t know much about email) but I got DMARC issues every time I sent an email to the list when a year earlier it seemed to work fine. From my server that is so maybe I’m at fault here.
>
>—
>julienxx
>
upas can't do any kind of dmarc at all.
trouble amplified when we moved off of ramnode ssd-backed disk to 9cloud. we had similar problems years ago when we were on 9cloud before we moved to ramnode.
the way mail is sent, runq hammered the disk, which severely tanked performance on spinning platter disks. we tinkered with it a bit and arrived at the current situation, where sending a message to a list no longer brings the entire system to a crawl, but still exhibits the same other defects.
we ignored this problem for years by throwing an ssd at it.
not much investigation has gone into wtf is going on, but now more people have cpu access to 1ess (mail and web server), so maybe somebody feels like taking a look.
sl
next prev parent reply other threads:[~2021-06-08 20:54 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 [this message]
2021-06-08 23:00 ` Toby
2021-06-08 19:41 ` sirjofri
2021-06-09 0:43 ` Stanley Lieber
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=C50E3D13-75D0-4A7B-BB74-5DD3CB9E96EA@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).