BS>> I saw the problem then a node whitch normally have his
 BS>> mail on Hold here, but his internet was down, so i want
 BS>> to route his mail thru by BOSS, but it "routed" the
 BS>> echomail too..

 BJ> Ah, yes....  that is a "feature" in squish, and 
 BJ> the older mail mashers
 BJ> that squish is based on.  You end up needing seperate runs of squish
 BJ> if you want to seperate netmail and echomail handling.  :(

 BS> All the tossers i've used did use sepperate netmail 
 BS> routing and echomail exporting.

You must be using newer software or software based on something other than
Fido/Fidonet/Confmail, Opus/(optional)Binkley/Ommm, Maximus/Binkley/Squish,
etc.  I know front door and dbridge handle some of this differently for
outbound routing, but I haven't played with those.....

 BS> Then all the bugs is corrected, i would be one of the 
 BS> things, but we should first get the Sqafix source..

Yup.....  Tackle SQAFIX issue first....

 ...
 BJ> Both ends of the transfer scrached our heads
 BJ> over that route.cfg error for a while.....  I forget how I finally
 BJ> stumbled on the solution....  Any way.....

 BS> BTW there is a solution too, you could use a tracker or 
 BS> cfroute, but it should be possible for squish to handle both.

I don't believe cfroute or tracker existed at the time I hit the bug....
...  

 BS>>> Well it's not the point that Binkley shouldn't touch
 BS>>> ILO.. What the problem about route "Normal" to binkp
 BS>>> nodes?

Since nodes are not guarenteed to handle any archived mail if they fly the
MN flag, or just a very old ARC standard if they don't fly the MN flag, I
default to non-archived netmail when sending direct to nodes I haven't
previously made contact with.  And with that, you know my issue with how
Squish handlesNormal, no archive and later route.cfg information.  :(  For
now, I tend to route all out of local net netmail via backbone channels
instead of trying to send via more direct routes.  I'd like to automate
sending more direct, but I don't have the software to do that properly at
this time.....

 BJ> One other probelm with routing "normal" for binkp is the way squish
 BJ> handles normal.  For that reason I don't use normal.  I only use
 BJ> Crash, Hold and Direct for squish's outbound mail packets.

 BS> It makes a arcmail and makes a flowfile with .flo extention?

See above....  Issues are when the mail is not compressed and how Squish
will then reprocess those outbound packets.  :(

 ...
 BS>> If it's ION you got a double points because their phone
 BS>> number _should_ be unpublished.

 BJ> I have two problems with using unpublished.  For ION's using
 BJ> unpublished, the problem becomes that my nodelist processor will
 BJ> substitute the NC's phone number for the POTS mailer, which you don't
 BJ> want dialed.

 BS> Oh i see.. But it's not default in Fastlst, or what you 
 BS> are using as nodelist compiler. Hmm.. i'm not scure 
 BS> about that..

I'd have to look it up, but I believe I am using QNode to produce a version
7 nodelist.  Fastlist used to be shareware, and is why I went with QNode at
the time.  And after fastlist went pd or GNU type license, I haven't seen a
functioning compiled version for running under OS/2 that could use my old
control file info.  Back when this (local) net (1:343) had around 100
nodes, that was an issue, because I have an extensive list of what
exchanges with in my area code(s) (now plural) are local and which are long
distance, have extra charges, or are plain not good to dial (i.e. emergency
numbers, operator, etc.).  These are both (seperate) cost and dial
translation tables for my location, containing over a thousand lines of
information at this point.  Under Unix/Linux it will be easier to convert
(using AWK, Grep and/or PERL) to another format, but it is a hastle to make
such changes....  Since there is now only one other node listed in the
current nodelist that is not marked private and is a local call for me, I
could cheat with writing a simple dial translation and cost tables now.....
 [I also need to handle one private, -unpublished- node, but that takes
additional nodelist processor configuration entries anyway....]

 ...
 BJ> The only "mailer" that I've seen handle ILO/IUT 
 BJ> packets is BinkD.  But
 BJ> I haven't tried stuff outside of BinkD or later 
 BS> than the last official
 BJ> release of Binkley (2.60).

 BS> Qico works with ILO too, but it's a UNIX only mailer.. 
 BS> I wonder if T-Mail can use ILO too?

Ah.  Ok.....

Take care.....

Bob Jones, 1:343/41

--- Maximus/2 3.01