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

From Célestin Matte
Subject Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing
Date
Msg-id 53316703-db69-7067-c82e-47a598711595@cmatte.me
Whole thread Raw
In response to Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-www
> I don't think this should be the responsibility of pglister. As you say, "most MTAs do add this field" -- and the
solutionis 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
actuallybreak 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



pgsql-www by date:

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