|Navigate > Green Parties > about www.greens.org > The Green Internet Society > Majordomo command set|
Your mailing list is managed by an automated mailing list management program called Majordomo. Majordomo should free you from dealing with most of the administrivia usually associated with running mailing lists (adding users, dropping users, etc.).
To submit something to your list, you (or anybody else) should simply mail it to the list posting address.
To be added to your list, a user simply sends a message to majordomo. There are two ways to do it:
Majordomo understands several commands, and is not limited to a single command per message (it will process commands until reaching end-of-message or the command ``end''). The command ``help'' will tell you about all the other commands.
Actually, it won't tell you about _all_ the other commands that Majordomo understands. There are several commands there for use by list owners such as yourself, which are not advertised to the public. All of these commands are password-protected on a list-by-list basis, but anyone with a valid list/password combination can invoke these commands. This is not exactly high-tech security, but it's more intended to keep annoyance to a minimum than to be foolproof.
The ``documented'' commands which Majordomo understands and which are for everyone to use are:
help'' as the message text to email@example.com).
The ``undocumented'' commands for use by list owners are:
subscribe'' or ``
unsubscribe'' command prefixed with ``
approvepassword '' (where you substitute the password for your list, for ``password'').
passwdList-Name Old-Password New-Password
subscribeList-Name''. 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.
infoList-Name''. (This file is also sent by ``
subscribeList-Name'' 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.
admin_passwordin the configuration file.
newconfig'' command to end-of-message or the word ``
EOF'' on a line by itself as the new info for the list. The
configfile is expected to be a complete
configfile as returned by ``
config''. Incremental changing of the
configfile is not yet supported. As soon as the
configfile 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
configfile. If there is an error in the
configfile (incorrect value...), the
configfile 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
configfile, so it would be a good idea to keep a copy of your outgoing email message.
configfile in standard form.
writeconfigforces a rewrite of the
configfile with all default values in place (or current values if the
configfile 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
max_lengthgiven in the
configfile. 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.