Re: [cobalt-users] mail lists

[Alfredo <alfredo@xxxxxxxxxxxxxxx>]

> He seems to request the config file through majordomo this seems OK ( I am
> not too sure of this command)


config listname password

> then he changes the congig file
>
> than uploads it - here he gets an error message :-( and again not too suer
> what the comand is so I can test it)


newconfig listname password

(that's the list's administrative password by the way and the 
commands go to majordomo@xxxxxxxxxxxxxxxxxxx (what that is in your 
case).

Andrew,

There's this set of instructions and commands that's on web pages all 
over the place. One place is:

www.marketing-magic.net/tutorial_majordomo.htm

There's a huge FAQ on the program and one place for that is:

www.greatcircle.com/majordomo/majordomo-faq.html

By the way, greatcircle.com is the place where majordomo sort of resides. :-)

Anyway...

You don't say what the error is. :-) My hunch is that it's an error 
saying that majordomo can't create a file with the suffix ".new" or 
something like that? I don't remember the exact error message myself.

It's a common issue and it's all over the list archives. There's a 
problem in the Raq3 with doing the majordomo list config file changes 
by email and the problem apparently resides with a line in the file

/usr/local/majordomo/config_parse.pl

this line:

       'restrict_post',       '#!"$list"',   # Like -I in resend

There's a suggestion in the archives that this be changed to

       'restrict_post',       '#!"$baselist"',   # Like -I in resend

That's supposed to enable email config changes but I've not tried it 
and have no idea if it would have an impact on the GUI interface with 
majordomo (doesn't seem that it would but I can't vouch for that -- I 
just haven't had any reason to try it).

The bottom line is that you can make any config change you want for 
basic majordomo lists (with only a few exceptions that are commented 
in the config file itself). The only issue is getting the revised 
config file uploaded and accepted.

I make changes to these files by Telnet but you can also download the 
config file, make the change with a text editor and re-up the file 
through ftp (being careful of permissions). The changes take place 
immediately; no need to restart anything.

That doesn't allow our client to do anything, though and you probably 
won't want the client going into this section of your server (the 
config files are in /usr/local/majordomo/lists).

If you want the client to deal with majordomo himself or herself by 
email, then you might just copy the parse file

cp /usr/local/majordomo/config_parse.pl 
/usr/local/majordomo/config_parsecopy.pl or something like that

and try making the change in the original file on that line and see 
if everything is okay.

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