[eliz@gnu.org: Re: [PATCH] gdb: Add missing single quotation mark in README]

[eliz@gnu.org: Re: [PATCH] gdb: Add missing single quotation mark in README]

[Eli Zaretskii]

[-- Attachment #1: Type: text/plain, Size: 560 bytes --]

Hi,

Since a few days ago, email messages from me to the gdb-patches
mailing list are delayed by several days.  I attach below an example
of a message that I got back from the list only today, 4 days(!) after
it was sent.  I also get a lot of messages from mailer-daemon@gnu.org
telling me that a message I sent is delayed because it could not be
delivered.  The gdb-patches@sourceware.org is the only address with
which this happens; the rest of my email delivery works just fine

Why is that happening?  What could be done to avoid these problems?

Thanks.


[-- Attachment #2: Type: message/rfc822, Size: 471 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add missing single quotation mark in README
Date: Thu, 09 May 2024 12:48:04 +0300

> From: Tiezhu Yang <yangtiezhu@loongson.cn>
> Date: Thu,  9 May 2024 16:35:10 +0800
> 
> Maybe forgot to add a single quotation mark for --with-system-zlib
> in commit 7f0bd4202c23 ("Update gdb's configure instructions"), just
> add it.

Thanks, fixed.

Re: [eliz@gnu.org: Re: [PATCH] gdb: Add missing single quotation mark in README]

[Mark Wielaard]

Hi Eli,

(Adding Ian to CC because we probably need some logs from eggs)

On Mon, 2024-05-13 at 13:47 +0300, Eli Zaretskii via Overseers wrote:
> Since a few days ago, email messages from me to the gdb-patches
> mailing list are delayed by several days.  I attach below an example
> of a message that I got back from the list only today, 4 days(!) after
> it was sent.  I also get a lot of messages from mailer-daemon@gnu.org
> telling me that a message I sent is delayed because it could not be
> delivered.  The gdb-patches@sourceware.org is the only address with
> which this happens; the rest of my email delivery works just fine
> 
> Why is that happening?  What could be done to avoid these problems?

Odd. First note that the message as you attached has Message-
Id:	<b0bfdbf450011acd857daf6ea986c9a816939325.camel@gnu.org>
But that seems bogus?
The message you are referencing seems to be:
https://inbox.sourceware.org/gdb-patches/8634qr71uz.fsf@gnu.org/raw
So Message-Id: <8634qr71uz.fsf@gnu.org>

That message only arrived at sourceware on May 13th:

Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
	by sourceware.org (Postfix) with ESMTPS id 379703861893
	for <gdb-patches@sourceware.org>; Mon, 13 May 2024 09:56:44 +0000 (GMT)

And I cannot find any earlier references in the logs at sourceware server2.

But it seems to have been received at eggs on May 9th:

Received: from fencepost.gnu.org ([2001:470:142:3::e])
	by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.90_1)
	(envelope-from <eliz@gnu.org>)
	id 1s50Nk-00086X-TB; Thu, 09 May 2024 05:48:08 -0400

I have no idea why eggs held onto it for 4 days.
Ian, can you see? Did we block eggs for some reason?

Cheers,

Mark

Re: [eliz@gnu.org: Re: [PATCH] gdb: Add missing single quotation mark in README]

[Mark Wielaard]

Hi,

On Tue, 2024-05-14 at 14:38 +0200, Mark Wielaard via Overseers wrote:
> On Mon, 2024-05-13 at 13:47 +0300, Eli Zaretskii via Overseers wrote:
> > Since a few days ago, email messages from me to the gdb-patches
> > mailing list are delayed by several days.  I attach below an example
> > of a message that I got back from the list only today, 4 days(!) after
> > it was sent.  I also get a lot of messages from mailer-daemon@gnu.org
> > telling me that a message I sent is delayed because it could not be
> > delivered.  The gdb-patches@sourceware.org is the only address with
> > which this happens; the rest of my email delivery works just fine
> > 
> > Why is that happening?  What could be done to avoid these problems?
> [...]
> I have no idea why eggs held onto it for 4 days.
> Ian, can you see? Did we block eggs for some reason?

Just for the record after looking at the logs of both machines we
figured out what seemed to be happening. eggs.gnu.org is a secondary MX
for gcc.gnu.org (== sourceware.org). Spammers tried to sent email to
gcc mailinglists through eggs which forwarded some which sourceware
then marked as spam. If too much got through sourceware MX would
trigger a postfix fail2ban rule and eggs would get blocked. Since eggs
also handles all @gnu.org emails that would then delay/block any emails
from @gnu.org to @sourceware.org/gcc.gnu.org.

Urgh :{

eggs.gnu.org has been added to the fail2ban ignoreip conf.

Cheers,

Mark