Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Florian Weimer via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
Cc: Lancelot SIX <lsix@lancelotsix.com>, schwab@linux-m68k.org
Subject: Re: Problems with email delivery from sourceware?
Date: Tue, 15 Jun 2021 22:32:48 +0200	[thread overview]
Message-ID: <87im2eg973.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <83zgvr2fl2.fsf@gnu.org> (Eli Zaretskii via Gdb-patches's message of "Tue, 15 Jun 2021 20:38:33 +0300")

* 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,
Florian


  parent reply	other threads:[~2021-06-15 20:34 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 [this message]
2021-06-19 12:28           ` Eli Zaretskii via Gdb-patches
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=87im2eg973.fsf@oldenburg.str.redhat.com \
    --to=gdb-patches@sourceware.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