From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christophe Pettus <xof@thebuild.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
        =?utf-8?Q?C=C3=A9lestin_Matte?= <celestin.matte@cmatte.me>,
        Magnus Hagander <magnus@hagander.net>, pgsql-www@lists.postgresql.org
Subject: Re: [PATCH] pgarchives: parser: handle messages in which Message-ID
 is missing
In-reply-to: <180139C3-7E0D-4ADC-BB68-FC91D8329C94@thebuild.com>
References: <202111041947.x5su2sdjdx74@alvherre.pgsql>
 <180139C3-7E0D-4ADC-BB68-FC91D8329C94@thebuild.com>
Comments: In-reply-to Christophe Pettus <xof@thebuild.com>
	message dated "Thu, 04 Nov 2021 12:56:06 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <350163.1636057714.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 04 Nov 2021 16:28:34 -0400
Message-ID: <350164.1636057714@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/350164.1636057714%40sss.pgh.pa.us>
Precedence: bulk

Christophe Pettus <xof@thebuild.com> writes:
>> On Nov 4, 2021, at 12:47, Alvaro Herrera <alvherre@alvh.no-ip.org> wrot=
e:
>> Maybe pglister should refuse to deliver messages that don't contain
>> a Message-Id.

> That seems reasonable.  If there's no message ID by the time pglister ge=
ts it, something is pretty broken along the path from the sender to us.

FWIW, I've long used a spam filtering rule that sends anything without
a message ID, or with a forged local message ID, straight to /dev/null.
It's quite effective, and I've not seen it eat any valid traffic.

			regards, tom lane