any way to eliminate 'mailman-owner'

[Nneul]

I am trying to have a setup where users of the ISP can
have their own lists. Works great, but unfortunately,
there are lot of idiot list-members out there who
insist on replying to mailman-owner messages about
passwords and stuff.

What I'd like is some way of saying:

Split the password reminder/other messages by list and
have them come from listname-owner instead of
mailman-owner.

I presume that there is no reasonable way to do this
currently, but I would consider it a very useful
enhancement.

The key is - other that "the server has gone amok", I
don't want to have to be dealing with all of these list
member questions, but I don't really want them ignored
either.

In the meantime, I'm probably going to set up
mailman-owner to bounce with a message as a short term
way of dealing with it.

Thoughts?

[http://sourceforge.net/tracker/index.php?func=detail&aid=413415&group_id=103&atid=100103]

[Barry Warsaw (barry)]

In MM2.1 "<email address hidden>" is a real list, so you can always
set up replybot messages for mailman-owner.

As for password reminders, it wouldn't be a difficult thing
for a Python programmer to rewrite cron/mailpasswds to
implement some other site-specific policy.