> Lately, I was asked to change the setting of a few features, and I
> used config to obtain the configuration file of the list in question
> and then sent it back after modification by newconfig.
>
> Well, for some strange reasons, the newconfig doesn't accept my new
> configuration and reported back an error.
>
> I recall that I used the config/newconfig in the past, the last time
> probably last summer and it worked flawlessly.
>
> After some experimentation this time, however, I found that the
> newconfig even refuses to accept the UNMODIFIED config that it sent me
> when I issued config. Further the error message suggests that
> something is totally broken. But I am not sure what (maybe upgraded
> perl?).
Try this sequence of operations:
writeconfig yourlist
config yourlist
[edit config file]
newconfig yourlist
The writeconfig command will write a clean, correctly formatted config
file for you using the current settings that majordomo is using for your
list.
--
If more government is the answer, it must have been a really stupid question.
phil stracchino ---- terminal cynical boy ---- mystic zen biker geek
-> see http://www.babcom.com/whitelist.html to bypass the spam filter <-
References:
|
|
