RE: [cobalt-users] MajorDomo Manual Config

[Robert Fitzpatrick <webmaster@xxxxxxxxxxx>]

>
>Wish I knew how to find the part I would edit to make it (the 
>CGI) take the
>listname value and add the .restrict part.>
>

Well, to hard code the restrict list, you would need to edit the following
file:

	/usr/lib/perl5/site_perl/5.005/Cobalt/List.pm

You will see the following section:

sub list_config_restrict
# disallow spam to the mailing list
{
    my ($group, $fqdn, $list) = @_;
    my $ret = list_config_update($group, $fqdn, $list,
				 "restrict_post", $list);
    return $ret if ($ret !~ /^2/);
    return (MSG_ok("list_config_restrict"));
}

Change the line below while replacing 'restrict.file.name' with the name of
your file:

				 "restrict_post", "restrict.file.name");

That means anytime you don't check that box for 'Allow Unsubscribed Posting
to List', it will use that file name you specify. By doing this, then you
would need to use the same file name for all lists as your restrict list.
You could instead change the routine right after the one I showed you above
in the List.pm file by changing this line:

				 "restrict_post", "");

To this line:

				 "restrict_post", "restrict.file.name");

And then by doing this, when you check the box, it will use your list, when
you don't check the box, it would use the normal list for restrictions. Of
course, backup the file before making any changes. Let me know if it works.

>
>Food for thought... If you create a file name in the lists 
>directory without
>an extension (.anything) it shows up in the GUI as a sperate list.
>
>Using this principal, how good would it be to have the CGI 
>make not only
>'list1' but also make 'list1_admin' in the GUI so you could make the
>'list1.config' have the line 'restrict_post = list1_admin'.
>

Thanks for the food, maybe that will make it easier....:)

--
Robert Fitzpatrick
WebTent Networking, Inc.
PO Box 10785
Tampa, FL 33679-0785
US
Tel: (813) 281-2253