<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">After Namibia’s independence calls to South Africa remained VERY cheap for a while and only gradually increased. So I dialled Grahamstown with UUPC at first and later managed to have the local University absorb calls to Pretoria from their Olivetti (!) box.<br />
<br />
Then Linux appeared and Taylor/UUCP with long and sliding packets. We then found an early version of smail making gzipping and batching possible which together made this very efficient.<br />
<br />
Once I figured out M4 I could set up sendmail up to do this in 9 lines :-)-O and when we had enough “paying” users to cross the leased lime threshold it took them a week or so to figure out that mails took minutes instead of hours :-)-O<br />
<br />
<br />
I still like (Taylor) UUCP and it might actually be more efficient over satellite phones than doing this over TCP/IP, especially if one could hack up something dropping all attachments and rejecting messages over a certain size to block circumvention :-)-O<br />
<br />
This might actually be helpful in disaster recovery :-)-O<br />
<br />
el</div>
<div name="messageSignatureSection"><br />
Sent from Dr Lisse’s iPad mini 4</div>
<div name="messageReplySection">On 6 Jul 2018, 22:41 +0100, John Levine , wrote:<br />
<blockquote type="cite">In article <CAC20D2Mb0GL0mB9_H_-L5UEoMmYrCjSUmwM6zzELjoqWxOQVzg@mail.gmail.com> you write:<br />
<blockquote type="cite">The UUCPnet grew incredibly fast because it was easy and reasonably cheap<br />
to attach ... but quickly the 'routing problem' emerged. In traditional<br />
UNIX style, UUCP had been design without worrying about some problems --<br />
UUCP was thinking small scale so how mail (packets or whatever got there)<br />
was not an issue. You did your own routing.<br /></blockquote>
<br />
Right. A lot of this involved hiding the phone bills in company overhead budgets,<br />
or carefully figuring out what was a local call. I have a beach house on Long Beach<br />
Island in New Jersey, and careful reading of the first pages of the phone book revealed<br />
that even though the Atlantic City airport was a long way away, quirks of geography<br />
made it a local call, and the uucp node at the FAA tech center at the airport kindly<br />
gave me a uucp feed for the summer.<br />
<br />
<br />
<blockquote type="cite">But with many, thousands of nodes, this was a huge problem.<br /></blockquote>
<br />
<blockquote type="cite">Netnews gets layered on top of UUCP and because of the growth, and the wild<br />
nature, this lack of support for routinr quickly becomes an issue.<br /></blockquote>
<br />
Actually, for netnews it didn't matter since you flooded your news to<br />
all your neighbors and it didn't matter what was multiple hops away.<br />
The mapping project was for e-mail.<br />
<br />
Everyone could use the route info to source route their uucp mail to<br />
anyone else on the map. Considering what a kludge it was, it worked pretty well,<br />
<br />
<br />
R's,<br />
John<br />
_______<br />
internet-history mailing list<br />
internet-history@postel.org<br />
http://mailman.postel.org/mailman/listinfo/internet-history<br />
Contact list-owner@postel.org for assistance.<br /></blockquote>
</div>
</body>
</html>