I have experimented and found out this out:
I had further restricted who could post to the list to just be the
administrator of the mailing list. I did this by editing the
"listname.config", specifically the "restrict_post" flag. Default setting
was:
restrict_post = listname:listname.administrator
I changed it to be:
restrict_post = listname.administrator
Under that arrangement, only the email address in the listname.administrator
file can successfully get results for an "info listname" command in
Majordomo. Under the original configuration, only email addresses
subscribed to the list as well as the administrator could get results for an
"info listname" command. What the post restriction configuration has to do
with this, I have no idea.
There is another flag that can be set, "private_info". If set to "no" the
requestor doesn't have to be subscribed to get results for an "info
listname" command. Setting this flag had no results. I would think the
purpose of the "info" command is to tell others what this list is about,
subscribed or not, or whether authorized to post or not.
Apparently it's not working this way. Thoughts?
-----Original Message-----
From: Darrell D. Mobley [mailto:dmobley (at mark) uhostme.net]
Sent: Saturday, May 06, 2006 4:55 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:05080] Re: majordomo
I have a mailing list set up and created an 'info' file for it by using the
Majordomo email command "newinfo list password" and then the body of the
information. The information was correctly captured on the server and
placed into a file named "listname.info" in the lists directory.
When I send another command back to majordomo requesting "info listname"
Majordomo returns an email "#### No info available for listname." Does the
info command work in Majordomo or does the info filename have to be
identified/configured?