Additional comments:
This is false (from admin_commands):
Every command will have at least one required argument, and may have one or
more optional requirements as well. The first required argument is usually
the listname; therefore, most commands will be submitted to the parser in
the format:
show, accept, reject, lists, register, unregister, password, etc. work just
fine without any arguments.
This is site policy:
Commands may be sent either to the majordomo server's address, or to the
list's -request address (i.e., scooters-request). For messages sent to the
-request address, the list name can be omitted from the commands. The list
cannot be omitted from commands sent to the majordomo address.
That paragraph explains what happens if the variable 'request_answer'
variable is set to 'majordomo' (which is the default). If it's set to
'owner' then mail sent to -request is forwarded to the list owners, and if
it is 'response' then a canned file will be sent.
Admittedly it makes it difficult to write help files when things can change
like this, but the debate on list-managers proved that this needs to be
configurable.
I'm making some changes to these files, mainly to clean up some of these
issues. Everything will be in CVS in an hour or so.
- J<
Follow-Ups:
References:
|
|
