TIP: Click on subject to list as thread! ANSI
echo: muffin
to: Bo Simonsen
from: Bob Jones
date: 2003-06-23 17:21:10
subject: Squish TODO

BJ> If you try to use "ROUTE NOARC NORMAL 1:234/567.8 1:234/*"
 BJ> and then have a line that does something like default route (from
 BJ> memory, something line "ROUTE CRASH 1:140/1 1:ALL 2:ALL 3:ALL 4:ALL
 BJ> 5:ALL 6:ALL"), then the mail that you packed for 1:234/567.8 gets
 BJ> retargted and sent to 1:140/1 (in this example).  
 BJ> Actually, it doesn't
 BJ> need to be a default route.  It just needs to be a command that ends
 BJ> up reprocessing node 1:234/567.8's outbound mail packets.....

 BS> But does squish not take topdown, until it find what it needed?
 BS> A thing there annoys me too, is that it use ROUTE.CFG 
 BS> for Echomail packages too.

Yes, Squish process the route.cfg file in a top down mannor.

And as to echomail, remember, echomail is just a special version of
netmail.  And like confmail and OMM, squish processes echomail just like
netmail....

 BJ> I forget whether the NOARC is needed or not needed in the ROUTE line
 BJ> for 1:234/567.8.  In any case, it keeps me from using NORMAL mail
 BJ> archives, and instead using just DIRECT, HOLD and CRASH.  I never did
 BJ> get Scott to understand why I considered this a bug in Squish.....

 BS> It shouldn't been because you are telling what to pack 
 BS> with in squish.cfg, i guess there is somekind of noarc 
 BS> option there?

You're keying off the noarc difference.  That is not the problem.  I
believe the problem is that squish re-scans the outbound area for each line
in route.cfg, and so reprocesses any newly created NORMAL flavor packets
with later lines in the route.cfg file.  

 BJ> Also, now that I have BinkP running, it might be nice to add support
 BJ> for ILO type flow controls to the ROUTE.CFG file.

 BS> For poll ?

If I had ILO packets (vs CLO, HLO, DLO and FLO), I could more easily
distingquish between sending something out via BINKD vs sending out via
Binkley.  Binkley won't touch the ILO packets, so with binkley configured
as a TCP/IP based mailer on my system, I can keep binkley from dialing my
BinkP based connections without nodelist mods (such as tweaking the cost
table, which is the method I'm using for now....)

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)
SEEN-BY: 633/267 270
@PATH: 343/41 10/345 106/1 2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.