Subj : Routing files
To   : Steve Quarrella
From : Mike Luther
Date : Fri Dec 07 2001 12:27 pm

Ah yes .. the Elephino DOES exist Steve!

 SQ> Do you _route_ files, though? :-)  Processing files is
 SQ> one thing.  Receiving a file from 1:3830/9.9 and 
 SQ> passing it onto 1:3830/9.10 is the objective I'm 
 SQ> trying to fulfill.

I just tried it and it works!  I sent an Email from the Internet side of 
1:117/3001 to 1:117/3000 with the latest NORMAN OS2_UPD/ZIP file attached to 
it.  Of course, that normally would have been crashed to 1:117/3000 direct.

But after it was all set up, I went into BINK and re-addressed the whole thing 
to 1:117/100 just to see what happened!

Poof .. It went intstead to 1:117/100, the Intermail and FE system.  Off it 
went to 1:117/3000 complete with file attach.

Here is a partial of the the ROUTE.FE file:

 forward-to  1:117/*
 forward-for 1:117/*
 Route-to    1:106/1 1:* 2:* 3:* 4:* 5:* 6:* 7:*
 no-route    1:117/*
 Route-to    1:117/0    1:117/0.*
 Route-to    1:117/100  1:117/100.*
 Route-to    1:117/110  1:117/110.*
 ...
 Route-to    1:117/325  1:117/325.*
 Route-to    1:117/3001 1:117/600.*
 Route-to    1:117/3000 1:117/3000.*
 Route-to    1:117/3001 1:117/3001.*

The part that does it, as far as I know, is the, I think, undocumented pair of 
lines at the top of it.  IIRC, it isn't at all clear in the documentation how 
you get this to work, but that does it.

In this case the HUB moves all the stuff for 1:117/600 to 3001, which forwards 
it by TELNET to Ferris at 1:117/600 ...


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)

.