RE: [cobalt-users] MajorDomo Manual Config

[Robert Fitzpatrick <webmaster@xxxxxxxxxxx>]

>> Can't we make it (the script) take the 'listname' value and 
>add a (hard
>> coded) '.restrict' to the end of it just as it drops the value at the
>> 'restrict_post' line. Then we are left only ever needing to 
>make and edit
>> 'test.restrict'. Anybody getting this far into the CGI could 
>probably make
>> the 'test.restrict' file get created automatically, only 
>needing a quick
>> edit in telnet.

I think the hard code thing would be easier than what I'm thinking (for the
admin, that is, but what about the user).

I found all of the files, I believe that control not only the Majordomo
configurations, but everything for that matter. The CGI that the online GUI
forms post to when a user is modifying a MD list is calling Perl modules,
for instance 'use Cobalt::List'. These modules are located at
'/usr/lib/perl5/site_perl/5.005/Cobalt/', at least on my RaQ3. Everything is
CGI/Perl, so I will be attempting to add a field onto the GUI form to allow
entering a 'restrict_post' value. And then modify the CGI/Module to accept
the information and right the appropriate value in the config file when it
is modified. If it works, then I'll add something to allow them to edit the
file. Can you specify an absolute or relative path in the 'restrict_post'
variable in the MD config file? I've never tried, but if it works to put
'/home/sites/home/site#/majordomo/list.restrict' as the value, that would be
great. Has anyone tried that before in a Majordomo list? Maybe I'll pass
that one along to the Majordomo users list.

>It's been a long time since I've looked at the Cobalt CGI files for
>majordomo, but I should warn you that any changes may be overwritten by
>future Cobalt packages you install so be sure to backup the 
>files you modify
>and be prepared to modify the files again after applying the 
>packages.

I know, I know, the Cobalt updates may overwrite this in the future. I will
just plan on keeping a copy (of course) and deal with it. And backup,
backup, backup.....:) We'll see what happens. I don't know when I'll get
around to it, this is a new server that 100 users have to be transferred to
before I can get to this kind of stuff, but the users will be transferred by
Sep 1 (I hope). If anyone finds an alternatively solution for allowing the
users control over the config file such as this, please let me know.

--
Robert Fitzpatrick
WebTent Networking, Inc.
PO Box 10785
Tampa, FL 33679-0785
US
Tel: (813) 281-2253