Hey Daniel,
Thank you for your assistance.
I certainly don't have any problem keeping the discussion on the list, but I just
figured we could keep it off-line until resolved. At that point I would post a
summary.
Summary:
Turned out to be a problem in the config_parse.pl script. I made a change to the
file that majordomo didn't like.
Correct:
'restrict_post', '', # Like -I in resend
Incorrect:
'restrict_post', '#!"$list"', # Like -I in resend
Found a similar problem in the majordomo-users archive from 1996 which pointed me in
the right direction. I made the change so long ago I'd forgotten about it and it
appears no list owners have attempted changing their configs since.
FYI
solaris 2.8
sendmail 8.9.3
majordomo 1.94.5
netscape enterprise server(httpd)
Mail worked fine by itself.
newconfig/writeconfig didn't work from majorcool or via email(which are essentially
the same if I am correct).
Majorcool would load correctly into a browser so our http server supports cgi in
general and perl in specific.
Everything worked fine in majordomo except when you tried to update the configs
through majordomo features(i.e. newconfig/writeconfig)
Thanks again for responses.
Joel M. Fisher
Daniel Liston wrote:
> Joel,
>
> I don't answer majordomo questions privately, unless there is
> sensitive information in the message content that should not
> be viewed by all members of the majordomo-users list publicly.
> I will include direct copies of replies to the origin when I
> post responses to the list, just to insure the sender receives
> the reply quickly.
>
> Perhaps before asking new questions, you should explain the
> results or outcome of the recommendation that you examine the
> testing.config file for a restrict_post = line. What did that
> line contain? Did the filename on the right hand side of the
> equals sign exist? If the filename was not "fully qualified",
> did the file exist in the "lists" directory? What are the
> ownership, permissions, and contents of that file? If the
> RHS was empty, you should not have received an error. If the
> filename is pointing to a file that had zero size, add an
> address to it. "nobody@[127.0.0.1]" usually works nicely.
>
> Since the "end result" of your error message is a positive
> confirmation of the new config file being written, have you
> checked the config file against what was in the email to see
> if the changes "were" in fact accepted?
>
> Also, as a majordomo tenderfoot, you should specify what MTA
> and version of majordomo you are trying to run. Knowing what
> OS you are running on is also helpful. The only version of
> majorcool I have ever heard of is 1.32, so that is assumed on
> my part, and typically, I also assume apache for a web server.
> Does your MTA (sendmail, postfix, qmail, exim, etc.) work by
> itself, without complicating it with majordomo?
> Does majordomo work, without complicating it with majorcool?
> Does your web server work? Does it support .cgi?
> Is the machine/OS you are running on, yours? Hosted?
> Do you have root access?
>
> Dan Liston
>
> "Joel M. Fisher" wrote:
> >
> > Hey Daniel,
> >
> > Thanks for the response.
> >
> > This problem occurs on all of my lists. I'm pretty green with majordomo.... so
> > if you could answer a few simple questions for me.
> >
> > I would like to run majordomo from the command line so I can put a system call
> > trace on it... but I'm not sure what needs to be passed to it.
> >
> > Would something like this work? Somehow it has to know what email address the
> > request came from.
> >
> > # majordomo < newconfig.txt
> >
> > Contents of newconfig.txt something like.
> >
> > writeconfig testing testingpass
> >
> > # The configuration file for a majordomo mailing list.
> > # Comments start with the first # on a line, and continue to the end
> > # of the line. There is no way to escape the # character. The file
> > # uses either a key = value for simple (i.e. a single) values, or uses
> > # a here document
> > # key << END
> > # value 1
> > # value 2
> > # [ more values 1 per line]
> > # END
> > ........etc
> >
> > Any insight would be appreciated,
> >
> > Joel
> >
> > Daniel Liston wrote:
> >
> > > Look at your testing.config file for the error. You have defined
> > > a "restrict_post = filename" but that filename does not exist or
> > > does not have the correct ownership/permissions. This file must
> > > exist "before" it can be activated via a newconfig/writeconfig
> > > command.
> > >
> > > Dan Liston
> > >
> > > "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:
|
|
