Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!news.cs.indiana.edu!maytag!xenitec!iguana!merce
From: merce@iguana.uucp (Jim Mercer)
Newsgroups: comp.sys.3b1
Subject: Re: BITFTP
Keywords: bitftp ftp 3b1
Message-ID: <1991Apr26.023037.20610@iguana.uucp>
Date: 26 Apr 91 02:30:37 GMT
Article-I.D.: iguana.1991Apr26.023037.20610
References: <91@morwyn.UUCP>
Organization: Ed (the iguana) Memorial Society
Lines: 33

In article <91@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes:
>For those of you who use BITFTP to get your files to the 3b1:  I'm curious
>about something.  I never really had a problem using BITFTP when I was 
>getting mail sent to a machine that was directly connected to UUNET... but
>it seems that when I involve another path with 2 more machines, BITFTP won't
>send the files to me... and BITFTP won't respond to the command HELP either,
>so I had no choice but to post to the net.  Anyone have any ideas as to why
>this is a problem?  Is there a way to specify the path that the file(s) is/are
>to be sent to?

there are a number of systems that are actively trashing bitftp requests and
replies.

this is because BITFTP is perceived to be a not a "good thing".

i happen to agree.

listservers limit the flow of requests, bitftp just spews forth.

the systems at work have been swamped twice, resulting in overflowing
filesystems.  in the first instance, someone ordered an 80 Meg VMS archive.

BITFTP, as i understand it was set up to facilitate file transfers between
the internet and BITNET.  its use has since propigated as widely as users
of distantly connected PCBOARD BBS systems.

BITFTP is a significant toll on uucpNET (ie USENET less internet).

at least, that's my opinion.

-- 
[ Jim Mercer   work: jim@lsuc.on.ca  home: merce@iguana.uucp  +1 519 570-3467 ]
[              "Anarchists Unite!" - seen spray painted on a wall             ]