Re: [cobalt-users] Majordomo an RAQ3

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

"Cobalt-Canada" <info@xxxxxxxxxxxxxxxxx> wrote:
> > restrict_post = FILE_HERE
> >
> > where FILE_HERE is a file containing the email address of the person(s)
> > allowed to post to the list.
> >
> > You could also make the list moderated, which will allow others to send
> > messages to the list, which will only be posted after a list
administrator
> > approves it.  In this case, set:
> >
> > moderate = yes
> >
>
> Keep in mind that every time you use the GUI to add or remove email
> addresses to/from the mailing list, you will have to edit the
> "restrict_post" entry in the configuration file again as the GUI keeps
> changing it back to restrict_post = nameofmailinglist (whatever the name
of
> the mailing is.)

It does?  Ouch!  I forgot to mention that I've installed a second copy of
majordomo on all of my RaQs and I use it instead of the Cobalt copy for all
my mailing lists so I edit all of the virtusertable, alias and config files
by hand and have archiving and digests setup (I don't even recall if they
were possible to setup through the Cobalt GUI).  If the "moderate" setting
doesn't get overwritten then perhaps this is a better (though potentially
less ideal) solution given the behavior of the GUI.  And if enough of you
find this behavior of the GUI to be inadequate perhaps you should let your
voices be known to Cobalt so they can change the behavior in an upgrade and
future OS versions.  Cobalt's code probably easily be hacked (perhaps by
commenting out some lines) to prevent this behavior, but it's probably a
better idea to learn to use majordomo commands to administer the list.  The
entire list configuration file, subscriptions and moderation can all be
handled via email by issuing the proper commands to majordomo.

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