Thank you for the tip. In the end I changed mailman/runners/bounce.py instead by moving the maybe_forward line so that it is always run. Smaller change (just removing one indention level) and preserves the handling. Might break something else, but I do not think so. diff --git a/src/mailman/runners/bounce.py b/src/mailman/runners/bounce.py index 57b259f..e772765 100644 --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -86,6 +86,6 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False Cheers // David On Sun, Nov 5, 2017 at 10:39 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 11/05/2017 01:29 PM, Mark Sapiro wrote:
The bottom line is we aren't doing anything with bounces other than storing them. We need to fix that, and we will (It's targeted for 3.2). If you could help with code, that would be great.
As an interim work around, if you wanted to send ALL bounces to the list owner instead of what little we currently do, at about line 65 in mailman/runners/rest.py, you'll see
SUBADDRESS_NAMES = dict( admin='bounces', bounces='bounces', confirm='confirm', ...
If you change the
bounces='bounces',
line to
bounces='owner',
that will cause all bounces to be just sent to the list owner(s).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/