Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlztO-005CrY-Hb for pgsql-www@arkaria.postgresql.org; Thu, 28 Sep 2023 22:53:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlztM-00H3wX-Hm for pgsql-www@arkaria.postgresql.org; Thu, 28 Sep 2023 22:53:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlztM-00H3wH-9g for pgsql-www@lists.postgresql.org; Thu, 28 Sep 2023 22:53:56 +0000 Received: from mail-oo1-xc2c.google.com ([2607:f8b0:4864:20::c2c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qlztJ-008Af4-DY for pgsql-www@postgresql.org; Thu, 28 Sep 2023 22:53:55 +0000 Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-57ba2cd3507so5390478eaf.2 for ; Thu, 28 Sep 2023 15:53:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695941631; x=1696546431; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=513Zvid0f5bFO1hKuAwka3tZaUtM8b5kPlfXgxkhFfo=; b=jRZ+thI9Vgv911XdY2aNsgNb3L90iN9r0tfKeQwauKWuJBeWV4xy+O3l8fT97mwLm+ +tb8qni7fnOpL9+9d/LayTn7W79s/Y7/v6nEdppA26nhLGJnydYvaEVpjHjblKuRzaZc FFGfV9V4ZLVnJz1FI5uj1DMFuNroei4n536ygHdmZry/K9qLCZ8gC4x9v0mutwqiFFHv 2IK5WPD8zMwQeT615cTJsBxGsmO3NSzaN1087x3B+AoinM6CpX1/srj15ONzfXGyqX3k 31gRdfGbcsfBK7MGp8rdFia4UeQZAJ35+4wwVkv8aIFEZxHCveywAwgrYw+2MbD2hF9Q gV2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695941631; x=1696546431; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=513Zvid0f5bFO1hKuAwka3tZaUtM8b5kPlfXgxkhFfo=; b=GXO4dIwQz/Srig+qhkuIe5+rKWZ4kGulynsiRH1qJkYXx7zLmxnZXSIV4BPTvBAwuA 0N+nnFgUgBHKUsz03nWwUVPfWYZ6pf+Yeg9T4oY5klTKd853KKKsAmnnKKrSwT7uG2/r x76JUfG1pIKreJC5aCUMtkeclsgkewaU9Vke8duaGgmYHq+w5Qo3OD+9FteGSdqpK8el sSk0u7bFZBsJzviPqComfrViJDmG16dilG0Ub6EYMdoP5A1U8GXbfe7Fc0dAIzTwNn55 2YjqKvAhk3obMwj79LJv8Yj2CX+ZWNJDLVBNxX0x0EvIX2ugl0srVNIKKfEKIZpOq2Nq gjxw== X-Gm-Message-State: AOJu0Yy26C+rhul74XmVBXPG4mQkKsAhJR0lFolecD9wX3yoeM75T3n6 spbcUYMgoRfGVHQ0xLG24BXb1LV4u1ltWBo4xSE= X-Google-Smtp-Source: AGHT+IEUhEoKpAQh1iG5+dFsy8/00ES1tykNhJPAdS5sAu8M/75VzeVtFtouglhjwurW4mmagr0uQymdB14zsPHkgH0= X-Received: by 2002:a4a:d1c7:0:b0:57b:f285:ae41 with SMTP id a7-20020a4ad1c7000000b0057bf285ae41mr2833126oos.9.1695941630731; Thu, 28 Sep 2023 15:53:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Thu, 28 Sep 2023 15:53:32 -0700 Message-ID: Subject: Re: Mailing list subscription's mail delivery delays? To: Matthias van de Meent Cc: pgsql-www@postgresql.org Content-Type: multipart/alternative; boundary="00000000000075ab510606732ee9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000075ab510606732ee9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Sep 28, 2023 at 3:48=E2=80=AFPM Matthias van de Meent < boekewurm+postgres@gmail.com> wrote: > I'm not sure if the issue is on my side (mail servers are gmail's) or > on the mailing list server - all traces I've checked indicate that the > delay is somewhere in the delivery from postgres' last mail server to > the first gmail mail server. > > I've only really noticed this sometime in the past few weeks. After > sampling my mails, I found other examples of significant delays (>1h) > for mails from well-respected hackers dating back to at least > 2023-08-28. > I have noticed the same thing happening for the Gmail account that I use. David J. --00000000000075ab510606732ee9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Sep 28, 2023 at 3:48=E2=80=AFPM Matthias van de Me= ent <boekewurm+postgre= s@gmail.com> wrote:
I'm not sure if the = issue is on my side (mail servers are gmail's) or
on the mailing list server - all traces I've checked indicate that the<= br> delay is somewhere in the delivery from postgres' last mail server to the first gmail mail server.

I've only really noticed this sometime in the past few weeks. After
sampling my mails, I found other examples of significant delays (>1h) for mails from well-respected hackers dating back to at least
2023-08-28.

I have noticed the same = thing happening for the Gmail account that I use.

Davi= d J.

--00000000000075ab510606732ee9--