TZUTC: -0400   
   MSGID: 805.binkd@1:2320/105 2315c253   
   REPLY: 2:280/464.47 5eb007a8   
   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   
   > You can try to spin it again and again. I already quoted the BinkleyTerm   
   docum   
   > tation from 1990. But I do it again for you:   
      
   >"Note that outbound areas for domains other than your own will ALWAYS have a   
   zo   
   >e extension."   
    [...snip...]   
   > Since I started using it in 1993 the 5D BSO format hasn't changed. Only binkd   
   > vented it's own thing.   
      
   I have both BT and binkd installed on the same machine here.  Both of them   
   use the same format for my outbounds, by default.  I do not have to specify   
   the zone extension for each zone's outbound in either config file, and   
   shouldn't unless I want to break something.   
      
   I can tell you that binkd is using the same format that BinkleyTerm is   
   using... the zone extension, in HEX.   
      
   Mike   
      
      
    * SLMR 2.1a * This just in: Research causes cancer in rats!   
   --- SBBSecho 3.11-Linux   
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)   
   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: 2320/105 261/38 320/219 203/0 280/464 229/101 426