Steve ..

I've used Fastecho with FrontDoor for longer than I
can remember, and FD's ROUTE.FD has always handled
routing of files.

Now, I'm using Fastecho on a Binkley-compatible
mailer, Radius, and would like to route files between
my direct downlinks. I'm not seeing anything in the
documentation, so I've either missed something, or
this isn't doable. Anybody got any pointers? Thanks
in advance.

The 1:117/100 HUB uses FastEcho with Intermail and MAX. But it also uses ALLFIX to handle the file deal as best I understand the issue.

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

Mike @ 1:117/3001

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

I've used Fastecho with FrontDoor for longer than I can remember, and FD's ROUTE.FD has always handled routing of files.

Now, I'm using Fastecho on a Binkley-compatible mailer, Radius, and would like to route files between my direct downlinks. I'm not seeing anything in the documentation, so I've either missed something, or this isn't doable. Anybody got any pointers? Thanks in advance.

---
* Origin: Fnord (1:393/9005)

My you pose such interesting questions ..

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

Like the cross between the Elephant and the Rhinocerous, .... Elephino?

Tell you what I will do! I will fire a file attach from 3001 to 3000, and then
change the calling address to 1:117/100 and see if it forwards it!

In theory it is set to forward files! We shall see.

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

Mike @ 1:117/3001

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

Ah yes .. the Elephino DOES exist Steve!

Do you _route_ files, though? :-) Processing files is
one thing. Receiving a file from 1:3830/9.9 and
passing it onto 1:3830/9.10 is the objective I'm
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)

The 1:117/100 HUB uses FastEcho with Intermail and MAX. But
it also uses ALLFIX to handle the file deal as best I
understand the issue.

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

---
* Origin: Fnord (1:393/9005)

Hi! Steve,

On 06 Dec 01 18:59, Steve Quarrella wrote to All:

I've used Fastecho with FrontDoor for longer than I can
remember, and FD's ROUTE.FD has always handled routing of
files.
Now, I'm using Fastecho on a Binkley-compatible mailer,
Radius, and would like to route files between my direct
downlinks. I'm not seeing anything in the documentation, so
I've either missed something, or this isn't doable. Anybody
got any pointers? Thanks in advance.

I used various forms of FroDo for about 4 years with FastEcho
(FE). All mail _routing_ was handled via a FE route file,

Move your underscores a bit <heh>: _Mail_ routing. In my case, I have a similar situation. I've used (and continue to use) FD here on 1:393/9005 for years, but file routing is a function of my ROUTE.FD. Now that I'm using a Binkley-style outbound with Radius, I continue to do the ROUTE.FE thing, similar to what you do, but files themselves just sit in my inbound and go nowhere. <scratching head>

So what is ol' Steve doin' wrong here?

---
* Origin: Fnord (1:393/9005)

Hi! Steve,

On 06 Dec 01 18:59, Steve Quarrella wrote to All:

I've used Fastecho with FrontDoor for longer than I can remember, and FD's ROUTE.FD has always handled routing of files.
Now, I'm using Fastecho on a Binkley-compatible mailer, Radius, and
would like to route files between my direct downlinks. I'm not
seeing anything in the documentation, so I've either missed
something, or this isn't doable. Anybody got any pointers? Thanks
in advance.

I used various forms of FroDo for about 4 years with FastEcho (FE). All mail _routing_ was handled via a FE route file, using the route file's name as an argument when packing in-transit netmail via a "FastEcho.Exe PACK -P -RRouteNet.Fe" command. In late '98 I switched over to using Binkley-style mailers (Binkley & BinkD), without blinking an eyelid. The FE route file still
did everything for me; mail & files.

The FE route file need only be a subset of what your Route.Fd consisted of. Mine looks like this:

----- ROUTENET.FE begins -----
; ---------------------------------------------------------------------
; ROUTENET.FE file for individual node for Fastecho.
; ---------------------------------------------------------------------
; Last revised: 2001-09-22

; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FORWARD-TO 1:* 2:* 3:* 4:* 5:* 6:* 173:*
FORWARD-FOR MYPOINTS 3:640/*.* 173:6177/*

ROUTE-TO 3:640/954.0 1:* 2:* 3:* 4:* 5:* 6:*
EXCEPT 1:154/* 3:633/262.0 3:640/379.* MYPOINTS 3:640/387.*

DIRECT MYPOINTS 3:633/262.0

ROUTE-TO 3:640/384.5 3:640/379.*
ROUTE-TO 3:640/387.0 3:640/387.*

; Zone 1, Net 154 nodes... node #15 runs iRex (IBN)...
ROUTE-TO 1:154/15.0 1:154/*

; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ROUTE-TO 173:6139/0 173:*
DIRECT 173:6177/*

----- ROUTENET.FE ends -----

Did that help any, Steve?

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.5
* Origin: SysOps just like to watch. (ZMH only) (3:640/384)

Hi! Steve,

On 07 Dec 01 09:32, Steve Quarrella wrote to Paul Quinn:

I used various forms of FroDo for about 4 years with FastEcho
(FE). All mail _routing_ was handled via a FE route file,

Move your underscores a bit <heh>: _Mail_ routing. In my case, I
have a similar situation. I've used (and continue to use) FD here on 1:393/9005 for years, but file routing is a function of my ROUTE.FD.

Mmm... maybe I have been using Binkley-style outbound (BSO) for too long, already. ;-)

In a BSO situation, your tosser is the mail & files router. A true Binkley system has no equivalent to a Route.Fd file... unfortunately.

Now that I'm using a Binkley-style outbound with Radius, I continue
to do the ROUTE.FE thing, similar to what you do, but files
themselves just sit in my inbound and go nowhere. <scratching head>

It's conceivable that FE could leave the files in the inbound and just reference them, there, in the .FLO file(s).<shrug> It still doesn't work, huh?

BTW, I gave up on FroDo at about the time when JoHo introduced the 2.2x version
with static outbound (queues?). I just never investigated what that was all about. So, if you're trying to shoehorn a FroDo static outbound with a BSO with Radius, I can't assist.

So what is ol' Steve doin' wrong here?

Forget FroDo... utterly. Dump it & go BSO only. :)

Are you using different FE config files between the two systems? I don't wanna
tell you how to suck the eggs, but you have told FE to use a 'Binkley/Xenia' mailer in FeSetup, now that you're toss/pack-ing mail to Radius' outbound?

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.5
* Origin: He's got a magnet! Everybody stand back! (ZMH only) (3:640/384)

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.

You know, I just noticed that the forward-to and forward-for lines in my routing file are respectively commented out and missing. I may owe you and Paul Q an apology for being premature. I don't really want to mess with this remotely, as I'm not in front of the system to see if something stops working, but I'll give this a look the next time I'm in front of 3830/9 (hopefully Wednesday...I owe Jim some nice bottles of stout. :).

Here is a partial of the the ROUTE.FE file:
forward-to 1:117/*
forward-for 1:117/*
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

It has to be, as I have plenty of the other goods in place.

---
* Origin: Fnord (1:393/9005)

Mmm... maybe I have been using Binkley-style outbound (BSO)
for too long, already. ;-)

You and Mike are both pushing me in the right direction, see previous. THAT is
what counts. :-)

BTW, I gave up on FroDo at about the time when JoHo
introduced the 2.2x version with static outbound (queues?).

Static Queue, right. Being a long-time FD user, well, I poked the STQ with a point-ad stick for awhile, but it didn't bite me, and today, I use it just fine. It basically saves you from having a lot of file-attach messages in your
netmail folder. As a mail mover and shaker, that cuts down on the rescan times
I see.

I just never investigated what that was all about. So, if
you're trying to shoehorn a FroDo static outbound with a BSO
with Radius, I can't assist.

Not at all. 1:393/9005 is the FD system that has existed for about ten years now. 1:3830/9, run by the same guy, was built from the ground up, and uses Radius and Fastecho with BSO. Forget 1:393/9005, as I referenced that only to display my history and knowledge with FD. There's nothing about FD to be found
on 1:3830/9, the system in question.

Forget FroDo... utterly. Dump it & go BSO only. :)

Given that I'm one of the more vocal beta testers of FrontDoor, that's probably
not going to happen. <heh>

systems? I don't wanna tell you how to suck the eggs, but
you have told FE to use a 'Binkley/Xenia' mailer in FeSetup,
now that you're toss/pack-ing mail to Radius' outbound?

Of course, and it works well. Let me play with those forward key words again, and see what comes up. I'll keep you guys advised, and thanks for your help.

---
* Origin: Fnord (1:393/9005)

Hi! Mike,

On 07 Dec 01 20:27, Mike Luther wrote to Steve Quarrella:

Here is a partial of the the ROUTE.FE file:
forward-to 1:117/*
forward-for 1:117/*

[ ...trim... ]

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.

They are mentioned in the doc file, Mike. See pages 120/121. I agree that some bits of the doc reads like pidgin English sometimes, though. :)

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.5
* Origin: As Socrates once said, "I drank WHAT?" (ZMH only) (3:640/384)

Hi! Steve,

On 09 Dec 01 18:14, Steve Quarrella wrote to Paul Quinn:

you have told FE to use a 'Binkley/Xenia' mailer in FeSetup,
now that you're toss/pack-ing mail to Radius' outbound?

Of course, and it works well. Let me play with those forward key
words again, and see what comes up. I'll keep you guys advised, and thanks for your help.

Cool, mate. Here's another thought for you: make sure you use the -P parameter
on the FE PACK command-line.

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.5
* Origin: SysOps just like to watch. (ZMH only) (3:640/384)

Hello Steve,

Thursday December 06 2001 18:59, Steve Quarrella wrote to All:

Now, I'm using Fastecho on a Binkley-compatible mailer, Radius, and
would like to route files between my direct downlinks. I'm not seeing anything in the documentation, so I've either missed something, or
this isn't doable. Anybody got any pointers? Thanks in advance.

except for Xenia and Mcmail I haven't seen many Binkley style mailers performing routing functions...
But I'd advise to use CFRoute to accomplish this task


o Steven Leeman,
)/\,[_) Sysop SkyNET Bbs
`T7 ]=[ steven@fido.be
... "Ally McFido" (ahem :) Misschien "Ally McMail" :-)))
--- FMail/Win32 1.60
* Origin: Fidonet - Skynet Bbs Belgium (2:292/624.1)

The 1:117/100 HUB uses FastEcho with Intermail and MAX. But
it also uses ALLFIX to handle the file deal as best I
understand the issue.

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

did you ever solve this?

)\/(ark


* Origin: (1:3634/12)

Hello there mark!

06 Jan 02 at 10:06, mark lewis writes to Steve Quarrella:

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

did you ever solve this?

Damn it Mark! That was going to be my question too (just catching up on this thread), I have the same problem but I don't use route.fe just the built in configuration - because route.fe stopped working last time I used it and I just
switched back to the inbuilt routing.
But looking at it I think "the boys" are correct about the route-to & route-for
verbs, unfortunately there is no inbuilt equivelent of those that I know of?

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

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

did you ever solve this?

Not yet, but I still have a few things to try. It's a little harder for me to get to the box lately, and as the room is full of Macintoshes, testing can be difficult. :-)

---
* Origin: Fnord (1:393/9005)

Damn it Mark! That was going to be my question too (just
catching up on this thread), I have the same problem but I
don't use route.fe just the built in configuration - because
route.fe stopped working last time I used it and I just

I think Mike and the rest were onto something with the "forward" verbs in the route file. I just need to put the right combination of verbs and systems together (I don't want everybody routing files through that systems...it'll be hell!).

---
* Origin: Fnord (1:393/9005)

Hello there Steve!

10 Jan 02 at 12:53, Steve Quarrella writes to Barry Blackford:

I think Mike and the rest were onto something with the "forward" verbs in the route file. I just need to put the right combination of verbs and systems together (I don't want everybody routing files through that systems...it'll be hell!).

I just want to hear that it DOES work so I can impliment it here :-)


Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Oh! The File Railroad game! Grin!

I just need to put
the right combination of verbs and systems together (I
don't want everybody routing files through that
systems...it'll be hell!).

Used to be that all railroads running through Texas had to have the name Texas in them! So long ago the Southern Pacific was the Texas and New Orleans (T&NO), the Missouri Pacific was the Houston and Texas Central (H&TC) - more affectionally known as the "Mop."

Even byt the late 1940's all the locomotives and cabooses rolling through College Station here had the T&NO and H&TC still on them in tiny letters, as well as the big parent line names in the big letters on them!

Earlier than that, little lines were all around Houston as well. There was the
Texas Western and Beaumont, which the good folks got to callin the "Toot Whistle and Bump." And there was also the the one that had a deadlock on all the freight shipped around Houston, the pest problem yard and terminal extension Houston and East-West Texas! It was NEVER on time and you could NEVER figure out which carload of stuff was where, when!

So the pet name it became over the routing issue was the:

"Hell Either Way Taken"

Grin ..

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

Mike @ 1:117/3001

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

Barry ..

I just want to hear that it DOES work so I can impliment it here :-)

It works for 1:117/100 but I haven't tried to involve the HUB at 1:116/1 in such an escapade yet. If you want, and can get to the 1:117/100 to try it,you can send me a short file to 1:117/3001, which is in the NodeList via the Houston Hub at 1:116/1. If they route it in, my bet is that I'll get it at 1:117/3001 from the HUB here!

Another way to do this if you can process NetMail and file attach, is to send me a Netmail with a small file attach via 1:116/1 to 1:117/3001, and I'll betcha if it clears Houston, I'll see it all at 1:117/3001.

It's a little more problematical for me to play me (Or, worse, someone else!) to use the HUB in Houston to try this, but a legitimate third party outside my enclave could do this and test it.

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

Mike @ 1:117/3001

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

Hello there Bob!

16 Apr 02 at 21:34, Bob James writes to Barry Blackford:

Day Barry
long time

B' long Bob!

This is what I had when running
call it with
fastecho pack -p -rc:\bbs\fast\route.fe

I had trouble when I used it with route.fe but as ALLFIX didn't complete it's venture into echomail tossing I may have to have another go with it..

hope it helps

Yep, but it was even better to hear from you again :-)

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hi! Bob,

On 16 Apr 02 at 21:34, Bob James wrote to Barry Blackford:

route.fe
;
Route-to 3:640/957 3:640/* 3:713/*

^^^
That probably should be #954, hey Bob. :)

Stuff if I know now it was an old file on the system that at one time worked whom 954 was maybe 957

Cheers,
Paul.

--- BT-W32 2.60XEg6/BinkD-W32 0.9.4
* Origin: =-DING!-= Dinner's Ready! (ZMH only) (3:640/0)

---
* Origin: Phantom Connection Bulletin Board Service (3:712/311)