MSGID: 1:275/201.30@fidonet 5eb2d9d5   
   PID: CNet PRO 5.21b   
   ML> i don't use the perl hooks... AFAIK, the existing nodelist perl thing with   
   ML> binkd is not for compiling the nodelist into a binkd nodelist but for   
   ML> performing lookups on the nodelist...   
      
   ML> i prefer to use the binkd_nodelister.pl script to build my binkd   
   ML> compatible nodelist... it can also be used to other nets but you have to   
   ML> be sure to specify the input, error, and output files for those othernet   
   ML> nodelists... i think there's one other problem in that it adds "@fidonet"   
   ML> to the end of all addresses even if they are not fidonet addresses...   
   ML> that's a small bug that can be fixed...   
      
   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   
   outgoing mail to the correct nodes or to your hub. Syncterm and CNet has a   
   route-to already included in the mail tosser config. That is the easer way to   
   do it.   
   --- CNet/5   
    * Origin: 1:275/201.0 (1:275/201.30)   
   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: 275/201 100 261/38 320/219 203/0 280/464 229/101 426