TID: Mystic BBS 1.12 A46   
   MSGID: 1:340/1000 923fe2f2   
   TZUTC: -0700   
   Made the changes & did a manual poll of one of my hubs. Didn't work...but it   
   did attempt it. Here's the log of it:   
      
   ! 04 May 12:34:11 [1] binkd.cfg: 38: d:\fe\inbound\insecure: incorrect   
   directory   
      
   Made the folder & went away.   
      
   ! 04 May 12:35:27 [1] binkd.cfg: 39: inbound-temp: unknown keyword   
      
   Changed this from inbound-temp to temp-inbound & went to the steps below.   
      
     04 May 12:36:48 [1] BEGIN, binkd/0.9.4 binkd.cfg   
     04 May 12:36:48 [2] clientmgr started   
     04 May 12:36:48 [1] servmgr started   
   ! 04 May 12:37:27 [1] got signal #4.   
      
     04 May 12:39:40 [1] BEGIN, binkd/0.9.4 -P3:770/1 binkd.cfg   
     04 May 12:39:40 [1] creating a poll for 3:770/1@fsxnet (`i' flavour)   
     04 May 12:39:40 [2] clientmgr started   
     04 May 12:39:40 [1] servmgr started   
   + 04 May 12:39:40 [3] call to 3:770/1@fidonet   
     04 May 12:39:41 [3] trying 219.89.83.33...   
   ? 04 May 12:39:41 [3] unable to connect: No route to host   
   + 04 May 12:40:40 [3] call to 3:770/1@fidonet   
     04 May 12:40:40 [3] trying 219.89.83.33...   
   ? 04 May 12:40:40 [3] unable to connect: No route to host   
   ! 04 May 12:40:49 [1] got signal #6.   
      
   Tried another hub as well...but got the same information. Looks like it's   
   running & trying to connect. Where do I goto now?   
      
   ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.   
      
   --- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)   
    * Origin: ACME BBS-W.Coyote & D.Brown are our best users.  (1:340/1000)   
   SEEN-BY: 1/123 90/1 120/340 601 220/50 226/30 227/114 702 229/100   
   SEEN-BY: 229/101 200 426 664 1014 240/5832 249/109 307 317 292/854   
   SEEN-BY: 342/200   
   PATH: 340/1000 770/1 280/464 229/101 426