TZUTC: 1100   
   MSGID: 1621.fdn_binkd@3:633/509 264cb5ec   
   REPLY: 1:129/215 72277c7d   
   PID: Synchronet 3.19a-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0   
   TID: SBBSecho 3.14-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0   
   COLS: 62   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: Re: Problem with filenames containing spaces   
     By: James Coyle to Oli on Tue Jan 18 2022 03:50 pm   
      
   James,   
      
   > And its sad that you convinced non-FTN-techincal people like Paul and Deon   
   that you are some sort of subject matter expert (when everyone who actually   
   does this stuff knows you're a subject matter idiot).   
      
   So I'll have to disagree with you there.   
      
   What makes you think I am "non-FTN-technical"?   
      
   What makes you think that I have pondered whether Oli is a "subject matter   
   expert"? Now that you mention it though, his research and understanding of the   
   problem is spot on IMHO.   
      
   We've had this kind of discussion before - I dont think you understand the   
   problem - mainly because your replies conflict. I'm still not convinced that   
   the problem is with Binkd (actually I'm very confident it is not), but that is   
   moot - if your software doesnt work with it, I dont get why you wouldnt want   
   to make it work with it, even if the binkd development team werent interested   
   in "fixing" it the way you want it "fixed".   
      
   You have many people that like your software, wouldnt you want to make it work   
   so that they dont have a reason to look for something else (if it's failures   
   were becoming problematic for them)?   
      
   You have a known use case, as from the logs received by a Mystic user, the   
   file "MyGUI v1.0.2.26.zip" is encoded as "MyGUI\x20v1.0.2.26.zip" by binkd and   
   sent to a Mystic system. Mystic recorded "BINKP 1-Receiving: MyG   
   I\000v1.0.2.26.zip (1,669,424 bytes)" in the log file, and saved the received   
   portion as "MyGUI" (instead of it's proper name - I'm guessing related to the   
   \00?). The M_GOT response only included the text "M_GOT MyGUI", not what it   
   should have quoted back "M_GOT MyGUI\x20v1.0.2.26.zip 1669424 1641463672",   
   hence binkd bawlked with an error and kept re-trying to send the file   
   everytime the node connected.   
      
   Anyway, I dont use it - we know it cannot handle files with spaces in it from   
   a binkd mailer.   
      
      
   ...ëîåï   
   --- SBBSecho 3.14-Linux   
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)   
   SEEN-BY: 1/123 14/0 15/0 90/1 105/81 106/201 114/705 709 120/340 123/120   
   SEEN-BY: 123/131 129/305 153/250 7715 218/840 220/70 226/17 30 227/114   
   SEEN-BY: 229/110 200 307 317 424 426 550 664 700 240/5832 249/206   
   SEEN-BY: 250/5 8 266/512 267/800 280/464 282/1038 292/854 298/25 301/1   
   SEEN-BY: 305/3 317/3 320/219 322/757 342/200 396/45 633/267 280 281   
   SEEN-BY: 633/384 410 412 416 509 640/1384 712/848 770/1 100 340 772/210   
   SEEN-BY: 772/220 230   
   PATH: 633/509 280 770/1 317/3 229/426