I need some help. I applied the restrict2domain patch and it works nicely
with majordomo. That is, the config can be written w/o any error reported,
and restrict_post works nicely for the list.
However, when a listowner tries to wirte the same, unchanged config with the
MajorCool web page, the same definitions are being flagged as errors by
config_parse.pl:
config_parse.pl: push(@errors, "Can't find restrict_post file $_ at line $.\n" )
The message emailed to the listowner is:
>>>> newconfig alpha PASSWD
The new config file for alpha was NOT accepted because:
Can't find restrict_post file /email/mj/Lists/@earthlink.net at line 54
Can't find restrict_post file /email/mj/Lists/@sbc.net at line 54
>>>> writeconfig alpha mmm
wrote new config for list alpha.
It just re-writes the file that was there. If the list-owner changed a
different keyword value, it doesn't get written.
The restrict_post keyword is set like this:
restrict_post = @earthlink.net:@sbc.net
Everything *works* except for trying to write the config via MajorCool.
Oh, and MC does NOT complain in the web page about the config.
Any help would be appreciated. I'm pulling my hair out. It's not a pretty
sight.
deb
Follow-Ups:
|
|
