AAPT Home > Support Information > Mailing Lists > Admin Commands
In addition to the User Commands, list owners can use the following commands to administer their list. When you see words in italics, replace them with the correct value. For example, "approve asni48 widgets fred@example.com" will subscribe fred@example.com to the widgets@lists.connect.com.au mailing list, if the admin password is asni48.
This is so that you can approve subscription to the list, if list owner approval if required. Note that this is just a standard subscribe or unsubscribe command prefixed with approve password (where you substitute the password for your list for password).
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 for password).
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.
This is so you can change the password for your list, if you desire.
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.
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.
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.
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.
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.
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.
| Copyright © AAPT Limited |
|