Xref: utzoo comp.mail.misc:5438 comp.mail.uucp:6508 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!swrinde!ucsd!brian From: brian@ucsd.Edu (Brian Kantor) Newsgroups: comp.mail.misc,comp.mail.uucp Subject: Re: BITFTP grief! Message-ID: <34032@ucsd.Edu> Date: 16 May 91 16:13:47 GMT References: <81678@bu.edu> <1705@aupair.cs.athabascau.ca> Followup-To: comp.mail.misc Distribution: na Organization: The Avant-Garde of the Now, Ltd. Lines: 16 I believe we're doing it the right way; I have (under construction) a mail-based archive server which not only limits volume, but will audit the address requesting the data. The qualifications are that we will send a large file in response to a request from someone if their return address is 1 hop from us (i.e., a direct connection) 1 hop from uunet (i.e., requester picks up the tab) on the internet everyone else gets a 'sorry charlie' response for files over the limit, which I'm currently inclined to make around a few Kb, like three or four. When we have it running and debugged, the server code will be available for anonymous ftp. Don't hold your breath. - Brian