Re: uncaught bounce messages
Putting back on the list.
On 10/23/21 1:37 PM, David Bremner wrote:
Mark Sapiro <mark@msapiro.net> writes:
If you send me the complete bounce message off list, I can see if it should be added to the recognition at https://gitlab.com/warsaw/flufl.bounce/.
Please find attached.
Thank you. I tested that DSN with current flufl.bounce and it is recognized as a temp failure for the reported address and that in turn should just be ignored by Mailman's bounce runner and not reported as unrecognized.
What version of Mailman core is this and what version of flufl.bounce?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro <mark@msapiro.net> writes:
Thank you. I tested that DSN with current flufl.bounce and it is recognized as a temp failure for the reported address and that in turn should just be ignored by Mailman's bounce runner and not reported as unrecognized.
What version of Mailman core is this and what version of flufl.bounce?
Sorry, meant to reply on list with the rest of the details, but got distracted by making dinner. So it sounds like the problem is old versions of flufl.bounce.
This particular machine is running debian oldstable, so things are a bit out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look into upgrading at least flufl.bounce.
thanks for your help,
David
David Bremner <david@tethera.net> writes:
Mark Sapiro <mark@msapiro.net> writes:
Thank you. I tested that DSN with current flufl.bounce and it is recognized as a temp failure for the reported address and that in turn should just be ignored by Mailman's bounce runner and not reported as unrecognized.
What version of Mailman core is this and what version of flufl.bounce?
Sorry, meant to reply on list with the rest of the details, but got distracted by making dinner. So it sounds like the problem is old versions of flufl.bounce.
This particular machine is running debian oldstable, so things are a bit out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look into upgrading at least flufl.bounce.
Oh. It's actually 3.0.1. Still not new enough, but 3 years newer.
d
On 10/23/21 4:23 PM, David Bremner wrote:
This particular machine is running debian oldstable, so things are a bit out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look into upgrading at least flufl.bounce.
Oh. It's actually 3.0.1. Still not new enough, but 3 years newer.
I don't think it's a flufl.bounce issue. I think it's a Mailman 3.2.1 issue - https://gitlab.com/mailman/mailman/-/issues/622 which is fixed in Mailman 3.3.0
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro <mark@msapiro.net> writes:
On 10/23/21 4:23 PM, David Bremner wrote:
This particular machine is running debian oldstable, so things are a bit out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look into upgrading at least flufl.bounce.
Oh. It's actually 3.0.1. Still not new enough, but 3 years newer.
I don't think it's a flufl.bounce issue. I think it's a Mailman 3.2.1 issue - https://gitlab.com/mailman/mailman/-/issues/622 which is fixed in Mailman 3.3.0
Oh great, I just upgraded to Mailman 3.3.0, so I'll see what happens.
I did notice a bunch (10 or 20?) of subscribers being disabled for being over the bounce threshhold right after the upgrade, I wonder if that is related.
d
On 10/23/21 5:29 PM, David Bremner wrote:
Oh great, I just upgraded to Mailman 3.3.0, so I'll see what happens.
I did notice a bunch (10 or 20?) of subscribers being disabled for being over the bounce threshhold right after the upgrade, I wonder if that is related.
See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U...
There is an example mailman shell session at
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
that will reenable delivery for members disabled by bounce if you think
the disables were spurious.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro <mark@msapiro.net> writes:
See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U...
There is an example
mailman shellsession at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... that will reenable delivery for members disabled by bounce if you think the disables were spurious.
Thanks very much for the recipe. I had been trying (and failing) to do something similar using the mailmanclient API / rest client. Does anyone happen to have a working example of updating user preferences via mailmanclient? I did call save(), after setting preferences['delivery_status']='enabled', but that seemed to not be enough. If no-one has a working example I can try to reconstruct a more precise reproducer.
d
P.S. I wonder if it would be worth collecting some of these recipes on the list as examples in the documentation?
On Sat, Oct 23, 2021, at 9:05 PM, Mark Sapiro wrote:
On 10/23/21 5:29 PM, David Bremner wrote:
Oh great, I just upgraded to Mailman 3.3.0, so I'll see what happens.
I did notice a bunch (10 or 20?) of subscribers being disabled for being over the bounce threshhold right after the upgrade, I wonder if that is related.
See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U...
There is an example
mailman shellsession at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... that will reenable delivery for members disabled by bounce if you think the disables were spurious.
I have just upgraded to 3.3.4 from 3.3.2 (via docker).
Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature).
Is it just catching up on old bounces?
Thanks, Seth
Oct 26 14:30:03 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 1. Oct 26 14:30:10 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:30:56 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 2. Oct 26 14:30:59 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:31:10 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:32:31 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 1. Oct 26 14:32:39 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 2. Oct 26 14:32:46 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:33:04 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 3. Oct 26 14:33:49 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 4. Oct 26 14:33:52 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:33:55 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:33:58 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:34:01 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:34:35 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 5. Oct 26 14:34:35 2021 (37) Disabling delivery for max@example.com on list listname.lists.example.net by bounce Oct 26 14:34:35 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score 5 >= threshold 5, disabling delivery. Oct 26 14:34:39 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:35:06 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:35:09 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:35:18 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:35:20 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:36:01 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:19 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:27 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:33 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:36 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:40 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:42 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:44 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:47 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:49 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:51 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:37:58 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:38:01 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:38:14 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:38:15 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:38:18 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:40:38 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 1. Oct 26 14:40:51 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 2. Oct 26 14:41:02 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 3. Oct 26 14:41:10 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 14:41:40 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 4. Oct 26 14:41:43 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 5. Oct 26 14:41:43 2021 (37) Disabling delivery for max@example.com on list listname.lists.example.net by bounce Oct 26 14:41:43 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score 5 >= threshold 5, disabling delivery. Oct 26 14:41:48 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:41:52 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:41:54 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:41:57 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:41:59 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:12 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:17 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:24 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:45 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:47 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:50 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:53 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:42:55 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:43:05 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 6. Oct 26 14:43:05 2021 (37) Disabling delivery for max@example.com on list listname.lists.example.net by bounce Oct 26 14:43:05 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score 6 >= threshold 5, disabling delivery. Oct 26 14:43:17 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:43:19 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:43:22 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:43:25 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:43:31 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:44:57 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:45:41 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:45:44 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:45:47 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:45:52 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:45:58 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:45:59 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:04 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:09 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:15 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:19 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:23 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:27 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:33 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:36 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:39 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:42 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:44 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:48 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:49 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:53 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:56 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:46:57 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:00 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:01 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:05 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:08 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:10 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:13 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:15 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:18 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:22 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:24 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:27 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:28 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:31 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:33 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:35 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:38 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:40 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:42 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:45 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:46 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:49 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:51 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:54 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:47:57 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:03 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:04 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:06 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:08 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:14 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:16 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:19 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:24 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:27 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:29 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:32 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:48:34 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:49:07 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:49:33 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:16 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:18 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:20 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:23 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:27 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:30 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:36 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:41 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:47 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:50:49 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 14:51:00 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 15:04:36 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 1. Oct 26 15:04:39 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 15:04:41 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 15:04:43 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 15:04:54 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 2. Oct 26 15:04:57 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 15:05:59 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 15:06:02 2021 (37) Member max@example.com already scored a bounce on list listname.lists.example.net today. Oct 26 15:10:00 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 3. Oct 26 15:11:51 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 4. Oct 26 15:12:30 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score = 5. Oct 26 15:12:30 2021 (37) Disabling delivery for max@example.com on list listname.lists.example.net by bounce Oct 26 15:12:30 2021 (37) Member max@example.com on list listname.lists.example.net, bounce score 5 >= threshold 5, disabling delivery. Oct 26 15:12:45 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 15:12:52 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net. Oct 26 15:14:36 2021 (37) Residual bounce received for member max@example.com on list listname.lists.example.net.
On 10/26/21 8:18 AM, Seth Seeger wrote:
I have just upgraded to 3.3.4 from 3.3.2 (via docker).
Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature).
Is it just catching up on old bounces?
There is no significant change in bounce processing from 3.3.2 to 3.3.4
If you really upgraded from 3.3.2, I don't know what would be responsible. On the other hand, it looks like you may in fact have upgraded from Mailman < 3.3.1 in which case, those are old, previously unprocessed bounces, and your log certainly looks like that.
If you think some or all users shouldn't have had delivery disabled, you can run the mailman shell seccion in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... to re-enable them and let current bounce processing handle the truly undeliverable ones.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
David Bremner -
Mark Sapiro -
Seth Seeger