Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!mcdchg!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.uucp
Subject: Re: Imminent death of UUCP Zone predicted
Message-ID: <1990Jul11.204251.6990@chinet.chi.il.us>
Date: 11 Jul 90 20:42:51 GMT
References: <7499@gollum.twg.com> <1990Jul10.133026.18326@terminator.cc.umich.edu>
Organization: Chinet - Public Access UNIX
Lines: 21

In article <1990Jul10.133026.18326@terminator.cc.umich.edu> honey@citi.umich.edu writes:
  >David S. Herron writes:
  >|> It would be better if that were somebody%stuff@cis.ohio-state.edu
  >|> (or %stuff.uucp) if only to avoid the operator-precedence problem.

>there is no ambiguity when an smtp speaker utters
>stuff!somebody@cis.ohio-state.edu to an smtp listener.
>see rfc 821.

The recipient in this particular conversation is unambiguous, but how
should the return address look when it hits the (uucp) mailbox?  If
"stuff" is A!B!C, what should the From_, From: and any To:/Cc: lines
look like at the receiving end, and how should non-ambiguous replies
be constructed, knowing that something!something@somewhere *is*
ambiguous in uucp-land?  Always saying user@domain is not a solution
if you assume that the intermediate uucp hops run out-of-the-box AT&T
rmail.  Even if user@domain is valid and what the user says, the
local mail has to generate a path to the domain gateway. 

Les Mikesell
  les@chinet.chi.il.us