Re: Slight issue in bounce management in PGLister

On Fri, May 2, 2025 at 7:15 PM Célestin Matte <celestin(dot)matte(at)cmatte(dot)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