From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: lsix@lancelotsix.com, schwab@linux-m68k.org, gdb-patches@sourceware.org
Subject: Re: Problems with email delivery from sourceware?
Date: Sat, 19 Jun 2021 15:28:42 +0300 [thread overview]
Message-ID: <83mtrmvy11.fsf@gnu.org> (raw)
In-Reply-To: <87im2eg973.fsf@oldenburg.str.redhat.com> (message from Florian Weimer on Tue, 15 Jun 2021 22:32:48 +0200)
> From: Florian Weimer <fweimer@redhat.com>
> Cc: Lancelot SIX <lsix@lancelotsix.com>, Eli Zaretskii <eliz@gnu.org>,
> schwab@linux-m68k.org
> Date: Tue, 15 Jun 2021 22:32:48 +0200
>
> * Eli Zaretskii via Gdb-patches:
>
> > But if I was the only one who experienced these strange delays, then I
> > don't want to waste bandwidth on these issues anymore. Thanks for
> > taking the time to look at the message I sent as an example.
>
> I encountered similar delays just before VERP was enabled for
> sourceware.org. Apparently it was not possible to figure out the cause
> of the mail delays based on the available Postfix logs. As I result, I
> don't know if it was Red Hat's email infrastructure or sourceware that
> caused the delay. Like in your case, the Received: lines only showed
> that the hand-off between the two domains did not happen in a timely
> fashion.
Thanks.
FYI: I asked the gnu.org sysadmins, and they replied that something
went wrong with sourceware.org's mail server, which caused the email
from there to trigger the fail2ban rule on gnu.org mail servers. The
solution was to unban and whitelist sourceware.org.
So yes, both sourceware.org and gnu.org mail delivery were parts of
the puzzle here.
next prev parent reply other threads:[~2021-06-19 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 16:12 Eli Zaretskii via Gdb-patches
2021-06-15 16:33 ` Andreas Schwab
2021-06-15 16:52 ` Eli Zaretskii via Gdb-patches
2021-06-15 17:14 ` Lancelot SIX via Gdb-patches
2021-06-15 17:38 ` Eli Zaretskii via Gdb-patches
2021-06-15 17:59 ` Andreas Schwab
2021-06-15 20:32 ` Florian Weimer via Gdb-patches
2021-06-19 12:28 ` Eli Zaretskii via Gdb-patches [this message]
2021-06-17 6:48 ` Eli Zaretskii via Gdb-patches
2021-06-17 10:28 ` Pedro Alves
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=83mtrmvy11.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=fweimer@redhat.com \
--cc=lsix@lancelotsix.com \
--cc=schwab@linux-m68k.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