MSGID: 2:280/464.47 61e1e914   
   REPLY: 1:129/215 a45b6c98   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   James wrote (2022-01-14):   
      
    JC> I can't figure out what you're trying to show there, but I don't think   
    JC> you know either.   
      
   Of course you know better what I know.   
      
    JC> Thats not the escaping code if that is what you're   
    JC> going for. This is:   
      
    JC> char *strquote (char *s, int flags)   
    JC> {   
    JC>        ... (cut some stuff) ...   
    JC>        sprintf (r + i, "\\x%02x", *(unsigned char *) s);   
    JC> }   
      
   I linked that.   
      
    JC> And at least in the version you're showing me, BINKD does not implement   
    JC> the per-connection option for legacy escaping as per the FTS update.   
      
   There is no such thing as legacy escaping. Please show us a binkd version from   
   the 90s that uses \## instead of \x##. I don't think there is one. AFAIK it   
   was always \x##.   
      
    JC> If   
    JC> it did, then Paul would not have the issue he's having and thus why I   
    JC> sent him in this direction.   
      
   Nope, it's a bug in Mystic.   
      
    JC> Paul's issue cannot be solved unless BINKD is updated or his downlink   
    JC> changes software versions. There is literally nothing I can do to help   
    JC> him.  I don't care if BINKD wants to support escaping in legacy mode as   
    JC> per FTS or not personally.   
      
   Of course you don't (and know better). Maybe your users do care though.   
      
    JC> And for the record.  Here's Mystic's code for this.  It more closely   
    JC> follows FTS in comparison to the link I just looked at which you sent, so   
    JC> I don't know what you're complaining about:   
      
   So you say that binkp should implement a workaround, because some Mystic   
   versions don't understand a "\x20" specified by a > 15 years old FTS?   
      
    JC> Function TBinkP.EscapeFileName (Const Str: String) : String;   
    JC> { Replace illegal characters with \## escaped sequences }   
   				    ^^^ wrong   
      
    JC>      Else   
    JC>        { 0=Original BINKP (Argus, IREX, Amiga) }   
      
   Argus indeed expects \##. But it's not "original binkp".   
      
    JC>        { 1=Updated (Post 2010+ FTS updates ie BINKD uses this) }   
      
   FSP-1011 had an error and "some mailers have implemented that method". For   
   that reason FTS-1026 states that "any mailer SHOULD decode \20 into space in   
   file names for compatibility purposes". FTS-1026 did not update/change \20 to   
   \x20, but added \20 as an alternative escaping method for non-   
      
   binkd also added a workaround for non-compliant mailers (but only one way).   
      
   ---   
    * 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