MIME-Version: 1.0
References: <c743009d-821b-4ddf-860d-bc6b15b5bc30@cmatte.me>
In-Reply-To: <c743009d-821b-4ddf-860d-bc6b15b5bc30@cmatte.me>
From: Magnus Hagander <magnus@hagander.net>
Date: Wed, 27 Aug 2025 16:16:14 +0200
Message-ID: 
 <CABUevEwOyXbB+58YijsH3SvDuWFkZoTe0D_+jS3f3nuP5nHWhA@mail.gmail.com>
Subject: Re: Slight issue in bounce management in PGLister
To: =?UTF-8?Q?C=C3=A9lestin_Matte?= <celestin.matte@cmatte.me>
Cc: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000347563063d596f31"
Archived-At: 
 <https://www.postgresql.org/message-id/CABUevEwOyXbB%2B58YijsH3SvDuWFkZoTe0D_%2BjS3f3nuP5nHWhA%40mail.gmail.com>
Precedence: bulk

--000000000000347563063d596f31
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, May 2, 2025 at 7:15=E2=80=AFPM C=C3=A9lestin Matte <celestin.matte@=
cmatte.me>
wrote:

> Hello,
>
> I noticed a problem with bounces in PGLister: when an address is newly
> added to a list, it is supposed that all former emails were properly
> delivered. All prior emails are marked as "Delivered to remote
> server", which is not the case as the address was not subscribed yet
> (they should not appear at all).
>
> As a result, a bouncing address will not immediately be flagged as a
> bounce.
>
> A way to fix that could be to add an "added_date" field to e.g.
> list_subscriberaddress.
>
> This may be intentional behaviour as fixing it requires adding a field,
> for what is pretty much a corner case (one can expect a newly added
> address is not immediately bouncing).
> Do you think a fix is worth implementing?
>

Here's a very late comment on this.

I'd consider it a corner case, so I'm not sure it would warrant this in
itself. But it's not intentional behavior that I'm aware of.

That said, tracking when a subscription happens could also be useful for
other cases I think it might be worthwhile doing.


Side-question regarding bounces: I did not find any process in the
> codebase that automatically unsubscribes bouncing addresses
> (bouncehandler.py leaves this as "run separtely").
> Is this expected to always done manually?
>
>
Correct, there is no code in place for that.They show up on the admin
dashboard for manual handling.

//Magnus

--000000000000347563063d596f31
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, May 2, 2025 at 7:15=E2=80=AFPM C=
=C3=A9lestin Matte &lt;<a href=3D"mailto:celestin.matte@cmatte.me">celestin=
.matte@cmatte.me</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_=
container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I noticed a problem with bounces in PGLister: when an address is newly<br>
added to a list, it is supposed that all former emails were properly<br>
delivered. All prior emails are marked as &quot;Delivered to remote<br>
server&quot;, which is not the case as the address was not subscribed yet<b=
r>
(they should not appear at all).<br>
<br>
As a result, a bouncing address will not immediately be flagged as a<br>
bounce.<br>
<br>
A way to fix that could be to add an &quot;added_date&quot; field to e.g.<b=
r>
list_subscriberaddress.<br>
<br>
This may be intentional behaviour as fixing it requires adding a field,<br>
for what is pretty much a corner case (one can expect a newly added<br>
address is not immediately bouncing).<br>
Do you think a fix is worth implementing?<br></blockquote><div><br></div><d=
iv>Here&#39;s a very late comment on this.</div><div><br></div><div>I&#39;d=
 consider it a corner case, so I&#39;m not sure it would warrant this in it=
self. But it&#39;s not intentional behavior that I&#39;m aware of.</div><di=
v><br></div><div>That said, tracking when a subscription happens could also=
 be useful for other cases I think it might be worthwhile doing.</div><div>=
<br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Side-question regarding bounces: I did not find any process in the<br>
codebase that automatically unsubscribes bouncing addresses<br>
(bouncehandler.py leaves this as &quot;run separtely&quot;).<br>
Is this expected to always done manually?<br><br></blockquote><div><br></di=
v><div>Correct, there is no code in place for that.They show up on the admi=
n dashboard for manual handling.</div><div><br></div><div>//Magnus</div><di=
v>=C2=A0</div></div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"=
ltr"></div></div></div>

--000000000000347563063d596f31--