| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing |
| Date: | 2021-11-04 20:28:34 |
| Message-ID: | 350164.1636057714@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Christophe Pettus <xof(at)thebuild(dot)com> writes:
>> On Nov 4, 2021, at 12:47, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>> 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 gets 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-11-04 21:07:14 | Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing |
| Previous Message | Christophe Pettus | 2021-11-04 19:56:06 | Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing |