Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site cbosgd.UUCP Path: utzoo!linus!philabs!seismo!harpo!floyd!vax135!cornell!uw-beaver!tektronix!ucbcad!ucbvax!cbosgd!mark From: mark@cbosgd.UUCP Newsgroups: net.wanted,net.mail Subject: Re: mail path needed to [Ss]hasta Message-ID: <60@cbosgd.UUCP> Date: Thu, 23-Jun-83 23:55:06 EDT Article-I.D.: cbosgd.60 Posted: Thu Jun 23 23:55:06 1983 Date-Received: Mon, 27-Jun-83 20:42:40 EDT References: <305@hou5f.UUCP> Organization: Bell Labs, Columbus Lines: 18 Shasta is an interesting case. The management there insists that their right to their upper case "S" is more important than being able to exchange mail with other sites. This is complicated by the lower case tradition on UUCP and a misfeature of 4.1BSD's delivermail program which translates upper case to lower case. In your case, the translation from Shasta to shasta happens because you routed your mail through a 4.1BSD machine (floyd). Try routing through ihnp4, for example. I also think (but am not sure) that Shasta can be accessed from the ARPANET with a syntax such as user%Shasta@Sumex.ARPA using Sumex as a gateway and % as a fake @ sign. I am unsure of the case sensitive situation here - RFC 822 claims it shouldn't matter in host names. Other machines have links to shasta (lower case) - eagle comes to mind.