TZUTC: 1100   
   MSGID: 1596.fdn_binkd@3:633/509 2645e392   
   REPLY: 3:770/100 12dbf6f0   
   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: 139   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: Re: Problem with filenames containing spaces   
     By: Paul Hayton to Stas Mishchenkov on Fri Jan 14 2022 10:42 am   
      
    > I am not a developer so am unsure what it is you are saying by posting this   
   reply?   
      
   James has quoted a FTS proposal. (hex chars are represent as \nn)   
      
   Stats quoted the accepted technical standard. (hex chars are presented as   
   \xnn, but should also accept/understand any mailer using \nn) - with a later   
   date IIRC.   
      
   binkd has implemented the procotol as per the standard, whereas james has   
   implemented as per the proposal.   
      
   Ergo, while he is saying binkd is doing it wrong, it is in fact mystic that is   
   doing it wrong (from a standards point of view).   
      
      
   ...ëîåï   
   --- 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 19/10 30/0 80/1 90/1 103/705 105/81 106/201   
   SEEN-BY: 114/709 120/340 123/131 129/305 153/7715 154/10 203/0 218/700   
   SEEN-BY: 221/0 1 6 242 360 226/30 227/114 229/110 200 307 424 426   
   SEEN-BY: 229/550 664 700 230/0 240/1120 5832 249/206 317 266/512 280/464   
   SEEN-BY: 280/5003 5555 282/464 1038 292/854 301/0 1 101 113 123 812   
   SEEN-BY: 317/3 320/219 322/757 335/364 341/66 342/200 396/45 423/81   
   SEEN-BY: 460/58 633/267 280 281 384 410 412 416 509 640/1138 1384   
   SEEN-BY: 712/848 770/1 920/1 3634/12 5020/1042 5058/104   
   PATH: 633/509 280 640/1384 221/1 301/1 229/426