On 2/2/23 04:54, Danil Smirnov wrote:
Isn't this a bug?
Eye of the beholder. I will argue it's a doc bug.
We are now showing users' bounce scores on the Members page and this would be misleading.
If you mean the member's own page, yes, confusion is a problem. If you mean it's the Members page that the admins see, documentation and education is the answer, IMO.
Is it difficult from internals perspective to have the bounce score reset immediately?
Mark Sapiro writes:
Yes, it is not difficult, but it's a lot of processing. It would require something like a task runner task to periodically look at each row in the member table and if the bounce score is > 0, find the associated list's bounce_info_stale_after and if last_bounce_received + bounce_info_stale_after < now, reset the score.
Aside: In programming, all problems are solved by another level of indirection. In databases, all problems are solved by another index. :-) You'd still need a runner, but it would be a simple "update these rows to zero", I guess.
About the education and documentation for subscribers: I would argue that we can document the bounce score as a "recent highwater mark", since delivery isn't disabled yet. That's useful information for those with ears to hear it. That is, if you see "0" 95% of the time, occasionally "1", and today it's "2", maybe you wanna have a talk with your postmaster? On the other hand, if we reset immediately, I bet most users will rarely see anything greater than 0 because most visits are triggered by list posting,
Admins would be similar, except that they might see correlations with remote domains, or if there was a wave across domains it might be a symptom of getting registered on an RBL or two.