I am currently running a number of lists including digest lists and a
bounces list with Majordomo 1.94.4 and Perl5 on a Debian 2.1 system.
Unfortunately I wasn't involved in the installation so I'm not sure if
files are where they are supposed to be...my involvement only started at
the configuring the lists stage. However since then I have been frustrated
by the fact that neither the bounce or the approve scripts do all that
according to the documentation they are supposed to do....and that is to
automate the approval and bounce processes.
With the 'Approved: password' header, Majordomo will send a message to the
list...but not before all the 'taboos' that caused it to bounce in the
first place have been edited out. It will NOT use the 'Approved:' to
override what is in the config file - even though from my understanding of
the documentation this is what it's supposed to do. Is my understanding
correct?
I also can't get Majordomo to recognise the 'bounce' command at all. I've
changed permissions, ownership and its location but still it just tells me
'command not found'. Yet bounce-remind works, although automated
bounce-expiry doesn't and I have to manually remove an address from a list
and add it to the bounces list. But then although I put the list and date
information in the bounces subscription command (as stipulated in the docs)
neither show up in the bounce-remind message that gets sent out...all there
is is a list of addresses plus the screed. This makes it impossible for
those on the bounces list (and me) to identify which list it was I unsubbed
them from.
As far as I know nothing was changed dramatically during the installation
process as in configuring the lists I encountered no problems.
So I'd really appreciate some help with this. For starters if someone
could tell me where these files are supposed to be located, what
permissions and ownership they should have and anything else that could be
pertinent at least I could stop pulling my hair out over this. :-)
Carolyn
Follow-Ups:
References:
|
|
