I have what looks to me like a bug report for 'approve'.
We've run into the case where majordomo's "approve" command fails with
a complaint of:
no password for list <LISTNAMEHERE>; skipping "subscribe <LISTNAMEHERE> <ADDRESSHERE>
" at approve line 148, <STDIN> line 20.
[...note the \n before the closing quote, which got me to looking...]
I've figured out what's going on there and how to deal with it.
If you look at the Reply-To: header on a message from majordomo, it
contains the address that should be in the right-hand column for all
entries in your .majordomo file for the list that message is related to.
If you have anything else that resolves to the majordomo program on
the other site (an alias, etc.) you'll get this error.
My question is "why does approve care" ?
Shouldn't it just be grabbing the listname from the message,
the password from the .majordomo file, and mailing back to whatever
Reply-To: address the mail started from ?
Now, I can see how some might consider it to be a feature that would
let you perhaps (I dunno, I didn't look THAT closely at the code)
be the list owner for two lists with the same name that were resident
on two different systems, but that seems a little far-fetched.
Is it a bug or just a documentation tidbit that's needs clarifying