smail-2.5 fix for domain gateway routing

Jim Mercer merce at iguana.uucp
Thu Jan 24 14:02:28 AEST 1991


In article <1991Jan23.061830.19719 at watdragon.waterloo.edu> gamiddleton at watdragon.waterloo.edu (Guy Middleton) writes:
>In article <1991Jan14.234354.8055 at eci386.uucp> woods at eci386 (Greg A. Woods) writes:
>> Here's the problem, as told by Mark Moraes <moraes at cs.toronto.edu>:
>> 
>> 	When looking up "foo.xenitec.on.ca", first look it up as is.
>> 	If matched, replace the %s in the path with username.  Else,
>> 	remove the first domain component (foo) and look up
>> 	".xenitec.on.ca".  If that matches, replace the %s in the path
>> 	with THE FULL DOMAIN NAME AND username.  I.e:
>> 
>> 		lsuc!utai!watmath!foo.xenitec.on.ca!user
>> 	NOT
>> 		lsuc!utai!watmath!user
>> 
>> 	smail2.5 interprets it the latter way, which is wrong.
>
>I think it would be nicer if the result was
>
>	lsuc!utai!watmath!xenitec!user
>
>That way, I could use smail on watmath to decide that foo.xenitec.on.ca was a
>local connection, instead of having to embed that information in my
>sendmail.cf file.

i think this would be best:

	lsuc!utai!watmath!xenitec!foo.xenitec.on.ca!user

that way xenitec at least has a chance at determining which sub-system "user"
is on.

otherwise, you have to assume that xenitec has aliases on it for ALL of the 
users on ALL of it's subdomain.

i beleive this was stated in a previous article (woods at eci386 or bdb at becker)
where it basically said that:

user at sub.registered.domain

might find an entry in the paths database like:

.registered.domain	<appropriate path to .registered.domain MS'er (server)>!%s

and that %s would be the full address specified (ie sub.registered.domain!user)

-- 
[ Jim Mercer   work: jim at lsuc.on.ca  home: merce at iguana.uucp  +1 519 570-3467 ]
[                "Clickity-Click, Barba-Trick" - The Barbapapas               ]



More information about the Comp.sources.bugs mailing list