Re: [cobalt-users] MajorDomo Manual Config

["Steve Werby" <steve-lists@xxxxxxxxxxxx>]

"Tim Lawson" <timl@xxxxxxxxxxxxxx> wrote:
> 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.

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.  What
you're attempting to do is definitely logical and reasonable.  If you don't
require Cobalt's GUI for majordomo then another solution is to install a
second copy of majordomo.  On my machines I have several copies installed.
Since they don't run as a daemon (majordomo just runs as emails are sent to
majordomo) there is no measurable additional load on the server (aliases
file and virtusertable will have more records).  All of majordomo can be
entirely administered through email by sending commands to majordomo to edit
the conf file and administer lists.  I don't know if that's a solution that
will work based on your needs, but it does for me.

--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/