Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!cmcl2!yale!husc6!mit-eddie!rutgers!clyde!cbatt!ukma!david From: david@ukma.ms.uky.csnet (David Herron, NPR Lover) Newsgroups: comp.mail.uucp Subject: Re: How do I tell an internet address from a UUCP address? Message-ID: <5271@ukme.ukma.ms.uky.csnet> Date: Fri, 5-Dec-86 17:32:24 EST Article-I.D.: ukme.5271 Posted: Fri Dec 5 17:32:24 1986 Date-Received: Sun, 7-Dec-86 02:42:41 EST References: <4058@mit-eddie.MIT.EDU> <5259@ukme.ukma.ms.uky.csnet> Organization: U of Kentucky, Mathematical Sciences, Lexington KY Lines: 73 Summary: seperation of domain and network address > From: Jeff Siegal > > In article <5259@ukme.ukma.ms.uky.csnet> you write: > >In article <4058@mit-eddie.MIT.EDU> nessus@eddie.MIT.EDU (Doug Alan) writes: > > > > > >hehehehe > > > > > >"Fixed in MMDF" > > > >MMDF *never* had this sort of problem ... > > Responses of this type don't seem (to me) to help anyone. > > Could you kindly post info on _how_ MMDF gets around this > problem, so that others can benefit from possible design > advantages of MMDF. > > Jeff Siegal OK... since ya asked (BTW folks, this is private mail that I'm quoting, hope Jeff doesn't mind)... MMDF seperates keeps the domain table(s) seperate from the routing table(s). One first designs a set of tables which describes all the domains. Then one designs another set of tables which describes the networks to which you are attached, and the domains which are present in each network. When the message comes in the domains are first "regularized" by looking in the domain tables to find the specific domain name. (Partial domain names are handled at this point by making repeated lookups stripping off lower levels of domains until an entry is found). Attached to each entry in the domain table is the "official name" for that domain. This "official" name is the tag used when looking in the channel tables. For each channel you list the domains to which you can send mail... the first channel which has the "official name" listed in it is the one through which the message is sent. There is also some validation going on here, one must be authorized for sending into particular channels. I suppose (but don't know because I've never done anything with authorization (yet)) that if the domain name were reachable by another channel, and a particular sender were not authorized for the first channel, that the message would travel through the second channel. "Out of the box" the scheme supports internet and uucp routing. I'm slowly building software to work nicely with bitnet as that is the third network we are attached to. Each of the three networks are at some stage of domainization at this point. A host can potentially appear in the channel table for all three networks. (In fact, this host I'm on now *really*does* appear in all three networks, just not with the same name (yet)). Sendmail on the other hand apparently has severe problems in doing something of this sort. My memory of the specifics is poor since it's been a couple of years since I tried to configure sendmail, and I never was able to get a good configuration. However, as I recall, the only kind of tables there can be are domain tables. There wasn't a way to have a domain-name to delivery-channel mapping... (would somebody who knows better please followup) I apologize for the tone of my earlier answer... I hope this answer is more useful. -- David Herron, cbosgd!ukma!david, david@UKMA.BITNET, david@ms.uky.csnet (I'm also "postmaster", "news", "netnews", "uucp", "mmdf", and ...) "What have I got in my pocketses?" -- I never heard such a stupid damn riddle!