Re: Making pglister work with exim 4.96+ - Mailing list pgsql-www

From Magnus Hagander
Subject Re: Making pglister work with exim 4.96+
Date
Msg-id CABUevEwq9fe_Vkhy_T2tm+cG8O6H2vj4sHAq-5Wa5Sxrf1mygQ@mail.gmail.com
Whole thread Raw
In response to Re: Making pglister work with exim 4.96+  (Célestin Matte <celestin.matte@cmatte.me>)
List pgsql-www
Hi!

Sorry about the late response to this one!

My first response was also going to be "but, we already implemented this". And when I went to double check, I realized I forgot to push :/

So now a solution for this is actually pushed :) The version pushed is imo cleaner, and in particular maintains backwards compatibility. To use it, set your inject command to something like:

/usr/local/pglister/bin/inject.py -s env:SENDER -d env:RECIPIENT -m env:HEADER_MESSAGE_ID

//Magnus

On Fri, May 2, 2025 at 4:59 PM Célestin Matte <celestin.matte@cmatte.me> wrote:
Formerly sent patch contained an error in the case of bounce emails.
Attached: corrected patch

(This patch following recommendations from prior discussion has not received a review yet)

On 19/06/2024 13:10, Célestin Matte wrote:
> OK I understand better now how environment variable is a better working solution. I completely removed argparse, since no more parameters are used.
>
> Patch to modify inject.py accordingly attached.
>
> On the exim side, final solution involves:
> - modifying pglister transport to add
> environment = HEADER_MESSAGE_ID=$header_message-id:
> - modifying pgarchives transport to use $local_part_data instead of $local_part


pgsql-www by date:

Previous
From: Jeff Davis
Date:
Subject: Re: git repo "https://" working but "git://" is not
Next
From: Devrim Gündüz
Date:
Subject: Patch for yum.js