TZUTC: -0400   
   MSGID: 834.binkd@1:2320/105 23187431   
   REPLY: 1:275/201.30@fidonet 5eb2d9d5   
   PID: Synchronet 3.18a-Linux  May  3 2020 GCC 7.5.0   
   TID: SBBSecho 3.11-Linux r3.172 May  3 2020 GCC 7.5.0   
   CHRS: ASCII 1   
   >I am not sure why you need to use the nodelist in binkd since all the nodes   
   can   
   >be included in the Binkd.cfg. The mail tosser should be able to route the   
   outgo   
   >ng mail to the correct nodes or to your hub. Syncterm and CNet has a route-to   
   a   
   >ready included in the mail tosser config. That is the easer way to do it.   
      
   Well, the one reason I can think of to use it is that if you want to send a   
   node a direct netmail, and you don't usually connect with them, you have to   
   set them up in the cfg before you can connect to them.   
      
   I am assuming that, with the nodelist enabled, you don't have to do that so   
   long as their nodelist entry is accurate.  I assume that because I usually   
   just add them to the cfg file.  :)   
      
   Mike   
      
      
    * SLMR 2.1a * You could be reading the next message by now.   
   --- SBBSecho 3.11-Linux   
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)   
   SEEN-BY: 1/123 10/0 1 14/5 15/0 16/101 19/36 20/4609 90/1 102/401   
   SEEN-BY: 103/705 106/201 116/18 120/331 340 601 123/140 128/2 153/757   
   SEEN-BY: 153/7715 154/10 203/0 214/22 218/0 1 215 401 700 720 802   
   SEEN-BY: 218/820 221/0 222/2 226/30 227/114 702 229/101 200 426 664   
   SEEN-BY: 229/1014 230/150 152 240/1120 2100 5138 5832 5853 6309 249/109   
   SEEN-BY: 249/307 317 250/1 261/38 100 266/512 267/155 275/100 280/464   
   SEEN-BY: 280/5003 5555 282/1031 1056 288/100 291/100 111 292/854 8125   
   SEEN-BY: 310/31 320/119 219 340/400 341/66 342/13 200 396/45 423/120   
   SEEN-BY: 640/1321 712/848 770/1 801/161 189 2320/0 105 195 304 2432/390   
   SEEN-BY: 2452/250 2454/119 3634/12   
   PATH: 2320/105 261/38 218/700 103/705 280/464 240/5832 229/426