Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!decwrl!uunet!coplex!dean
From: dean@coplex.uucp (Dean Brooks)
Newsgroups: comp.mail.misc
Subject: Re: BITFTP grief! (UUNET email-ftp?)
Message-ID: <1991May23.053628.17360@coplex.uucp>
Date: 23 May 91 05:36:28 GMT
References: <1991May15.042146.29800@iguana.uucp> <81678@bu.edu> <4068@island.COM> <1991May22.081251.1026@uunet.uu.net>
Distribution: na
Organization: Copper Electronics, Inc.
Lines: 29

asp@uunet.uu.net (Andrew Partan) writes:

>If someone can write some software that can distinguish between
>	customer!customer-node!user
>and
>	customer!non-customer-node!user
>for all customers w/o us having to keep a database of interior customer
>nodes, then we will consider running it.

Solve the problem not by determining reply paths and all that garbage.
Instead, arrange for direct uucp to the receiving node.  Perhaps not
as convenient for a secondhand customer node, but any site connected
to uunet (as a customer) will be able to direct uucp of responses.

By theory, this is the correct solution.  UUCP was devised for file
transfers.  Email was designed for textual data.  

This would also open up the possibility of a 1-900 service for non-customers.
Basically, they would mail the request, and anon uucp the source via
anon login (on the 1-900 number).  When the FTP'd software is available
for download, send mail in response notifying so.  If after 48 hours
the software is not received, trash it.

  This may be a little harder to do, but certainly profitable... (-8

--
dean@coplex.uucp (Dean Brooks)
Copper Electronics, Inc.
Louisville, Kentucky