Mailman resources? Need to deal with a Mailman DoS

[David Wolfskill]

Sorry for the vague Subject....  I'm having a challenge with a Mailman
installation where -- judging from the available evidence -- it looks as
if someone who doesn't have enough chores to do is submitting forged
bounce-o-grams.

Mailman is apparently processing the forged bounce-o-grams as if they
were legitimate, causing certain targeted individuals to become
unsubscribed to certain mailing lists.

Ideally, I'd like to make Mailman clever enough to ignore forged
bounce-o-grams, but I suspect that given the variety of types of
bounce-o-grams, that could be challenging -- especially since I don't
know Python, don't have any books on it, and don't have a budget for
buying books.  Further, I have little clue as to the "flow" of things in
Mailman.

As a backup for making Mailman cleverer, I thought that it might be
useful to provide a file that could contain email addresses (one/line,
to make parsing easier); if an address is found in the file, bounces for
the address should be ignored.

Unfortunately, I need to be fairly careful about any changes I make, as
the installation in question is fairly high volume; while it is not a
money-making venture, it is fairly high visibility.

I solicit suggestions for resources to help me figure out how to cope.

Thanks,
david
-- 
David H. Wolfskill				david at catwhisker.org
There is a place in software engineering for an appreciation of history.

See http://www.catwhisker.org/~david/publickey.gpg for public key.