🚀 go-pugleaf

My original contention:
>   2.  A message passing through your domain on its way to my domain
>       should be left alone, without ANY modifications to the message
>       AT ALL except for the envelope.

According to karl_kleinpaste@cis.ohio-state.edu:
>I _can't_ send
>	MAIL FROM:<tct!chip>
>in SMTP because it lacks "@right.hand.side" as required by the RFCs.
>
>I _can't_ send
>	From: chip@tct.uucp
>in the headers.  "uucp" is not a valid top-level domain.  Similarly,
>	From: tct!chip
>is insufficient due to no "@right.hand.side."

Okay.  I concede that Karl is right for the example he gives.

Let me put forth two more examples, and see what would happen.

1. Let us suppose that the hypothetical machine "tct" with UUCP
connection to "osu-cis" has just been registered under the domain
TCT.COM.  (I hope to do so shortly.)  In that case, my hypothetical
message will arrive at osu-cis with the envelope:
	From tct!chip
but the header will be valid RFC822:
	From: chip@tct.com
Will this header be rewritten into a bang path just because the mail
came in from UUCP?  I expect that it won't, since it's already RFC822.

2.  (This is the example that sparked my original suggestion.)  If
mail from BAR.COM is being delivered to TCT.COM via UUCP from osu-cis,
will the headers:
	From: foo@bar.com
	To: chip@tct.com
be rewritten into bang paths just because my site's transport of
choice is UUCP?  This munging is *not* necessary.  It is, in my
opinion, rude to mung headers of UUCP sites which are cooperative
enough to register with the DNS and comply with RFC822.
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
"Please don't send me any more of yer scandalous email, Mr. Salzenberg..."
		-- Bruce Becker