Anything that appears in capitals and italics should be replaced with the appropriate value. For example, SITE_PASSWORD should be replaced with CSF's site password for majordomo lists.
All majordomo commands should be sent to email@example.com. Commands in the Subject: line will be ignored. The first command in the message should tell majordomo what password to use for the commands that follow, for example,
default password YOUR_LIST_PASSWORD
createlist LIST OWNER_EMAIL_ADDRESSAfterward, one of the site managers must configure sendmail so that it recognizes the addresses of the new list.
configset LIST master_password = PASSWORD
configshow LIST configshow-nocomments LIST
configshow LIST subscribe_policy,access_rules
The configshow command presents the options in the form of majordomo commands. This makes it easy to edit the results of configshow, then send your changes to majordomo to have them take effect.
Every action that is delayed pending someone's approval has a token associated with it. To see which tokens are awaiting approval, use the command
showtokens LISTTokens expire if no action has been taken, usually in seven days. One reminder is sent to the appropriate person after four days have elapsed. Both of these time periods can be changed by the list owner.
configset LIST token_remind = 4 configset LIST token_lifetime = 7
To require confirmations when subscribing, but allow people to unsubscribe without confirmation, use the following commands:
configset LIST subscribe_policy = open+confirm configset LIST unsubscribe_policy = openThis is shown on the recipe page.
These options may be set to one of the following values:
As an example, to restrict the subscriber list to only the owners, use the following command:
configset LIST who_access = closed
configset LIST access_rules <<HERE post consult, reason="Address was not found in the subscriber list" !@MAIN HERE
Since this configset command occupies more than one line, it uses the "here document" format. The "<<HERE" portion tells majordomo to use all of the following lines, up to a line beginning with HERE, as the value of the access_rules option. The tag "HERE" is arbitrary...you can use any word you like to indicate the end of the here document.
Another useful setting is to restrict incoming messages that don't have the list's address in either the To: or Cc: header. Use the admin_headers option as follows...
configset LIST admin_headers <<THEEND !/(To|Cc):.*LIST/i THEEND
The access_rules and admin_headers options are complicated and powerful. Briefly, each rule has three parts, and each part appears on a separate line. The parts are
To get more information about the access rules, use the majordomo commands
help configset_access_rules help configset_admin_bodyIt is not necessary to use a password for the help commands. In fact, a bug in majordomo will keep help commands from working if the default password command is used in the same message.
newinfo LIST <<ENDABC Welcome to the LIST mailing list To post messages to the list, write to $LIST@csf.colorado.edu. If you need help, write to $OWNER. ENDABCThe value of $LIST (the mailing address of the list) and $OWNER (the list owner address, e.g., "LISTfirstname.lastname@example.org") will be filled in automatically.
For the faq and intro documents, use newfaq and newintro in place of newinfo, and rewrite the here document to meet your needs. Each of these three documents (info, intro, faq) may be retrieved using the command of the same name.
The short and long descriptions are sent to people who use the lists and lists-long commands, respectively. If the long description isn't defined, the short description is used in its place. Here is an example:
configset LIST description = Discussion of the colors of the rainbow. configset LIST description_long <<ENDTAG Some people say the rainbow has seven colors: red, orange, yellow, green, blue, indigo, and violet. Others look upon it a a continuity of colors. Aristotle wrote that the rainbow has precisely three colors. This list is for rainbow lovers of all colors, to meet and exchange views on one of nature's great marvels. See http://haldjas.folklore.ee/folklore/vol6/rainbow.htm to learn more about the folklore of the rainbow. ENDTAG
Each digest has eight variables, which are listed in the following table.
|Name||A one-word name for the digest. When subscribers use the set LIST digest-NAME-TYPE command, this name may be used in place of NAME.||No default value.|
|Time||Hour, day, weekday, or month during which digests may be created. May be a range of values.||Anytime.|
|Minimum Size||Minimum number of messages and/or kilobytes in a digest.||Zero.|
|Maximum Size||Maximum number of messages and/or kilobytes in a digest.||Infinite.|
|Maximum Age||Greatest age allowed for the oldest message in a digest.||Infinite.|
|Delay||Minimum amount of time between digests.||Zero.|
|Minimum Age||Smallest age allowed for the youngest message in a digest.||Zero.|
|Type||Digest format; may be text, mime, or index.||mime|
When a digest is defined, vertical bars are used to separate the values. Following each set of values is a one-line description of the digest. If a value is omitted, the default value is used instead. For example, the following commands create two digests, one of which is distributed daily between 6 PM and 11 PM, and the other once every four days. The daily digest has a limit of 100 kilobytes; the tetra-daily digest, 250 kilobytes.
configset LIST digests <<DONE daily | 18-23 | 50k | 100k | | | | LIST Daily Digest tetra | 1st, 5th, 9th, 13th, 17th, 21st, 25th, 29th | 30k | 250k | | | | LIST Semiweekly Digest DONEIf a subscriber uses the command set LIST digest, majordomo will use the settings in the first digest you define. In the example you just saw, set LIST digest and set LIST digest-daily-mime would have the same effect.
For more details, use the majordomo command
configshow LIST owners
This command will return to you the list of owners as part of a configset command. Edit that list and return the configset command to majordomo.
configset LIST archive_split = weeklyThe maximum size of each archive file may be configured using the archive_size option.
To obtain the list archives, first use the index-recursive command to obtain a list of files; then retrieve the archive using the get command. The archive command can also be used to view a summary or the complete text of one or more messages.
configset LIST message_footer <<TAG ===== To leave this mailing list, send a message to email@example.com. In the body of the message, put the command unsubscribe LIST TAG
Subject prefixes appear at the beginning of the Subject: header. Configuration is as expected:
configset LIST subject_prefix = [LIST]