MSGID: 2:280/464.47 61e0a41e   
   REPLY: 3:770/100 12dbf6f0   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Paul wrote (2022-01-14):   
      
    PH> On 13 Jan 2022 at 10:15a, Stas Mishchenkov pondered and said...   
      
    PH>>> This is not a properly escaped filename being sent by BinkD as   
    PH>>> it doe not follow the BINKP protocol specifications for   
    PH>>> filename escaping:   
      
    SM>> http://ftsc.org/docs/fts-1026.001   
      
    PH> Hi Stas   
      
    PH> I am not a developer so am unsure what it is you are saying by posting   
    PH> this reply?   
      
   Like it's always the same. It's never Mystic's problem, the others are doing   
   it wrong. (Why should the guru read the fucking manual? Why should he ask for   
   advice? He always knows better ...)   
      
   As far as I understand it, the quote in your mail was from an older spec and   
   not the most recent FTSC. Mailers must send \x20, but should accept \20 too.   
   Sending \20 is a bug in Mystic, but most mailers would accept it. Not   
   understanding \x20 was a bug in Mystic in previous versions.   
      
   ---   
    * Origin: Birds aren't real (2:280/464.47)   
   SEEN-BY: 1/123 14/0 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 153/250 757 7715 154/10 203/0   
   SEEN-BY: 218/840 220/70 221/0 226/17 30 227/114 229/110 200 307 424   
   SEEN-BY: 229/426 550 664 700 240/5832 249/206 317 250/5 8 266/512   
   SEEN-BY: 267/800 280/464 5003 5555 282/1038 292/854 8125 298/25 301/1   
   SEEN-BY: 305/3 310/31 317/3 320/219 322/757 341/234 342/200 396/45   
   SEEN-BY: 423/120 460/58 633/280 712/848 770/1 100 340 772/210 220   
   SEEN-BY: 772/230 2452/250   
   PATH: 280/464 770/1 317/3 229/426