Conference hydra::amiga_v1

    There's no "cd" command.  You must include the full directory path in
    each dir or get command, i.e.
    	dir /amiga/f6
    
    Also, watch out... many times you don't need the beginning slash.
    
    FTPMAIL will tell you about its commands if you send a message
    containing the line 
    	help

    
    	Thanks for the pointer here is the latest response.:-
    
    
    
We have entered the following request into our job queue:
 
	reply [email protected]
	connect grind.isca.uiowa.edu anonymous ftpmail/[email protected]
	dir /amiga
	dir amiga
	ls -r /amiga
	ls -l /amiga
 
You should expect the results to be mailed to you within a day or so.
This is done to give first-class mail priority over FTPMAIL traffic.
 
Note that the "reply" or "answer" command in your mailer will not work
for this message or any other mail you receive from FTPMAIL.  To send
requests to FTPMAIL, send an original mail message, not a reply.
 
  -- Ftpmail Submission Transcript --
<<< reply [email protected]
>>> OK, will reply to <[email protected]>
<<< connect grind.isca.uiowa.edu
>>> Connect to grind.isca.uiowa.edu as anonymous with ftpmail/[email protected]
<<< ascii
>>> Grab files in "ascii" mode
<<< dir /amiga
>>> list directory /amiga
<<< dir amiga
>>> list directory amiga
<<< ls -r /amiga
>>> list directory -r /amiga
<<< ls -l /amiga
>>> list directory -l /amiga
<<< quit
>>> Done - rest of message will be ignored
>>> checking security of host `grind.isca.uiowa.edu'
>>> host `grind.isca.uiowa.edu' is ok
  -- End Of Ftpmail Transcript --
 
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by mts-gw.pa.dec.com; id AA07956; Wed, 24 Jul 91 08:05:59 -0700
From: nobody (ftpmail daemon on mts-gw.pa.dec.com)
To: arrods::goldstein
Subject: your ftpmail request has been received
    

    
    Here is my lastest answer from NOBODY::
    
    
Orig message-id: <[email protected]>
Orig from: Steve Goldstein 071-412-5416 DTN 847-5416 24-Jul-1991 1607 <[email protected]>
Orig date: Wed, 24 Jul 91 08:05:50 PDT
 
>>> open grind.isca.uiowa.edu
Connected to grind.isca.uiowa.edu.
220-Iowa Student Computer Assn  HP/Apollo BBS FTP server ready.
220-
220-This is a test FTP server.  Comments to [email protected]
220-Try 'ls -l' for descriptions of files.
220-
220-You can also telnet to the ISCA BBS (grind.isca.uiowa.edu login iscabbs)
220 The BBS supports FTP as a download protocol.
>>> user anonymous ftpmail/[email protected]
331 Guest login ok, send ident as password.
230 Guest login ok, access restrictions apply.
>>> ls "-r /amiga" /tmp/ftpmail9274.file.dirls
200 PORT command successful.
150 Opening data connection for /bbs/bin/ls (16.1.240.16,1167) (0 bytes).
226 Transfer complete.
>>> ls "-l /amiga" /tmp/ftpmail9274.file.dirls
200 PORT command successful.
150 Opening data connection for /bbs/bin/ls (16.1.240.16,1169) (0 bytes).
226 Transfer complete.
>>> dir "/amiga" /tmp/ftpmail9274.file.dirls
200 PORT command successful.
150 Opening data connection for /bbs/bin/ls (16.1.240.16,1171) (0 bytes).
226 Transfer complete.
>>> dir "amiga" /tmp/ftpmail9274.file.dirls
200 PORT command successful.
150 Opening data connection for /bbs/bin/ls (16.1.240.16,1172) (0 bytes).
226 Transfer complete.
 
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by mts-gw.pa.dec.com; id AA09278; Wed, 24 Jul 91 08:30:02 -0700
From: ftpmail server on mts-gw.pa.dec.com <nobody>
To: arrods::goldstein
Subject: results of your request

    This is a problem that people using interactive FTP don't have, sigh...
    
    Generally when someone posts to Usenet saying to FTP a file from a
    certain site, only about half the time does the author spell out the
    whole directory path _and_ get it correct.  The person doing the file
    transfer session has to figure out where he is in the Unix directory
    tree and then navigate from there.  In interactive mode this requires
    only a few DIR and CD commands to figure things out.
    
    If the path you've gotten does not work, then my advice is to get ready
    to send a string of messages through FTPMAIL.  The first is just a
    "dir" of the default directory.  This will usually show that there is a
    "pub" or "ftp" or, with luck, even an "amiga" subdirectory.  Just keep
    heading in what you think is the right direction through a(n
    excruciating) series of messages to FTPMAIL until you locate the right
    directory.  If you can't locate the right place, do a directory of the
    root directory "/", "/pub" or "/ftp"...
    
    Many public FTP sites also keep a README file or a comprehensive file
    list called something like "ls-lR.Z" in a top level directory.
    
    Good luck!
    
    Wes

   In case anyone is interested, a few ftp sites keep current listings
   of all sites on-line, for example.. have a look in

   Host: csus.edu
   Directory: /pub/ftpsites/

   You should find fairly recent listings of most known ftp sites.
   Each listing is named after the site itself.

   By the way, I havent been able to get through to nic.funet.fi, is it
   still around? I vaguely remember hearing that you can get things
   from there using a mail server. Anyone know how?

   Dave

    
    I don't know the specifics on the Finnish node, but I remember
    skimming over some info on it in the IBMPC and/or the SHAREWARE
    conference(s), so you might look there.
    
    

 Okay, I finnally got the syntax right to pull files of the FTP sights in
 UUENCODE format.
  They come across in parts.
 I take it I extract/noheader the mail messages, than append them to each
 other, then run UUdecode on the final file.
 This usually results in an FTPfile.uu.
 Can I simply rename this file and be all set?
 Or is there more too it?

								Thanx;
									Ed

   Re: -.1

> Okay, I finnally got the syntax right to pull files of the FTP sights in
> UUENCODE format.
>  They come across in parts.
> I take it I extract/noheader the mail messages, than append them to each
> other, then run UUdecode on the final file.
> This usually results in an FTPfile.uu.
> Can I simply rename this file and be all set?
> Or is there more too it?

   To make it just a tad easier, use extract/nohead/append in mail so you don't
   have to use the vms append command. (Just remember to do 'em in the right
   order). There's an archive called myuud.lzh somewhere on the net (I think 
   it's on crista, but can't recall where I got it from) that ignores all the 
   internet headers and trailers when uudecoding them. And yes, no problem 
   in renaming the file.

   -Dom
   

re .7

> I take it I extract/noheader the mail messages, than append them to each
> other, then run UUdecode on the final file.
> This usually results in an FTPfile.uu.

If you look at the file before you UUdecode it you should see aline like:

BEGIN 600 FILENAME.EXT

This will be the filename UUdecode creates when it is run.  Usually this is the
right name.  Are you saying your FTP files are all named *.uu?

> Okay, I finnally got the syntax right to pull files of the FTP sights in
> UUENCODE format.

Can you post an example?  I lost track of how since the mailserver changed.

Thanks,

...Ed

    re: .8 extract/nohead/append
    
    This does NOT work because the mail messages also have "trailer"
    information.  There are actually a few ways to automate file
    reconstituting.  A utility called "uustrip" will remove all the
    non-uuencoded lines in a file, so you can just extract/append the
    sections in order, run this program, and get a uuencoded file.  There's
    also a .COM file somewhere -- you put all the file parts in a mail
    folder by themselves, any order, exit mail and run the script.  You
    wind up with a reconstituted, decoded file at the end.
    
    Look around old notes for more info, maybe even earlier in this note.
    
    re: .7 files named "ftpmail.uu"
    
    Paul Vixie, author of FTPMAIL, got many complaints about file naming in
    the original versions.  Files would be transferred with the full Unix
    pathname in the uuencode header, which VMS uudecode usually couldn't
    parse.  So he just made all the uuencode headers say "ftpmail.uu".  YOu
    can change it back (manually) to the original filename with an editor
    before decoding or $RENAME after decoding.
    
    Wes

    re: .10
    
>    This does NOT work because the mail messages also have "trailer"
>    information.  There are actually a few ways to automate file
>    reconstituting.  

    Wes,

    Perhaps with the standard uudecode the trailers get in the way. With
    the version I've got, I never have to worry about editing out the
    trailers. Since I couldn't find it on eot::, and since I know I found
    a pointer to it in this notesfile (can't recall who the author is), I 
    just copied a version to eot::amiga:[upload]myuud.lzh. It skips over all 
    the header and trailer junk so you don't have to edit the file. I've been
    using it for a number of weeks now and it most definitely works.

    -Dom

    Here's the command procedure. It uses UUSTRIP but with a few minor
    changes you could pull that out and use the new improved UUD that
    ignores the internet crap. All you need to do is to move the parts
    into a folder and type EXTRACT {foldername} {filename}.
    
    Cheers,
    
    				Jamie.
    
    
$!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
$! EXTRACT.COM - a routine to assemble ftpmail parts.
$! Written 15th May 1991 by Jamie Badman, Service Industry Engineering,
$!			    Digital, Reading, England.
$!
$! Requires UUD.EXE and UUSTRIP.EXE. To run, from DCL type :
$! @EXTRACT mail_foldername required.filename
$!
$
$open/write temp 'p1'_temp.com
$write temp "define sys$output ''p1'_mail_list.tmp"
$write temp "$mail"
$write temp "select ''p1'"
$write temp "dir"
$write temp "quit"
$write temp "$deassign sys$output"
$write temp "exit"
$close temp
$@'p1'_temp
$open temp 'p1'_mail_list.tmp
$open/write temp2 'p1'_mail_list2.tmp
$next_line:
$read/end_of_file=sort_things temp temp_line
$if f$locate("part",temp_line).eqs.f$length(temp_line) then goto next_line
$if f$extract(f$locate("part",temp_line)+6,1,temp_line).nes." " then goto write_line
$part_pos=f$locate("part",temp_line)
$temp_line = f$extract(0,part_pos+5,temp_line)+"0"+f$extract(part_pos+5,f$length(temp_line)-part_pos+8,temp_line)
$write_line:
$write temp2 temp_line
$goto next_line
$sort_things:
$close temp
$close temp2
$open temp 'p1'_mail_list2.tmp
$get_next_line:
$read temp temp_line
$if f$locate("part",temp_line).eqs.f$length(temp_line) then goto get_next_line
$close temp
$key_pos=f$locate("part",temp_line)+6
$sort/key=(position:'key_pos',size:2,decimal) 'p1'_mail_list2.tmp 'p1'_sort_mail.tmp
$type 'p1'_sort_mail.tmp
$open/write temp 'p1'_temp_extract.com
$write temp "$mail"
$write temp "select ''p1'"
$open/read temp2 'p1'_sort_mail.tmp
$next_sorted:
$read/end_of_file=go_fer_it temp2 temp_line
$mail_no=f$extract(0,5,temp_line)
$write temp "''mail_no'"
$write temp "extract/append/nohead ''p2'"
$goto next_sorted
$go_fer_it:
$!write temp "del/all"
$write temp "exit"
$close temp
$close temp2
$@'p1'_temp_extract
$
$uus=="$heavy_user4:[jamie.utilities.packers]uustrip"
$uud=="$heavy_user4:[jamie.utilities.packers]uud"
$define sys$output 'p1'_uutemp.uue
$uus 'p2'
$deassign sys$output
$search 'p1'_uutemp.uue begin
$uud 'p1'_uutemp.uue
$delete 'p1'_sort_mail.tmp;*
$delete 'p1'_temp_extract.com;*
$delete 'p1'_temp.com;*
$delete 'p1'_mail_list.tmp;*
$delete 'p1'_mail_list2.tmp;*
$delete 'p1'_uutemp.uue;*
$delete 'p2';*
$copy ftpmail.uu 'p2'
$set prot=(w:rwe) 'p2'
$delete ftpmail.uu;*
$exit

Example follows for successful FTP of files, Note 2 of the files are binary
    transfer, the other is ascii.
    The whole thing is mailed to DECWRL::FTPMAIL
    
    
    _________________________________________________________________________
    
connect ab20.larc.nasa.gov
uuencode
binary
get /amiga/games/amos/amoner01.dms amoner01.dms
get /amiga/games/amos/scroll2.amos scroll2.amos
ascii
get /amiga/games/amos/scroll2.txt
quit
$exit

I have a program called uucat that I snarfed off the net awhil back that
performs a uudecode while ignoring any header garbage between file segments.
You can just extract/append all the pieces from mail, then $uucat file.ext
and you have a uudecoded file. If anyone is interested in it (I also have the
sources), I can upload it to EOT:

Frank

    re: last
    
     Yes please do...
    								ED
    

OK, I have uploaded uucat.c and uucat.exe to EOT::AMIGA:[UPLOAD]. I also
uploaded the following .readme.

-------------------------------------------------------------------------

UUCAT.EXE is a VMS utility to concatinate a bunch of uuencoded file
segments received via FTPMAIL and uudecode them ignoring any header
or trailer information as it goes.

You must install it as a foreign command, ie:

$ uucat :== $disk:[user]uucat.exe

The command syntax is:

$ uucat file1 file2 file3 ... filen

where file1 file2 etc are segments of the file to be concatinated and
uudecoded. The segments must be listed in order! You of course can give
it a single file to be uudecoded as well. The resultant file is a uudecoded
stream-lf file already for file transfer etc!

Enjoy,
AMIGA::RIES, Frank