From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DCC511F543 for ; Wed, 7 Jun 2023 13:45:34 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=KffZxm5l; dkim-atps=neutral Received: by mail-qt1-x82f.google.com with SMTP id d75a77b69052e-3f7f73e90f9so61548561cf.2 for ; Wed, 07 Jun 2023 06:45:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1686145533; x=1688737533; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=InXSLCHHrkv3wx3CUZrLA8cI2fjxaFvQ0hUm72eGvjs=; b=KffZxm5lQg/VPiSvMd3WNOfHhGyPnWlsI0TuEJXPY/ZKTL005x8Y8Ik7rWWDtF6ihx onFMVowLcfEJ6095cjv4XAnvjjgPFdgeJZBJQThoSAJBYZX1i35Vm2FNxPER3Bk8/8Yu YNr7GVcGD4vF/+3bq87f98+Y7zB/hFm+XQyU0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686145533; x=1688737533; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=InXSLCHHrkv3wx3CUZrLA8cI2fjxaFvQ0hUm72eGvjs=; b=BXY0VXJam/JgNdULkjV7yxpPiZrmldl9fYRxi85Zoosm7OoZKl+9oipGYi7Yw9HVEG r7VTpmWMJ686YPu8bnzHCQuPzDhgRn2kMk6Lc/AAHGD4feIivuDgnrSHhTff4XpEZacP dhHR7EVHts/WmOe0s1JmGO0uekZd0pPfphPb/TATp8WtXlYI3aLLCOUfLW4Tj7BNvBr6 YcaK7eXCIMtLaCtzY2PpNZTwNf/ItV20Aw9F0lTAEB0KV6UnVfjYnue2sz/lW8bOVEF6 WLJOYJ9LEWk2DyiuVSAJhqdHk2reCAPpacQxAtoOl9J3pLdocTLrCLEJGXHZ6Q97FGX3 JwLw== X-Gm-Message-State: AC+VfDwBdary40DyGi9k7qipIOA28eCIKBjRnG9vCjp9f3nrEjcipafm VDTsmSXm6Jxbdi31ICAd+fSJ8g== X-Google-Smtp-Source: ACHHUZ5Ylt61FcBBs9wUp03q1v0EiZVRpGnprBZFxxuH3ampPetLSjkF70+9T7S3m+/mPXTZS2kJ3w== X-Received: by 2002:ac8:5e4e:0:b0:3f8:6f77:29f1 with SMTP id i14-20020ac85e4e000000b003f86f7729f1mr3977766qtx.49.1686145533330; Wed, 07 Jun 2023 06:45:33 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-30-209-226-106-132.dsl.bell.ca. [209.226.106.132]) by smtp.gmail.com with ESMTPSA id fw15-20020a05622a4a8f00b003f8e6071e43sm3343650qtb.3.2023.06.07.06.45.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 07 Jun 2023 06:45:32 -0700 (PDT) Date: Wed, 7 Jun 2023 09:45:31 -0400 From: Konstantin Ryabitsev To: "Yin, Fengwei" Cc: Eric Wong , meta@public-inbox.org Subject: Re: https://lore.kernel.org/linux-mm/ Message-ID: <20230607-silenced-impromptu-478c52@meerkat> References: <050c9cdf-d311-797f-89d7-56fd67c8daf6@intel.com> <20230607000743.M229994@dcvr> <24247bcd-3b57-beac-7b8b-ab31d7d2b669@intel.com> <20230607023016.M573921@dcvr> <844f09ab-8a21-063b-3a81-aa655ab4a523@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <844f09ab-8a21-063b-3a81-aa655ab4a523@intel.com> List-Id: 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