>Date: Fri, 03 Mar 1995 10:49:18 -0500 (EST)
>From: Ron Emaus <remaus@great-lakes.net>
>
>Before I pursue alternate config files much further - it is true that
>very little info is used out of the config file. The main thing I use it
>for is to direct the user to two different "list" (and archive and
>digest) areas on the same machine (grant funded lists and commercial lists).
>
>If the paths to list directories, archive directories, and digest
>directories were all clearly present in the lists configuration file,
>then the only thing majordomo.cf would be needed for is to specify where
>the majordomo perl files were located.
>
>It's been my experience so far that the list-name.config doesn't seem to
>do anything for me so I put everything on the command lines in the alias
>file. Is this wrong? The most recent README says to use the config file
>but the config file says all the functions I want to use aren't
>implemented yet. What's true?
I would like to say that I think the config files are great and offer
lots of useful features. Since this list and the list-owners list often
contain debates about how to deal with people who send personal replies
to the list, I would like to mention that I find the ability to put
message_fronter << END
* The default address for replies is to post them to this list.
* If you want to reply to the poster, you must readdress the message
* (i.e., forward it) to $SENDER.
END
or
message_fronter << END
* Replies will probably go to $SENDER
* unless they are explicitly readdressed to $LIST@hed.bio.ns.ca
END
in each message automatically is a great help.
--
Bill Silvert, Habitat Ecology Div., Bedford Inst. Oceanography
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2
Personal InterNet Address: silvert@biome.bio.ns.ca
HED runs a WWW server at URL=http://biome.bio.dfo.ca
|
|
