Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!emory!hubcap!ncrcae!ncr-sd!sceard!mrm
From: mrm@sceard.Sceard.COM (M.R.Murphy)
Newsgroups: comp.mail.misc
Subject: Re: Which headers may Sendmail re-write?
Message-ID: <1990Dec19.154652.11573@sceard.Sceard.COM>
Date: 19 Dec 90 15:46:52 GMT
References: <1990Dec16.203543.22769@chinet.chi.il.us> <1990Dec17.183615.3887@mp.cs.niu.edu> <1990Dec18.071226.20809@chinet.chi.il.us> <1990Dec18.155353.5024@mp.cs.niu.edu>
Reply-To: mrm@Sceard.COM (M.R.Murphy)
Organization: Sceard Systems, Inc.  San Marcos, CA  92069
Lines: 21

In article <1990Dec18.155353.5024@mp.cs.niu.edu> rickert@mp.cs.niu.edu (Neil Rickert) writes:
[...]
>  I expect the internet -> UUCP gateway to transform the address to
>'site!user' if the gateway happens to be 'domain', and to transform it to
>'domain!site!user' (or perhaps 'gateway!domain!site!user') otherwise.  Most
>Internet to UUCP gateways do this, Chip Salzenberg to the contrary
>notwithstanding.  In that case prepending another 'node!' by a site along the
>way doesn't totally massacre the address.

Prepend node! to the "From ", not to the "From: ". Don't mung valid RFC822
addresses. Bounce invalid RFC822 addresses if you feel like it. I think that it
is a service and a long term favor to do so. Or let the site that doesn't
understand the address bounce the message. Don't rewrite RFC822 addresses based
on transport. That way prepending 'node!' doesn't massacre the address at all,
since it isn't prepended.

If it ends up being a real problem, and the communication is life or death, then
there is always the telephone, which can be used to communicate to set up a
direct mail connection :-)
-- 
Mike Murphy  mrm@Sceard.COM  ucsd!sceard!mrm  +1 619 598 5874