Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!clout!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.misc
Subject: Re: BITFTP grief!
Message-ID: <1991May17.155134.25876@chinet.chi.il.us>
Date: 17 May 91 15:51:34 GMT
References: <1705@aupair.cs.athabascau.ca> <OCCB4F3@xds13.ferranti.com> <34032@ucsd.Edu>
Distribution: na
Organization: Chinet - Chicago Public Access UNIX
Lines: 20

In article <34032@ucsd.Edu> brian@ucsd.Edu (Brian Kantor) writes:
>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

Hmmm... Are you looking at the From: header or the envelope-from?  Everything
I send through uunet goes through three internal machines via uucp.  One on my
desktop, a local gateway, and a machine in our Washington DC office where
it's a local call to uunet.  The From: line will just have fb.com, which
doesn't tell you much.  Am I going to have to rip out the uucp From_ line
on the from the DC machine to uunet?

Les Mikesell
  les@chinet.chi.il.us