Joel,
If you are using sendmail, 775 permissions are too loose.
Is your majordomo REALLY 1.94? Or is it 1.94.5?
What does the restrict_post = line in your testing.config look like?
The proper syntax is "restrict_post = filename", if filename is not
fully qualified, must exist in your /opt/majordomo/lists directory.
Filename must only contain email addresses, one per line, of users
that are allowed to post to your list.
Does your "problem" only manifest itself when using majorcool, or does
the same thing happen when emailing newconfig commands to majordomo?
Your list(s) must work WITHOUT majorcool before being able to trouble-
shoot majorcool.
Please post the results of these commands. Become root before issuing.
script output.txt
cd /opt
ls -ld majordomo
cd majordomo
ls -l
cd lists
ls -l
egrep '^[^# ]' testing.config
egrep -i '^(testing|majordomo)' /etc/aliases
egrep '^[$]' /etc/majordomo.cf
exit
If the first egrep above does not produce a list of settings in your
.config file, use "cat testing.config" instead. This would also be
a clue as to the format of your .config file being incorrect. The
whitespace between # and ] is <space> followed by <tab>. Carot signs
are just that (shift 6), not symbols for holding down the ctrl key
and pressing the character that follows.
Adjust the filenames in the second and third egrep to match your
environment for location/name of aliases and majordomo.cf files.
Now edit the output.txt file to make sure you will not be revealing
anything you consider "sensitive" about your system, and paste it
into a message to this list. Please make sure you have word-wrap
disabled before sending the output.txt file.
Dan Liston
"Joel M. Fisher" wrote:
>
> Hey All,
>
> Here's a little more info.
>
> installdir= /opt/majordomo
> permissions on $installdir/lists = 775 majordom:majordom
>
> If I run it command line I get the below output with config_parse.pl debug level
> 2.
>
> $ /opt/majordomo/wrapper majordomo < /tmp/message.txt
> get_config(/opt/majordomo/lists, testing)
> adding site-wide defaults
> Overriding with existing config files
> parsing config get_config(/opt/majordomo/lists, testing)
> get_config(/opt/majordomo/lists, testing.new)
> adding site-wide defaults
> Overriding with existing config files
> parsing config get_config(/opt/majordomo/lists, testing.new)
> Can't find restrict_post file /opt/majordomo/lists/testing.new at line 383
>
> My restrict_post is actually set to testing.restrict, so I'm not sure where it's
> getting the name testing.new.
>
> Solaris 8
> majordomo 1.94
>
> Any help would be appreciated.
>
> Thanks,
>
> Joel
> "Joel M. Fisher" wrote:
>
> > Hey All,
> >
> > I'm having a problem with newconfig. Anytime a config change is
> > submitted via email or majorcool I receive the below error.
> >
> > Any info would be appreciated.
> >
> > Thanks,
> >
> > Joel
> >
> > >>>> newconfig testing testingpass
> > The new config file for testing was NOT accepted because:
> > Can't find restrict_post file /opt/majordomo/lists/testing.new at line
> > 66
> > >>>> writeconfig testing testingpass
> > wrote new config for list testing.
References:
|
|
