[Mailman-Users] Bounce Handling Question

Kirke Johnson kjohnson at pcc.edu
Mon Sep 28 17:56:41 CEST 2009

I have often wondered about the inefficiencies of having every list 
arrive at member removal via independent bounce processing. I think 
there is value in removal of a bounced member from ALL lists.

This seems particularly useful where we have adapted the script from 
the Pasus mailing lists site to have an all-campus list where 
membership is automatic for everyone who is on any of our seven 
campuses. We are on version 2.1.9, so sibling lists are not a 
available feature, and I wanted to reduce duplicate mailings. I am 
still unsure whether Mailman will eventually get unhappy with members 
popping up the next day after they have been added back from a campus 
list that has not yet completed bounce processing for that member.

The same concern applies for captive lists where the membership is 
generated nightly from employees' roles in our administrative 
software database. In that case there is no possibility of a 
subsidiary list removing a member through bounce processing, and the 
roles may persist for a long time after an account is abandoned and 
goes over quota. Sibling lists naturally would not be applicable in 
that situation.

As a side question, is there some place in Mailman that keeps track 
of list members that have been removed by bounce processing in case 
they reappear immediately and still bounce?

At 10:54 AM 9/26/2009, Mark Sapiro wrote:
>(--  snip   --)

>So the issue is, is it worth enhancing bounce processing so that when a
>bounce is returned for a non-member of list X, we look at list X's
>regular_include_lists and score the bounce for any of those lists of
>which the bouncing address is a member?
>Thoughts anyone?
>It seems that in the situation above where there are (I think) two
>active lists that get their own posts, there would be enough regular
>bounces so that ignoring the additional bounces from the all list
>wouldn't be a problem, but there may be other situations where a list
>is used as an alternative umbrella where almost all the posts would be
>to the 'umbrella' and this would be a problem.
>I added a note about this to the FAQ at <http://wiki.list.org/x/TIA9>.
>Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
>San Francisco Bay Area, California    better use your sense - B. Dylan
>Mailman-Users mailing list
>Mailman-Users at python.org
>Mailman FAQ: http://wiki.list.org/x/AgA3
>Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
>Security Policy: http://wiki.list.org/x/QIA9

Kirke Johnson                               Internet: kjohnson at pcc.edu
Email Administrator, TSS , Sylvania Campus      http://www.pcc.edu/
Portland Community College, Portland, OR, USA     (503) 977-4368 

More information about the Mailman-Users mailing list