At 4:44 AM 5/7/94 -0400, wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510 wrote:
Jim Nalbandian, who's recently been posting to cypherpunks, has a signature line that contains a couple of *severely* non-portable addresses; I have no way to tell whether my email to him worked on the netcomish address. Don't know about his spelling errors, but his addressing errors distinctly *are* international.... ^^^^^^^^^^ ^^^^^ ^^^^^^^^^^^^^ I don't understand what you mean by the above.
I think the correct address would be just jim%lassie@netcom.com, which is a UUCP connection to netcom. Connected to netcomsv. Escape character is '^]'. 220-netcomsv.netcom.com Sendmail 8.6.4/SMI-4.1 ready at Sat, 7 May 1994 03:05:00 220 ESMTP spoken here 250 <test@netcomsv.netcom.com> expn netcomsv!nonexisting!addr #test a bogus addr to see error message 501 netcomsv!nonexisting!addr... nonexisting is an unknown UUCP connection expn netcomsv!lassie!jim%lassie@netcom.com 250 <jim%lassie@netcomsv.netcom.com>
I got an interesting bouncegram from Namibia when I tried using the N7SZS@K7BUC.AZ.US.NA address - it's some sort of Amateur packet radio address, which has a syntax similar to Internet addresses but rips off the .na namespace
The Hams have implemented TCP/IP over the air, using the airwaves as a sort of ethernet (albiet slowly). Works quite well. However, these addresses are not internet addresses, and the Ham network has very important FCC-mandated restrictions on message content. (No encrypting, no commercial traffic, no explicit or oobscene stuff). Don't confuse this with the UUCP city.state.us domains. If you see a user or site name such as [KN]*[1-9]* (e.g. N7SZS or K7BUC), recognize that as a ham call sign and assume that it is a tcp/ip packet network. -- Rusty Hodge <rustman@netcom.com>