public inbox for [email protected]
help / color / mirror / Atom feedSlight issue in bounce management in PGLister
2+ messages / 2 participants
[nested] [flat]
* Slight issue in bounce management in PGLister
@ 2025-05-02 17:15 Célestin Matte <[email protected]>
2025-08-27 14:16 ` Re: Slight issue in bounce management in PGLister Magnus Hagander <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Célestin Matte @ 2025-05-02 17:15 UTC (permalink / raw)
To: PostgreSQL WWW <[email protected]>
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?
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?
Regards,
--
Célestin Matte
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Slight issue in bounce management in PGLister
2025-05-02 17:15 Slight issue in bounce management in PGLister Célestin Matte <[email protected]>
@ 2025-08-27 14:16 ` Magnus Hagander <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Magnus Hagander @ 2025-08-27 14:16 UTC (permalink / raw)
To: Célestin Matte <[email protected]>; +Cc: PostgreSQL WWW <[email protected]>
On Fri, May 2, 2025 at 7:15 PM Célestin Matte <[email protected]>
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-08-27 14:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-05-02 17:15 Slight issue in bounce management in PGLister Célestin Matte <[email protected]>
2025-08-27 14:16 ` Magnus Hagander <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox