Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site decuac.UUCP
Path: utzoo!watmath!clyde!cbosgd!decuac!avolio
From: avolio@decuac.UUCP (Frederick M. Avolio)
Newsgroups: net.mail.headers
Subject: Re: Mail Header Summary Document...
Message-ID: <655@decuac.UUCP>
Date: Sat, 19-Oct-85 08:33:33 EDT
Article-I.D.: decuac.655
Posted: Sat Oct 19 08:33:33 1985
Date-Received: Sun, 20-Oct-85 06:09:54 EDT
References: <50000001@hpcnof.UUCP> <841@vortex.UUCP> <2297@ukma.UUCP>
Organization: ULTRIX Applications Center, MD
Lines: 19

In article <2297@ukma.UUCP>, david@ukma.UUCP (David Herron, NPR Lover) writes:
> But --Lauren--!!   What if you're an intermediate site and the message
> is leaving the domain?  For instance, when seismo gateways uucp mail
> ...

I wrote a long note to Dave Taylor with my comments on his document.  In it
I agree with Lauren with David Herron's exception -- no one should think
they are smart enough (as in smart mailer) to change the From: field.
EXCEPT if you are a gateway and need to protect one side or the
other from certain forms onthe From: line.  So, an APRA <--> UUCP gateway
should try to make the From: line be in "user@host.dom" format if that is
what is needed.  An ENET <--> UUCP gateway, such as decuac, should change
addresses in the form "node::user" and make it "user@node.DEC" to 1) get rid
of colons in addresses which bother many sites and 2) make the address
look like the   addressing form adopted by the UUCP community's common use
of ".DEC" to indicate DEC's ENET.  (ANd decuac does this with mail passing
though us from the Enet.)

Fred.