Re: Re: Test2
  By: Nicholas Boel to Joe Delahaye on Wed Nov 19 2014 17:02:54

 JD>> I wonder if a PW is necessary.  When I was playing with that, (the
 JD>> host and the point were the same person), I had no PW with  him, but
 JD>> direct mail would go out.  I have most of my contacts set to either
 JD>> direct, or None.

 NB> A packet password? I doubt it, since the point would be routed through the
 NB> host node, it should probably only matter with the system you're
 NB> connecting with (the host). So if you already have a password setup with
 NB> Mark's main system, you shouldn't need to specify one for the point, since
 NB> that's unknown as you're routing through the host.

No, a session password.  Also, the recipient, is not in my sbbsecho nodelist
(bossnode I mean)


 JD>> Yeah, but how would that work for those that I have a direct link
 JD>> with?

 NB> I *think* it would take preference on the direct links before the routed
 NB> ones. So, if a direct link is specified, it would be send direct. Then
 NB> "ALL" links not specified otherwise, would be routed through Mark's
 NB> system.

I am at a loss on how to do that since only those in my tosser nodelist, can
handle a route statement.  I tried it without by adding a route-to manually and
sbbsecho refused to do anything other then start the program.   Even after I
rememoved that entry, it still would not, until I opened a cmd window and ran
it that way..  Was fine after that. (thankfully)

 NB> With this, I'm not sure if order matters (I don't think it does), but
 NB> since I use sbbsecho.cfg directly instead of the GUI thing (echocfg I
 NB> think), I order them the way I want them, ie:

 NB> DIRECT 
 NB> DIRECT 

 NB> ROUTE_TO  1:ALL or net specific>

 NB> DIRECT 
 NB> DIRECT 

 NB> ROUTE_TO  2:ALL or net specific>
 NB> It's much easier for me to read and keep track that way, but I don't think
 NB> echocfg utilizes any kind of order like that so I'm not sure it matters
 NB> any.

I will play with it some more and see what happens. but anything in the que
wont be affected by any change made in the tosser.


 NB> I'm leaning towards a bit of both of those reasons, but probably more of
 NB> the first, since I'm sure other mailers handle that just fine. BUT, if you
 NB> have routing in both your tosser and your mailer, it can probably be
 NB> pretty easy to mess things up even worse, so.. I digress. :)

Not hard to mess things up at all 
--- SBBSecho 2.27-Win32