rja@edison.GE.COM (rja) (09/26/88)
A lot of AT&T sites still generate headers identifying themselves as
machine-name-here.UUCP or something other than machine-name-here.ATT.COM.
This makes accurate routing harder especially now that AT&T only handles
internal mail routing -- the problem is that mail senders don't always
know which sites are internal to the ATT domain and so a path through
att is OK and which sites merely have paths which (erroneously these days)
route their mail through ATT.
I think that the answer is for ATT sites to convert their machines over
to the full domain system -- at least for all sites who can send mail or
post news that might get outside of ATT. If all ATT sites identify
themselves by a fully qualified domain name, routing is simple and easy
by comparison with the status quo.
Will someone at AT&T please let the rest of us know if this is going to
happen and if so in what kind of timeframe ?? A definitive posting
from someone at AT&T would be greatly appreciated.
Thanks,
Ran
P.S. In the places above where I wrote machine-name-here you can
substitute a valid sub-domain-name within the ATT.COM domain. (Which is
to acknowldedge that domain-names aren't always the same as machine names.)
______________________________________________________________________________
rja@edison.GE.COM or ...uunet!virginia!edison!rja
via Internet (preferable) via uucp (if you must)
______________________________________________________________________________