Re: [cobalt-users] list owner alias

["Puneet Pawaia" <puneet@xxxxxxxxxx>]

Hi,

Thanks for the info.

I did manage to modify the config of a test list in a similar manner. I used
a script called Commander that permits the execution of non-interactive
commands.

I copied the config file from the appropriate majordomo subdir to my web
directory folder and then downloaded the same to my hdd. Here I was able to
modify the file. I then uploaded the new config to my web directory and
again using commander, copied this file to the appropriate location. This
seems to have worked.

What I need to know is how to ensure that list-owner address is set rightly
to the actual list owner.

Regards
Puneet Pawaia
web : http://www.pawaia.com
e-mail : puneet@xxxxxxxxxx

"Only those who will risk going too far can possibly
find out how far one can go." T.S. Eliot...

----- Original Message -----
From: Alfredo <alfredo@xxxxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Wednesday, November 15, 2000 7:12 PM
Subject: Re: [cobalt-users] list owner alias


> >I then wanted to modify the config so that I customize the list, for
which I
> >used the list owner commands config and newconfig. However, I started
> >getting the following error
> >
> >The new config file for lucknow-l was NOT accepted because:
> >Can't find restrict_post file
> >/usr/local/majordomo/www.pawaia.com/lists/lucknow-l.new at line 387
>
>
> As it's configured, Puneet, majordomo on the Raq3 doesn't allow this
> email uploaded change. The problem is here:
>
> /usr/local/majordomo/config_parse.pl
>
> and it's on the following line in that file
>
> 'restrict_post',       '#!"$list"',   # Like -I in resend
>
> They did something to this function and it's probably related to the
> GUI's interaction with majordomo in the creation and configuration of
> the list. BUT, that doesn't help you and your real problem is...
>
> >I do not have telnet access.
>
> Oh oh! Because you need Telnet access for any of the fixes that have
> appeared on this list over the months (and there have been several
> that you can research in the archives, by the way).
>
> One fix, the one I use for several lists we run (all reconfigured),
> is to go into the list's config file and make the change (I use vi).
>
> In the file
>
> /usr/local/majordomo/thedomainname/lists (you know -- where
> thedomainname is the domain of the list) you'll see the config file
> itself listname.config. You can just make your config edits right
> there and save them. The changes take immediate effect -- you don't
> have to stop and start anything to make majordomo changes.
>
> The other is to go into the config_parse.pl file and make a small
> change in that one line above from "list" to "baselist" but I haven't
> tested that one yet so I'm not sure if it changes any of the GUI
> functions, etc.
>
> In any case, you need Telnet to do both of those. I've found that,
> without Telnet, you're really limited because, while it's a great
> machine for what it does, it's going to give you problems when you
> try to do something the GUI isn't configured for -- like really
> working with majordomo to do serious and professional lists. Then it
> requires changes to the configuration files that can't be made
> through the GUI.
>
> You should get them to give you Telnet access, I think.
>
> Alternatively, Jeff Lasman (a regular around here) specializes in
> majordomo professionally and has some services his company offers.
> Maybe he'll jump in at some point soon.
>
> Sorry I couldn't be more helpful but Telnet is the only way I know
> for dealing with these issues.
>
> Alfredo
> --
> People-Link/Institute for Mass Communications
> www.people-link.org
> Communications for a Better World...and for the People Who are Building
One!
> Members, Local 1180, Communications Workers of America, AFL-CIO
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>