The following is from the NEWLIST file included with majordomo and
modified by me for clarification or update in a few places.
To create a list:
1) Create an empty file called <listname> in $listdir, mode 644.
The location of $listdir is defined in your majordomo.cf file.
(As the majordomo user, `touch $listdir/<listname>`, or better yet,
`echo your.email@your.domain > $listdir/<listname>`)
2) Create a file called "<listname>.info" in $listdir, mode 644, with
the initial introductory info for the list in it. (This can be
done later via email with the 'newinfo' command.)
3) Create a file called "<listname>.intro" in $listdir, mode 644, with
the initial welcome info for the list in it. (This can be done
later via email with the 'newintro' command.)
4) Create the appropriate entries for the list in your Sendmail
aliases file (/etc/aliases or a separate majordomo.aliases file.)
Each list requires several aliases. For an example list called
'test', these aliases are required:
test The list alias itself
owner-test The owner of the list (who should get bounces)
test-request The address for administrative requests.
test-approval The person who approves postings to the list
(for moderated lists as well as unmoderated ones)
These would look like this:
test: :include:/path/to/majordomo/lists/test
owner-test: your.email@your.domain,
test-request: "|/path/to/majordomo/wrapper request-answer test"
test-approval: your.email@your.domain
It's more likely that the outgoing messages to the list will be
passed through "resend" to catch Majordomo commands, as well as
give other useful features. A typical set of aliases without anything
fancy, such as archiving or digesting, would look like this:
test: "|/path/to/majordomo/wrapper resend -l test test-list"
test-list: :include:/path/to/majordomo/lists/test
owner-test: your.email@your.domain,
test-owner: your.email@your.domain
test-request: "|/path/to/majordomo/wrapper majordomo -l test"
Finally, a more complete set of aliases that provides digestification,
archiving, and header manipulation would look like:
test: "|/path/to/majordomo/wrapper resend -l test test-outgoing"
test-digest: test
# I put the digest and archive programs on the outgoing list so that
# messages bounced by resend don't end up in the digest or archive
# unless I send them through resend explicitly.
test-outgoing: :include:/usr/local/Lists/test,
"|/path/to/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing",
"|/path/to/majordomo/wrapper archive2.pl -a -M -f /path/to/majordomo/archive/test/test.archive"
# archive produces a monthly archive with the -M flag.
# Also note that indented lines in the aliases file indicate a
# continuation of the previous line above it.
test-digest-outgoing: :include:/path/to/majordomo/lists/test-digest
owner-test: your.email@your.domain,
owner-test-outgoing: owner-test
# note that the "-digest" and "-digest-outgoing" suffixes
# are required to allow the majordomo mkdigest command, and the
# config code to work properly.
owner-test-digest: owner-test
owner-test-digest-outgoing: owner-test
test-request: "|/path/to/majordomo/wrapper request-answer test"
test-digest-request: "|/path/to/majordomo/wrapper request-answer test-digest"
test-approval: your.email@your.domain,
test-digest-approval: test-approval
As you can see, setting up a list can be quite complex.
You can run majordomo at the -request address (recommended), and it will
handle requests such as:
subscribe
unsubscribe
signoff
without requiring the user to supply a list name. To do this set up an
alias similar to:
test-request: "|/path/to/majordomo/wrapper majordomo -l test"
Where the argument to -l is the name of the list.
Hopefully in a future release of majordomo archive2.pl will be
integrated into majordomo so that the frequency of archive rollover
(daily, monthly, yearly) will be controllable via the config file
mechanism.
***** NOTE: CONVERTING FROM A PREVIOUS MAJORDOMO VERSION *****
For those who are converting from an earlier version of
majordomo, note that resend has very few command line
arguments. If you don't strip the command line arguments from resend,
the comments in the configuration file that deal with default
values for resend will be incorrect.
More examples of alias setups can be found in the file majordomo.aliases.
For sendmail users, don't forget to run 'newaliases' to rebuild the
alias database.
5) If the list will be archived, create an archive directory in the
location specified by the $filedir and $filedir_suffix variables.
6) If the list has a digest, create a digest work (incoming) subdirectory
under $digest_work_dir. Use the same name as the digest list (example:
test-digest). You must also create an archive directory for the digest
list as explained in step 5.
7) Finally, make sure everything is owned by user majordomo, group
majordomo, and writable only by the owner (i.e., mode 644 for
files and mode 755 for directories).
8) Now issue a 'config <listname> <listname>.admin' command to
Majordomo. This will cause it to create a default configuration
file for the list, and send it back to you. Make any desired
changes, SUCH AS CHANGING THE DEFAULT PASSWORDS, as well as adding
a description, and send it back with the 'newconfig' command.
NOTE: Issuing commands to majordomo is done via email messages to the
majordomo alias on the system you just set up. Subject lines can be
blank, and the syntax of most commands is a non-wrapped line in the body
of the message containing <command> <listname> <password>. There are
exceptions to this syntax, and multiple commands can be sent in the same
message (but only one command per line). Please ready your
list-owner-info file in the Doc directory of your installation for a
complete description of commands available only to list owners.
Now send a test subscribe and unsubscribe, just to further verify that
the list is working.
Dan Liston
Manoj Mishra wrote:
>
> Hi Daniel,
>
> Thanks for your continuous support, I have set all the settings as
>mentioned by you, and all steps seem to give positive results, i am
>confused at one instance that for a list we have a listname file which
>contains the mail id of the members who are in that list, a
>listname.config file, a listname.info file etc. I am not aware how does
>the listname.config file gets created as i don't have any listname.config
>file in my lists directory.....
Listname.config gets created by majordomo the first time the list
is accessed. Step 8 above, or editing the file from the OS shell
will allow configuration changes.
> As soon as i am sending mail from outside to say listname@sgippd7.sdrc.com
>and check for mailq at sgippd7 i get a message no control file, probably
>this is due to not having the listname.config file, kindly guide me about
>the very initial list creation steps....
>
> Regards
> Manoj
References:
|
|
