Re: [cobalt-users] Mail lists and config file

[Alfredo <alfredo@xxxxxxxxxxxxxxx>]

> The user is uploading his new config file and It seems there is something
> wrong with the creation of file
> /usr/local/majordomo/www.domain/lists/listname.new
>
> Now it seems looking through the list and the help I got on my last email I
> need to change the config_parse.pl but too what as it seems that each email
> I look at some say one line needs changing others say a few more ?


It's only a one line change as I see it in the archives, Andrew. The 
whole section of lines is quoted but only for context. Here's part of 
what's in that post (from April) and the "x's" are mine:

XXXXXXXXXXX

*** config_parse.pl     Sun Apr 16 20:06:37 2000
--- config_parse_fix.pl Sun Apr 23 17:20:50 2000
***************
*** 119,125 ****
                                      # to null if it is not a -digest list,
                                      # or the non-digest list if it is
                                      # a -digest list.
!         'restrict_post',       '#!"$list"',   # Like -I in resend
          'purge_received',     'no', # Remove received lines
          'administrivia',      'yes',# Enable administrivia checks
        'resend_host',          '',   # Change the host name
--- 119,125 ----
                                      # to null if it is not a -digest list,
                                      # or the non-digest list if it is
                                      # a -digest list.
!         'restrict_post',       '#!"$baselist"',   # Like -I in resend
          'purge_received',     'no', # Remove received lines
          'administrivia',      'yes',# Enable administrivia checks
        'resend_host',          '',   # Change the host name


XXXXXXXX

Okay. Check closely and you'll see that this is the only line that changes

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

to

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



The original post from the archives, with the full explanation and 
rationale is at :

list.cobalt.com/pipermail/cobalt-users/2000-April/010792.html

As I said before, this should be tested after copying the original 
config_parse file because I can't say whether it will affect GUI 
operations. But as far as I know, there is no Cobalt workaround for 
this because, I would guess, the GUI doesn't support it and Cobalt 
generally doesn't "patch" stuff that doesn't work through the GUI.

Hope this helps.

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