MSGID: 2:203/2 61e98958   
   REPLY: 1:3634/12.73 61e96dc7   
   PID: JamNNTPd/Win32 1   
   CHRS: CP437 2   
   TZUTC: 0100   
   TID: CrashMail II/Win32 0.71   
    ml> i remember you posting about this... it is one of the things that lead   
    ml> to me attempting to reproduce the defect here on my OS/2 setup at that   
    ml> time... now i'm on linux and the defect still exists...   
      
      I don't know if it's the same, but I run a *very* old version directly on a   
   WinXP, and a few times the binkd has exited after a new nodelist compile. But   
   considering that it's worked perfectly for more than seven years now, I didn't   
   bother to spend any time on it.   
      
      
   Binkd 1.1a-65 (Sep 21 2014 18:59:33/Win32)   
   Compilation flags: mingw32, perldl, https, ntlm, amiga_4d_outbound, bwlim,   
   ipv6, fsp1035.   
   Facilities: fsp1035 ipv6   
      
      
      
      
   ..   
      
   --- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125   
    * Origin: news://eljaco.se:4119 (2:203/2)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 153/250 757 7715 154/10   
   SEEN-BY: 201/0 203/0 2 124 218/840 220/70 221/0 1 226/17 30 227/114   
   SEEN-BY: 229/110 200 307 317 424 426 550 664 700 230/0 240/5832 249/206   
   SEEN-BY: 250/5 8 266/512 267/800 280/464 5003 5555 282/1038 292/854   
   SEEN-BY: 292/8125 298/25 301/1 305/3 310/31 317/3 320/219 322/757   
   SEEN-BY: 341/234 342/200 396/45 423/120 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/100 340 772/210 220 230 2452/250   
   PATH: 203/2 0 280/464 770/1 317/3 229/426