On 9/30/22 12:41, Andy Smith wrote:
This just happened again. As a refresher, the issue I'm seeing is that Mailman registers a bounce against addresses that aren't subscribed, including addresses for the list itself and for the -leave address that is in some footer text.
Here's the bounce.log:
Sep 30 17:12:25 2022 (8428) Member [elided1]@[elided1].force9.co.uk on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users@mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email mailto:[elided2]@gmail.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided2]@gmail.com on list users.mailman.bitfolk.com, bounce score = 1. Sep 30 17:12:25 2022 (8428) Bounce message for a non subscriber: Email users-leave@mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Sep 30 17:12:25 2022 (8428) Member [elided3]@[elided3].org.uk on list users.mailman.bitfolk.com, bounce score = 1.
I have elided parts of the email addresses of real subscribers.
Attached is the actual non-delivery report from the MTA that triggered this. In it I have done my best to elide the names and addresses of real people, but nothing else. They match the same elisions from the bounce log.
What is your version of flufl.bounce?
I made one change to your attached DSN. In the message/selivery-status part, I changed
Final-Recipient: rfc822;[elided1]@[elided1].force9.co.uk
to
Final-Recipient: rfc822;elided1@elided1.force9.co.uk
and processed the message with flufl.bounce.scan_message() which returned the single address elided1@elided1.force9.co.uk.
I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan