From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, gdb-patches@sourceware.org
Subject: Re: Problems with email delivery from sourceware?
Date: Tue, 15 Jun 2021 18:14:10 +0100 [thread overview]
Message-ID: <20210615171410.kv7wzwxuj7uhw3cc@gwenhwyvar> (raw)
In-Reply-To: <838s3b3w9h.fsf@gnu.org>
Hi Eli,
From what I can see, I received this message on time. It reached my mail
server on “Fri, 11 Jun 2021 21:08:41 +0000 (UTC)”.
The delay you had was before the mail could reached eggs.gnu.org. Any
chance this host had issues during last week?
Lancelot.
On Tue, Jun 15, 2021 at 07:52:58PM +0300, Eli Zaretskii via Gdb-patches wrote:
> > From: Andreas Schwab <schwab@linux-m68k.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>
> > Date: Tue, 15 Jun 2021 18:33:07 +0200
> >
> > On Jun 15 2021, Eli Zaretskii via Gdb-patches wrote:
> >
> > > Is (or was?) something wrong with email delivery from sourceware? I'm
> > > receiving only now some emails that were sent to the list 4 days ago.
> >
> > Any example?
>
> I attach one such email below.
>
> > > The headers clearly show that the email messages were stuck on
> > > sourceware.org for all those 4 days.
> >
> > Are you sure they were stuck @sourceware.org, and not just delayed by
> > the next hop?
>
> I could be misinterpreting the headers, so please see for yourself.
>
> Thanks.
>
next prev parent reply other threads:[~2021-06-15 17:14 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 [this message]
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
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=20210615171410.kv7wzwxuj7uhw3cc@gwenhwyvar \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--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