From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] transient dns errors cause smtp failure
Date: Tue, 09 Feb 2021 16:58:41 +0100 [thread overview]
Message-ID: <0951F0EBDBBBBC7C75B4042E1D52878F@hog> (raw)
In-Reply-To: <477917F0-25D1-481A-8CF7-F371554DF2E8@stanleylieber.com>
Quoth Stanley Lieber <sl@stanleylieber.com>:
> i cranked Maxreqtm to 30*1000 and it's already making a huge difference cleaning out the queue. we'll see how it plays out.
I'm only now receiving this reply.
The list may not be fast but at least it's steaming.
next prev parent reply other threads:[~2021-02-09 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1B74CAEE535895AEA8BD0EFB600EF335@hog>
2021-02-07 16:53 ` Stanley Lieber
2021-02-09 15:58 ` kvik [this message]
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
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
2021-02-06 15:03 ` sirjofri
2021-02-06 16:41 ` sirjofri
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=0951F0EBDBBBBC7C75B4042E1D52878F@hog \
--to=kvik@a-b.xyz \
--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).