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?
*******************************************************
Ron Emaus remaus@cic.net
CICNet, Inc 313.998.6419 Voice
2901 Hubbard 313.998.6105 FAX
Ann Arbor, MI 48105
*******************************************************
|
|
