From: Thomas Guyot-Sionnest <thomas@guyot-sionnest.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Derrick Stolee <stolee@gmail.com>
Subject: Re: Large delays in mailing list delivery?
Date: Sat, 4 Dec 2021 11:51:43 -0500 [thread overview]
Message-ID: <2cd4a07b-6ffe-15f9-c8d4-fab322a79d2f@guyot-sionnest.net> (raw)
In-Reply-To: <20211203195856.7lfcy4gfvheb7lau@meerkat.local>
On 2021-12-03 14:58, Konstantin Ryabitsev wrote:
> On Fri, Dec 03, 2021 at 11:52:58AM -0800, Elijah Newren wrote:
>> Are there some rather large delays in mailing list delivery these
>> days? Anyone know who to contact to investigate? [*]
> The right person to contact is postmaster@vger.kernel.org, however I can
> actually answer your question (despite not actually being in charge of
> vger.kernel.org). Periodically, Gmail decides that there's just too much
> incoming mail for some accounts and will arbitrarily delay delivery by
> returning a "this account is receiving too much mail, please try later."
>
> I am willing to bet that this is what happened to you.
I have already contacted postmaster and they are aware, however you add
very good point. Somehow I knew it but it's the way you put it that made
me realize: the emails are sent in bulk to gmail (to many or all
recipients for a single copy at once). The mail header even shows this,
listing the first recipient followed by "+ 99 others". If it's delayed
for all because of a single recipient that can only be because the 4xx
error is returned at the end of the DATA command (rather than on a
specific RCPT TO command), so no way for the sender to retry that single
faulty address alone later.
I'm not sure if their software allows it but I suggested sending to a
single recipient at a time for gmail, that would solve the issue.
In the meantime what I did is switch my subscription to another email
using a forwarder address on a domain I own - I still haven't received
all the backlog but at least I'm getting new posts timely now.
Regards,
--
Thomas
next prev parent reply other threads:[~2021-12-04 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 19:52 Large delays in mailing list delivery? Elijah Newren
2021-12-03 19:58 ` Konstantin Ryabitsev
2021-12-04 16:51 ` Thomas Guyot-Sionnest [this message]
2021-12-03 20:02 ` Ævar Arnfjörð Bjarmason
2021-12-03 20:24 ` Konstantin Ryabitsev
2021-12-03 20:26 ` Ævar Arnfjörð Bjarmason
2021-12-03 21:52 ` Jeff King
2021-12-06 16:12 ` Ævar Arnfjörð Bjarmason
2021-12-06 16:36 ` Eric Wong
2022-02-02 9:34 ` Using public-inbox+lei+Emacs+mu+mu4e (was: Large delays in mailing list delivery?) Ævar Arnfjörð Bjarmason
2022-02-07 21:27 ` Eric Wong
2021-12-07 4:20 ` Large delays in mailing list delivery? Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd4a07b-6ffe-15f9-c8d4-fab322a79d2f@guyot-sionnest.net \
--to=thomas@guyot-sionnest.net \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).