Michael Donohue wrote:
> On line 385 of your listname.config file, there is an entry for
> restrict_post. The syntax for this value is:
> restrict_post = listname:listname-digest
Actually, this can also be a "<space>" separated list, and you are not
limited to just listname and listname-digest. You could also use
someother-listname, someother-listname-digest, or even a root-anchored
filename in some other directory as long as majordomo can read that
file. (/home/username/thisfile for example)
If you have direct access to the majordomo/lists directory, you can put
any filename in the list of restrict_post setting that contains or will
contain nothing but email addresses. The requirements are, the file
must exist, be readable (and preferably writable) by majordomo, and hold
the email address of at least the list-owner (yours?).
A little trick I use, is to create a majordomo/lists/listname-post file.
Because there is not already a period (dot) in the filename, it itself
becomes a mini majordomo list, but there are no aliases required to be
created for it. Majordomo will create a default listname-post.config
file the next time it sees this file in the lists directory. The real
trick in not requiring an alias to be created is in how the
listname-post.config file is set up.
1. Turn off announcements, administrivia, and welcome messages.
2. Make all *_access and (un)subscribe_policy settings "closed".
3. Hide the list with the noadvertise setting, /.*/
As long as these settings are followed, there should never be a reason
for majordomo to attempt to deliver a message to an owner/approval
address for the fake list, and therefore need for an alias to be created.
The advantage now, is that you can add and remove people from this list
just like any other majordomo list. This can be used for situations
where you have an announcements only list, that only a couple people in
the company/organization are allowed to post and you do not want list
members themselves to post or reply back to the list, or for adding
non-subscriber email addresses to a discussion type list for those folks
that try to post from several addresses but are only subscribed at one.
This of course, assumes that you "know" the extra addresses actually
belong to the same person. :)
> What the Major is telling you is that he cannot find the files that you
> have pointed him to in this entry.
> Do the files in question exist in the majordomo/Lists directory?
> These files should contain the email addresses of your list members, one
> per line.
> Please post that section of your config if this does not help.
> At Wednesday 18:26 5/24/2000, you wrote:
> >I am having trouble using the newconfig command on one of my lists on
> >swe.org. Here is the system info:
> >Below is the message I get when I try to update the config file for the
> >list swe-testme. Any ideas what I am doing wrong?
> Michael K Donohue
> Webmaster/Sys Admin
> Bardic Solutions