For Advanced Users: Configuring Your Mailing List

For those that would like to configure the mailing list, the following commands can be sent to majordomo@sfsu.edu.

config <list> <password>
e.g. config mailing-list password

newconfig <list> <password>
e.g. newconfig mailing-list password

Majordomo will send you a mostly self-documenting configuration file. A portion of a configuration file is shown below.

>>>> config mailing-list password|
# The configuration file for a majordomo mailing list.
# Comments start with the first # on a line, and continue to the end
# of the line. There is no way to escape the # character. The file
# uses either a key = value for simple (i.e. a single) values, or uses
.
.(skipping some)
.
# admin_passwd [word] (test.admin) <majordomo>
# The password for handling administrative tasks on the list.
admin_passwd = password
# administrivia [bool] (yes) <resend>
# Look for administrative requests (e.g. subscribe/unsubscribe)
# and forward them to the list maintainer instead of the list.
administrivia = yes
.
.(skipping rest)
.

This is the file where the password can be changed, moderator can be added or changed, as well as other list policies and access rules. After changes are made to the config file you need to send it to Majordomo so the file can be updated. The file sent to Majordomo should be the complete file as returned by the "config" command, not just a portion of it. The easiest way to make changes is to edit the config file message that Majordomo sends when you issue the ‘config’ command. Either redirect the message (if using Eudora) or forward the message (if using pine).  A sample message body is below.

newconfig mailing-list password
>>>> config mailing-list password
# The configuration file for a majordomo mailing list.
# Comments start with the first # on a line, and continue to the end
# of the line. There is no way to escape the # character. The file
# uses either a key = value for simple (i.e. a single) values, or
(rest of config is snipped)

NOTE: If you are changing the password, use the OLD password with the ‘newconfig’ command. The new password will take effect after the new configuration file is written.

Last modified May 26, 1998 by Computing Services Help Desk, San Francisco State University

---

Site Home | What We Do | Help Desk | Account Services | Software | Hardware | Network
Telephone Services | Training | Computer Labs | Web Publishing | Policies | Sitemap | Contact Us

---