Message-ID: <53316703-db69-7067-c82e-47a598711595@cmatte.me>
Date: Thu, 4 Nov 2021 16:34:35 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.1
Subject: Re: [PATCH] pgarchives: parser: handle messages in which Message-ID
 is missing
Content-Language: en-US
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-www@lists.postgresql.org
References: <c12954dd-c19c-f809-f92c-116469c9543f@cmatte.me>
 <CABUevExbE==POwr9LOESmJ-J+PvkCQ=-F6wH=1SegFUAzxfsCA@mail.gmail.com>
From: =?UTF-8?Q?C=c3=a9lestin_Matte?= <celestin.matte@cmatte.me>
In-Reply-To: 
 <CABUevExbE==POwr9LOESmJ-J+PvkCQ=-F6wH=1SegFUAzxfsCA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/53316703-db69-7067-c82e-47a598711595%40cmatte.me>
Precedence: bulk

> 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