public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: Matthias van de Meent <[email protected]>
Cc: [email protected]
Subject: Re: Mailing list subscription's mail delivery delays?
Date: Mon, 02 Oct 2023 16:52:48 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEwGPj-UXWM=WZGd5C3oDXvCv4KVHJA111PSdka=zvbJqQ@mail.gmail.com>
References: <CAEze2Wi08Zw4BFfWaVMR1ufe9jhsbqYZtnBhOCyDsZLp-accXg@mail.gmail.com>
<CAKFQuwZtPAoXi1OgeQL19ybix8fPe3u379C0S_8mAsH02PvjMg@mail.gmail.com>
<[email protected]>
<CABUevEwGPj-UXWM=WZGd5C3oDXvCv4KVHJA111PSdka=zvbJqQ@mail.gmail.com>
Magnus Hagander <[email protected]> writes:
> On Fri, Sep 29, 2023 at 1:11 AM Tom Lane <[email protected]> wrote:
>> I have been seeing the same thing for a few days now, on my
>> definitely-not-gmail personal server. Something's flaky in the
>> PG mail infrastructure. It's gotten better since yesterday's
>> outage, though I'm not convinced it's totally fixed.
> There have been some pretty bad issues with gmail recently. Some
> changes have been deployed that will hopefully help mitigate those and
> make things better, but it takes time to recover.
> The massive backlogs caused by gmail have been enough to spill over
> and affect other destinations as well simply due to the load created
> since we have such a huge number of gmail subscribers. But we're
> slowly seeing the backlogs shrink now and the load come down so
> hopefully the changes made will continue to have effect and let us be
> back to normal soon.
I'm still seeing multi-hour delivery delays on a subset of traffic,
like maybe half a dozen instances today.
Looking at the Received: timestamps shows pretty conclusively that
the delays are within PG infra, for example this recent message from
Heikki got hung up at two separate jumps:
Return-Path: <[email protected]>
Received: from malur.postgresql.org (malur.postgresql.org [217.196.149.56])
by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTPS id 392HruLZ2135620
(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT)
for <[email protected]>; Mon, 2 Oct 2023 13:53:57 -0400
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
by malur.postgresql.org with esmtp (Exim 4.94.2)
(envelope-from <[email protected]>)
id 1qnN7D-00GbGd-FB
for [email protected]; Mon, 02 Oct 2023 17:53:55 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[email protected]>)
id 1qnGcb-00AqOg-Ti
for [email protected]; Mon, 02 Oct 2023 10:57:53 +0000
Received: from meesny.iki.fi ([195.140.195.201])
by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[email protected]>)
id 1qnF5S-007kvc-AQ
for [email protected]; Mon, 02 Oct 2023 09:19:35 +0000
Received: from [192.168.1.115] (dsl-hkibng22-54f8db-125.dhcp.inet.fi [84.248.219.125])
(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
(Authenticated sender: hlinnaka)
by meesny.iki.fi (Postfix) with ESMTPSA id 4Rzb4d51FBzydx;
Mon, 2 Oct 2023 12:19:29 +0300 (EEST)
Message-ID: <[email protected]>
Date: Mon, 2 Oct 2023 12:19:29 +0300
...
Also, my own message <[email protected]> went
out to -hackers about 25 minutes ago and hasn't come back,
so based on other recent examples I'm betting I won't see it
for hours.
Plenty of other traffic *is* coming through in normal-ish time,
so I'm not sure I buy that there's still a massive logjam.
regards, tom lane
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Mailing list subscription's mail delivery delays?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox