From: David Hildenbrand <david@redhat.com>
To: Benjamin LaHaise <bcrl@kvack.org>, Vlastimil Babka <vbabka@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>, Zi Yan <ziy@nvidia.com>
Subject: Re: linux-mm mailing list problems
Date: Thu, 5 Dec 2024 16:52:45 +0100 [thread overview]
Message-ID: <4f863bcd-7926-4504-8ff0-3b20debaf107@redhat.com> (raw)
In-Reply-To: <20241205154213.GA5247@kvack.org>
On 05.12.24 16:42, Benjamin LaHaise wrote:
> On Thu, Dec 05, 2024 at 03:43:54PM +0100, Vlastimil Babka wrote:
>> On 12/5/24 13:12, David Hildenbrand wrote:
>>> On 05.12.24 09:52, David Hildenbrand wrote:
>>>> Sending this via the RH SMTP first, because IT doesn't see any obvious
>>>> problems why the mails shouldn't be reaching linux-mm, so let's see if
>>>> the problems are gone now. If this doesn't work, I'll resend them
>>>> using the known-working gmail SMTP. Sorry already for the noise ...
>>>
>>> I talked to RH IT, and it looks like the mails get delivered to
>>> linux-mm@kvack.org just fine, and linux-mm decides to silently drop them.
>
> Messages were being dumped into a spam folder as the upstream spam
> filtering service used for kvack.org was incorrectly tagging them as spam.
> The folder where these messages were being quarantined in was not the one
> being checked for the last few months due to the spam tagging changing
> back on September 8th.
Ah that explains it,
>
>>> Does anybody know who maintains linux-mm@kvack.org?
>
> Use owner-linux-mm@kvack.org, which has been in place since the mailing
> list was first created. That is the sender of every mailing list message.
Ah!
>
> Unfortunately, the issue was not flagged to me until today. The mailing
> list footers that used to let people know about the mailing list contact
> info previously had to be removed due to the implementation of DKIM
> enforcement. Even sending emails to majordomo@ per the List-Subscribe:
> and List-Unsubscribe: headers would have gotten my attention.
Yeah, I tried hard finding a contact, and apparently ...
>
>>> I wrote a mail to
>>> mbot@kvack.org, but I am pretty sure that is the wrong address.
>
> mbot@kvack.org is a spam trap. Do not send emails there unless you want
> to be marked as a spam sender.
... all I found was a trap :)
(guess I'm now a swam sender ;) )
>
>> AFAIK it's Benjamin, CC'd
>
> It should now be fixed as I have tweaked the spam filtering rules.
Thanks!
> The
> messages misfiled as spam since September 8th have now been delivered.
> I'm shocked that nobody bothered reporting this until now.
Hm, I sent quite a bunch of patches after September 8th, and I think
they mostly got delivered. For me, it started ~1 week ago.
> Please do not
> report mailing list issues to the mailing list. I simply do not have the
> time / energy to scan the thousands of messages that fly by every week.
Now that I know how to contact you, that will obviously be my first choice.
Thanks!
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-12-05 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:52 [PATCH v1 0/2] mm: don't use __GFP_HARDWALL when migrating remote pages David Hildenbrand
2024-12-05 8:52 ` [PATCH v1 1/2] mm/page_alloc: don't use __GFP_HARDWALL when migrating pages via alloc_contig*() David Hildenbrand
2024-12-09 7:47 ` Oscar Salvador
2024-12-05 8:52 ` [PATCH v1 2/2] mm/memory_hotplug: don't use __GFP_HARDWALL when migrating pages via memory offlining David Hildenbrand
2024-12-09 7:48 ` Oscar Salvador
2024-12-05 12:12 ` linux-mm mailing list problems David Hildenbrand
2024-12-05 14:43 ` Vlastimil Babka
2024-12-05 15:42 ` Benjamin LaHaise
2024-12-05 15:52 ` David Hildenbrand [this message]
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=4f863bcd-7926-4504-8ff0-3b20debaf107@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox