TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 0fdcf527   
   REPLY: 2:203/2 61e79116   
   TZUTC: -0500   
    BF>  d> Anyway, I dont use it - we know it cannot handle files with spaces   
   in  BF>  d>  BF>  d>  BF>  d>  BF>  d>    
    BF>  d> from a binkd mailer.   
    BF>    
    BF>    After all, there's a plethora of alternatives, many of them Open   
    BF> Source (like the product discussed in this echo), so why insist on using   
    BF> something that you can see never will fix obvious bugs?   
      
   Agreed.  Why would anyone use the software that is outright refusing to   
   implement FTS guidelines for filename escaping?  One that would knowingly fix   
   compatibility issues with legacy BINKP implementations?   
      
   It took a whole hour to get this implemented when it was asked to be added   
   into Mystic and the person who asked didn't have to endure a bunch of drama!   
      
   Other options are right :)   
      
   ... Running Windows is better than washing them!   
      
   --- Mystic BBS v1.12 A48 2022/01/14 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 14/0 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 120/616 123/10 120 131 124/5016 129/215 305 153/250 757 7715   
   SEEN-BY: 154/10 30 40 50 700 203/0 218/840 220/70 80 90 221/0 6 226/17   
   SEEN-BY: 226/18 30 227/114 201 229/110 200 307 310 317 424 426 550   
   SEEN-BY: 229/664 700 240/5832 249/206 250/5 8 266/512 267/800 280/464   
   SEEN-BY: 280/5003 5555 282/1038 292/854 8125 298/25 301/1 305/3 310/31   
   SEEN-BY: 317/3 320/219 322/757 341/234 342/200 396/45 423/120 460/58   
   SEEN-BY: 633/280 712/848 770/1 100 340 772/210 220 230 2320/105 2452/250   
   SEEN-BY: 3634/12   
   PATH: 129/215 154/10 280/464 770/1 317/3 229/426