lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f863bcd-7926-4504-8ff0-3b20debaf107@redhat.com>
Date: Thu, 5 Dec 2024 16:52:45 +0100
From: David Hildenbrand <david@...hat.com>
To: Benjamin LaHaise <bcrl@...ck.org>, Vlastimil Babka <vbabka@...e.cz>
Cc: linux-kernel@...r.kernel.org, Matthew Wilcox <willy@...radead.org>,
 linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
 Oscar Salvador <osalvador@...e.de>, Zi Yan <ziy@...dia.com>
Subject: Re: linux-mm mailing list problems

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@...ck.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@...ck.org?
> 
> Use owner-linux-mm@...ck.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@...ck.org, but I am pretty sure that is the wrong address.
> 
> mbot@...ck.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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ