MSGID: 2:280/464.47 5eb3cd02   
   REPLY: 805.binkd@1:2320/105 2315c253   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0200   
   TID: CrashMail II/Linux 1.7   
   Dumas wrote (2020-05-04):   
      
    >> 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."   
    DW>   [...snip...]   
    >> Since I started using it in 1993 the 5D BSO format hasn't changed. Only   
    >> binkd vented it's own thing.   
      
    DW> I have both BT and binkd installed on the same machine here.  Both of them   
    DW> use the same format for my outbounds, by default.  I do not have to   
    DW> specify the zone extension for each zone's outbound in either config   
    DW> file, and shouldn't unless I want to break something.   
      
    DW> I can tell you that binkd is using the same format that BinkleyTerm is   
    DW> using... the zone extension, in HEX.   
      
   how do your outbound directories look like? what's the outbound config in   
   binkd.cfg?   
      
   ---   
    * Origin:  (2:280/464.47)   
   SEEN-BY: 1/123 90/1 103/705 120/340 601 154/10 203/0 221/0 226/30   
   SEEN-BY: 227/114 702 229/101 200 426 664 1014 240/2100 5138 5832 5853   
   SEEN-BY: 240/6309 249/109 307 317 280/464 5003 5555 288/100 292/854   
   SEEN-BY: 292/8125 310/31 320/219 342/200 396/45 423/120 712/848 770/1   
   SEEN-BY: 2432/390 2452/250 2454/119   
   PATH: 280/464 240/5832 229/426