Yours is a dilema I think most of us have trudged through at some point
or another. The proper answer would be that regardless how many names
are actually the same domain, only the address used when subscribing is
valid as far as majordomo is concerned. Can we assUme that the list in
question is used only for the domains mentioned? If so, you could write
a script that adds all the variations of domain names per member of your
list.restrict that gets executed by cron nightly.
A work-around, could be something like this;
listname = sports
.../lists/sports.config
restrict_post = sports:sports-post:sports-digest
.../lists/sports-post.config
restrict_post = master.post
moderated = yes
moderator = owner-sports
subscribe_policy = closed+confirm
unsubscribe_policy = closed+confirm
No extra aliases required for this. Requests to Post-Only membership
for the sports list are managed by majordomo, and majordomo IS aware
of the sports-post list by existance of the file and the config.
Anyone wanting to post but not receive sports list messages may send
a subscribe message to majordomo using the alternate domain (or the
alternate format of the subscribe command) and the sports-post list
membership. These requests would of course have to be approved by
the sports list owner, so they could validate membership in the other
list with the other domain name.
The above work-around also assUmes that you allow anyone on the list
to post to the list. If sports-post or sports-digest files do not
exist, the list still works.
Using your Joe Shmoe example, js@world.std.com subscribes to sports.
He would also have to send subscribe requests to sports-post as
js@world.com and as js@theworld.com. A single email to majordomo
would look like this to handle the whole process;
To: majordomo@world.std.com
From: Joe Shmoe <js@world.std.com>
Subject:
subscribe sports
subscribe sports-post js@world.com
subscribe sports-post js@theworld.com
end
Yet another solution, would be to download and modify the script
I wrote which sits on a listname-subscribe alias. If you can
understand/write perl scripts, take a look at;
ftp://ftp.ccsf.org/majordomo-contrib/subscribe.1
Some additional if/then statements and domain matching regular
expressions for populating the print message portion of the
script to match what I proposed above should not be too hard.
Dan Liston
"Steven W. Orr" wrote:
>
> I have a few lists that I run here. Some of the people on my lists are
> from world.std.com which is a company here in Brookline Mass called
> Software Tool and Die. Over the years they also bought the domain
> world.com as well as theworld.com. My problem is as follows:
>
> Joe Shmoe signs up for a list as js@world.std.com and everything is hunky
> dory. The list is copied to list.restrict to prevent people who are not on
> the list from being able to post. Then he send mail again but this time
> his from addr is js@theworld.com instead of js@world.std.com. This causes
> majordomo to reject the message thinking that the message is coming from
> someone who is not in the restrict list.
>
> I realize that this may not be a majordomo problem. Is there a way to fix
> this in majordomo? And if not, is there a way to fix this in sendmail?
>
> Many thank all.
>
> --
> -Time flies like the wind. Fruit flies like a banana. Stranger things have -
> -happened but none stranger than this. Does your driver's license say Organ
> -Donor?Black holes are where God divided by zero. Listen to me! We are all-
> -individuals! What if this weren't a hypothetical question? steveo@syslang.net
Follow-Ups:
References:
|
|
