Hi Roger,
Thanks for your help!
Using my current aliases below, majordomo doesn't respond to any commands. I
moved one name from my free-pctech-news list to my free-pctech-news-outgoing
list so there is something to be included as you suggested. I can send a
post to free-pctech-news-outgoing, and only the name in my free-pctech-news
list gets the post. So the include truely isn't working. Since I'm not
getting any majordomo responses or errors, something appears wrong with the
resend except that everything may be going to nobody (the null device lol).
My host provider origionally installed majordomo for me. Most of the files
in /majordomo have majordomo as the owner and daemon as the group.
Previously, in order just to get majordomo to reply to commands and allow
subscriptions to my free-pctech-news-list, I had to set the permissions on
my lists to
owner = daemon and group = daemon. I'm not sure if this is actually correct
or not. My instict is saying to bestow ownership of everything to majordomo
and group majordomo like the faq and other documentation suggests. However,
the majordomo group is invalid and I'm not versed in how to actually create
it as of yet using debian-linux.
This is what I am trying to accomplish and my assumptions are when all is
said in done:
1. Users will be able to subscribe/unsubscribe to free-pctech-news.
2. No one will be able to post to Free-PCTech-News
3. I will post to free-pctech-news-outgoing and listmembers of
free-pctech-news will recieve the post showing TO: free-pctech-news
4. when list command is issued only free-pctech-news list is advertised.
5 who command is disabled so no one can retrieve member list (this was
working prior to alias changes).
Previous working aliases
------------------------
majordomo: "|/majordomo/wrapper majordomo"
free-pctech-news: :include:/majordomo/lists/free-pctech-news
owner-free-pctech-news: mrwelch
free-pctech-news-request: "|/majordomo/wrapper request-answer
free-pctech-news"
free-pctech-news-approval: mrwelch
owner-test: mrwelch
Current aliases
-------------------
nobody: /dev/null
free-pctech-news: "|/majordomo/wrapper resend -h free-pctech-support.com -l
free-pctech-news free-pctech-news-outgoing,nobody"
free-pctech-news-outgoing: :include:/majordomo/lists/free-pctech-news
free-pctech-news-owner: mrwelch
free-pctech-news-outgoing-owner: mrwelch
approved-free-pctech-news-owner: mrwelch
free-pctech-news-request: "|/majordomo/wrapper request-answer
free-pctech-news"
free-pctech-news-approval: mrwelch
I believe there is a endless loop happening here but why?:
free-pctech-news: "|/majordomo/wrapper resend -h free-pctech-support.com -l
free-pctech-news free-pctech-news-outgoing,nobody"
thanks,
Michael Welch
-----Original Message-----
From: Roger B.A. Klorese [mailto:rogerk@queernet.org]
Sent: Tuesday, October 23, 2001 12:05 AM
To: Michael R. Welch
Subject: RE: How do I restrict posts?
At 10:41 PM 10/22/2001 -0700, you wrote:
>Hi, I took your suggestion but Houston there's a problem
>
>Here's how my new list aliases looks like:
>
>nobody: /dev/null
>free-pctech-news: "|/majordomo/wrapper resend -l
>free-pctech-news-outgoing,nobody"
you forgot the "-h free-pctech-support.com" option.
>I created a blank list called free-pctech-news-outgoing and posting to that
>works fine except for it shows the from being from
>free-pctech-news-outgoing@free-pctech-news instead of
>free-pctech-news@free-pctech-support.com(easily fixed in config I believe).
No, if the -outgoing is an :include: alias, nothing you do in the config
means squat.
>Also free-pctech-news outgoing is blank so I know the include is
>working.
If it's empty, sendmail will generate address/aliasing loop errors.
|
|
