Geesh. I feel like such a newbie. Thanks for all the help on my previous
posts. I'm now trying to do newconfig. Majordomo is griping about lines
that are actually comments. Can anyone tell me what is wrong here?
I did a Config list passwd and saved the output to a file. At the top of
the file are a bunch of comments about the format of the file, and a few
lines were really long, like they were missing some <returns>. It
originally griped about those lines and I added returns in front of the
embedded '#' signs where it looked like they meant to start a new line.
Bottom line, all the comments at the top now start with # in the first
column. Other than that, I changed a couple of parameters, like moderate,
and tried to send it back with newconfig. Any help is appreciated...
Should I just strip out all the comments and just submit the key-values?
This would be a real pain if I have to do that everytime I want to change
something.
Now, I'm getting errors with the following:
>> unknown key |which| in file sfaustingc.new.config at line 29
# regexp -- A perl style regular expression with
# leading and trailing /'s.
# restrict_post -- a series of space or : separated file names in
which
# to look up the senders address
# (restrict-post should go away to be replaced by an
>> unknown key |<majordomo,resend,di| in file sfaustingc.new.config at line
307
# sender [word] (owner-sfaustingc)
<majordomo,resend,di
# The envelope and sender address for the resent mail. This string
# has "@" and the value of resend_host appended to it to make a
and
>> unknown key |/open;closed;auto;op| in file sfaustingc.new.config at line
332
subject_prefix =
# subscribe_policy [enum] (open) <majordomo>
/open;closed;auto;op
# One of three values: open, closed, auto; plus an optional
# modifier: '+confirm'. Open allows people to subscribe themselves
and
>> unknown key |open| in file sfaustingc.new.config at line 341
Can't even find this one. I'm thinking that majordomo is stripping out
blank lines before processing, so the line numbers are off a bit. Correct?
Thanks,
Robert
~~
Robert Poldervaart
rpoldervaart@lgc.com
Follow-Ups:
|
|
