Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing

From: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: 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 15:34:35
Message-ID: 53316703-db69-7067-c82e-47a598711595@cmatte.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

> I don't think this should be the responsibility of pglister. As you say, "most MTAs do add this field" -- and the solution is to configure the MTA to do this. We already rely on the MTA to get a lot of other important things right.

But then these messages will get delivered by pglister but pgarchives will fail to archive them, although they do not actually break requirements. Shouldn't we follow the RFC here?

> It may be something that should get documented somewhere as a requirement. 

I'll write a small readme for pgarchives

--
Célestin Matte

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Célestin Matte 2021-11-04 15:46:29 Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing
Previous Message Célestin Matte 2021-11-04 15:22:06 Re: [PATCH] pglister: Add possibility to override settings.py in settings_local.py