Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!mailrus!cornell!batcomputer!itsgw!steinmetz!ge-dab!ge-rtp!edison!rja
From: rja@edison.GE.COM (rja)
Newsgroups: comp.mail.uucp
Subject: problems with att machine naming?
Summary: inquiry
Message-ID: <1650@edison.GE.COM>
Date: 25 Sep 88 17:55:37 GMT
References: <1988Sep23.105347.652@lsuc.uucp> <2300@att.ATT.COM>
Organization: GE-Fanuc North America
Lines: 30

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)
______________________________________________________________________________