-=> mark lewis wrote to Bill McGarrity <=-   
      
    ml> 22 Feb 16 14:49, Accession wrote to you:   
      
    BM>>>> OK... so in sbbsecho.cfg I can just have a ROUTE_TO 1:xxxx/xxx   
    BM>>>> 1:xxxx/xx.* with no need to play with binkd.... :)   
      
    Ac>>> Correct. As long as you have the .0 (boss node) address in your   
    Ac>>> binkd config.   
      
    ml> yes, and as mentioned later, if you are using the distributed binkd.txt   
    ml> or are creating your own, that .0 boss node should be available...   
      
   Which I do.   
      
    BM>> If I'm using sbbsecho to route it to the boss node, why would I need   
    BM>> the boss node's address in the binkd.cfg?  Wouldn't sbbsecho create a   
    BM>> .cut using the boss nodes address which binkd will understand?   
      
    Ac> If you're using BINKD.TXT I don't suppose it would be an issue, since   
    Ac> you would basically have an unsecure (passwordless) session defined in   
    Ac> binkd's config anyways.   
      
    ml> right... the main thing is to make sure that you have sbbsecho   
    ml> configured to route a message to a point to its boss node /unless/ that   
    ml> point has a connection with your system... in that case, you will have   
    ml> an entry for that point already set up...   
      
   Which I just added to my sbbsecho.cfg   
      
    Ac> Either way, some kind of link for that bossnode would have to be   
    Ac> somewhere in binkd or you would have to be using binkd.net for   
    Ac> lookups, otherwise it would have no idea who or where to poll.   
      
    ml> depending on the operator's routing configuration, it may go routed to   
    ml> their echomail feed... that is if sbbsecho's 1:ALL format also covers   
    ml> points or if one has to specify 1:ALL/ALL.ALL... this also in   
    ml> conjunction with the message's own FTN control attributes which may   
    ml> specify (eg) DIRect which then overrides any routing and requires that   
    ml> the point either poll for the waiting mail OR there is an entry in a   
    ml> binkd.txt type of list with connection details for the destination   
    ml> point system...   
      
    ml> once the mail is packed, the destination is set in BSO type mailer   
    ml> systems... external tools like bonk and son-of-bonk were created to   
    ml> handle the rerouting of mail in BSO environments...   
      
    ml> this is where dynamic mailers shine compared to BSO type "blackhole"   
    ml> mailers ;)   
      
   Agreed. Frontdoor is so much easier but I'm sure I got it working... :)   
      
   Thanks...   
      
      
   --   
      
   Bill   
      
   Telnet: tequilamockingbirdonline.net   
   Web: bbs.tequilamockingbirdonline.net   
   FTP: ftp.tequilamockingbirdonline.net:2121   
   IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697   
   Radio: radio.tequilamockingbirdonline.net:8010/live   
      
      
   ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!   
   --- MultiMail/Win32 v0.50   
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)