From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Mailing List missing messages
Date: Fri, 15 Sep 2023 10:06:12 +0200 [thread overview]
Message-ID: <1694764946@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <cb777ab6-f1c5-4b8b-b3a9-2304e2ea9aec@gmail.com>
Leonidas Spyropoulos wrote...
> I've noticed the Mailing List archives contain messages I never received
> in my email. Anyone else experienced this issue?
This may or may not be related to what's written in
https://social.afront.org/@warthog9/111050845570244562
| Well, vger (as of right now) no longer directly attempts to deliver to
| gmail/google/googlemail just to get the ridiculous backlog out of the primary
| mail paths. Vger (1 machine) is kicking all of that queue over to 8 other
| machines and letting them go try to get that delivered and queue up somewhere
| where it's not going to cause everyone else pain.
|
| This should, at least for now, settle out several things, but if you are
| seeing mail wonkiness give postmaster@ a ping and I'll take a look.
|
| Also if you are on Gmail and doing kernel dev, might be worth looking at other
| email providers.
And a follow-up:
| All of this would be workable if there was a means to reach out, but that's
| particularly hard and slow with them. So yeah there's thousands of gmail users
| I can absolutely confirm haven't been getting vger related traffic because of
| the push backs and there's little from the vger end we can do about it.
next prev parent reply other threads:[~2023-09-15 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 14:13 Mailing List missing messages Leonidas Spyropoulos
2023-09-15 8:06 ` Christoph Biedl [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-11 17:14 Leonidas Spyropoulos
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=1694764946@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=artafinde@gmail.com \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.