unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Yin, Fengwei" <fengwei.yin@intel.com>
Cc: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: https://lore.kernel.org/linux-mm/
Date: Wed, 7 Jun 2023 09:45:31 -0400	[thread overview]
Message-ID: <20230607-silenced-impromptu-478c52@meerkat> (raw)
In-Reply-To: <844f09ab-8a21-063b-3a81-aa655ab4a523@intel.com>

On Wed, Jun 07, 2023 at 10:41:18AM +0800, Yin, Fengwei wrote:
> > Messages on lore.kernel.org show up because an email address
> > they control receives messages from the linux-mm list.  Since
> > (I assume) kvack.org is controlled by someone else, kernel.org
> > needs to subscribe to the linux-mm list just like you or anyone
> > else.
> Oh. So the problem is kernel.org does not subscribe to linux-mm
> after May 31st? Thanks.

We had a mail server configuration problem that was a result of thousands of
zombie hosts all trying to relay mail via mail.kernel.org. This caused our
public RBL lookups to fail with "you're using us too much!" error, which
unfortunately fails in the worst possible ways -- by marking all RBL lookups
as spam.

Our monitoring quickly alerted us to this, but unfortunately we did bounce
pretty much all incoming mail for about 10-15 minutes. If there was a patch
series coming in during that time, that would have generated enough bounces to
cause the archiver address to be unsubscribed.

This is the reason why there's a gap from May 31 to June 6. If you would like
to contribute the missing messages, I'll be happy to feed them into the
archive.

-K

  reply	other threads:[~2023-06-07 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  8:05 https://lore.kernel.org/linux-mm/ Yin Fengwei
2023-06-07  0:07 ` https://lore.kernel.org/linux-mm/ Eric Wong
2023-06-07  1:39   ` https://lore.kernel.org/linux-mm/ Yin, Fengwei
2023-06-07  2:30     ` https://lore.kernel.org/linux-mm/ Eric Wong
2023-06-07  2:41       ` https://lore.kernel.org/linux-mm/ Yin, Fengwei
2023-06-07 13:45         ` Konstantin Ryabitsev [this message]
2023-06-08  1:30           ` https://lore.kernel.org/linux-mm/ Yin Fengwei
2023-06-08  6:40           ` https://lore.kernel.org/linux-mm/ Jonathan Corbet
2023-06-08 19:24             ` https://lore.kernel.org/linux-mm/ Konstantin Ryabitsev
2023-06-07  2:53       ` https://lore.kernel.org/linux-mm/ Yin, Fengwei

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: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230607-silenced-impromptu-478c52@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=fengwei.yin@intel.com \
    --cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).