[Mailman-Users] Cron job to reset member bounce value

[Ethan Rudnitsky]

Carl, my apologies as I see what you are saying now. The server is indeed
retrying instead of giving up right away, so they do receive the messages
eventually but the retries are being counted as a bounce.

Mark, when I run your get_bounce_info script I do get an output of the
current score for each member in each list, but when I manually run
"./withlist -a -r reset_bounce --" it returns "Importing reset_bounce..."
[newline] "Running reset_bounce.reset_bounce()... and it then lists all of
the lists on each line as it goes through them and appends each with an
(unlocked) and then says Finalizing. However, if I run the get_bounce_info
again, nothing is reset to 0 bounces, it lists the same thing as before. So
I guess I need clarification, will this only reset bounce counts for
members who are already/currently locked, or is it supposed to reset the
count back to 0 even if they are unlocked and below the threshold?

Thank you, sir.

On Tue, Dec 17, 2019 at 11:34 AM Carl Zwanzig <cpz at tuunq.com> wrote:

> On 12/17/2019 10:24 AM, Ethan Rudnitsky wrote:
> >   the issue with the server/MTA bring offline is a known and
> > unavoidable issue because of lack of satellite availability overhead for
> > most of the day unfortunately.
>
> That is an entirely avoidable issue. When a destination MTA is
> offline/busy
> (which happens all the time and is accounted-for in SMTP), the sending MTA
> usually queues the messages and retries in 15/30/120 minutes, and usually
> keeps that up for at least 24 hours. If the sending MTA is giving up
> immediately and returning a failure, IMHO it's misconfigured (knowing the
> exact error code returned is important, here).
>
> That said, the operator(s) of that server may not be interested in fixing
> the problem.
>
> Do the satellite-served list members receive every message eventually or
> are
> they content to only receive ones sent during their connectivity window?
>   If the -do- get all the messages eventually then they are being retried
> and the temporary failure is being counted as a bounce.
>
> Later,
>
> z!
>