John Watkins wrote:
On the other hand, if you have the membership list and the config file
from your list, I am fairly sure your new provider can help you get it
back into operation.
I do have both. Is that all that's needed? Can I just substitute the old
config file for the new one? Or must the new provider do something more.
They frankly say they make majordomo available but don't support it,
suggesting greatcircle instead.
The following information is available in the list-owner-info document that
comes with the majordomo files from greatcircle, so you can ignore the
misleading "undocumented" statement below. ;)
The "undocumented" commands for use by list owners are:
* approve passwd {subscribe|unsubscribe} list [address]
This is so that you can approve subscription or unsubscription actions that need approval by the list owner. Note that this
is just a standard "subscribe" or "unsubscribe" command prefixed with "approve password" (where you substitute the password for your
list, which is listed above, for "password").
* approve passwd who list
This allows you to get the list of addresses for your anonymous list. Without the password, even the list owner can not see
who is on the list.
* passwd list old_passwd new_passwd
This is so you can change the password for your list, if you desire.
* newintro list password
This is so that you can replace the information file that people get when they do "intro list" or "subscribe list". It reads
everything after the "newintro" command to end-of-message or the word "EOF" on a line by itself as the new intro for the list.
* newinfo list password
This replaces the information file that people get when they do "info list". (This file is also sent by "subscribe list" if
the intro file doesn't exist.) This reads everything after the "newinfo" command to end-of-message or the word "EOF" on a line by
itself as the new info for the list.
* config list password
Retrieves a self-documenting configuration file for the list list. The password can be the password contained in the file
list.passwd or the admin_password in the configuration file.
* newconfig list password
Validates and installs a new configuration file. It reads everything after the "newconfig" command to end-of-message or the
word "EOF" on a line by itself as the new info for the list. The config file is expected to be a complete config file as returned by
"config". Incremental changing of the config file is not yet supported. As soon as the config file is validated and installed its
settings are available for use. This is useful to remember if you have multiple commands in your mail message since they will be
subject to the settings of the new config file. If there is an error in the config file (incorrect value...), the config file will
not be accepted and the error message identifying the problem line(s) will be returned to the sender. Note that only the error
messages are returned to the sender not the entire config file, so it would be a good idea to keep a copy of your outgoing email
message.
* writeconfig list password
Write a new config file in standard form. Writeconfig forces a rewrite of the config file with all default values in place
(or current values if the config file already exists). It is useful to use after an upgrade of Majordomo since it will add the new
keywords for people to change. It also updates the documentation in the file if that has changed.
* mkdigest digest list name password
mkdigest digest list name digest outgoing alias password
Generate a digest immediately without waiting to reach the maxlength given in the config file. The first form will cause the
digest to be sent to an alias found by appending "-outgoing" to the digest list name. Because this can be a security concern, the
second form allows specification of the name of the alias that the outgoing digest will be sent to.
References:
|
|
