REPLY: 3:770/100 111cf092   
   MSGID: 2:460/5858 61dfd227   
   PID: GED+W64 1.1.5-b20170303   
   CHRS: CP866 2   
   TZUTC: 0300   
   RealName: Brother Rabbit   
   TID: hpt/w64-mvcdll 1.9.0-cur 2021-10-08   
   Hi, Paul!   
      
   13 ï­¢ 22 11:53, Paul Hayton -> All:   
      
    PH> This is not a properly escaped filename being sent by BinkD as it does   
    PH> not follow the BINKP protocol specifications for filename escaping:   
      
   http://ftsc.org/docs/fts-1026.001   
      
   Publication:    FTS-1026   
   Revision:       1   
   Title:          Binkp/1.0 Protocol specification   
   Authors:        Michiel Broek   
                   Stas Degteff   
   Issue Date:     1 December 2005   
   Review Date:    1 December 2007   
      
   [...skipped...]   
      
     5.2 Escaping method for illegal characters in Command Argument   
     --------------------------------------------------------------   
      
      In some cases there is a need to send illegal characters in   
      the command argument (usually the file name). These characters   
      SHOULD be escaped using form of 4th symbols sequence: "\", "x"   
      and two hexadecimal digits (digits "a".."f" may be any case).   
      Examples:   
      whitespace (" ") excaped as "\x20"; pipe ("|") escaped as "\x7c".   
      
      If escaping may be used in some command argument, mailer MUST   
      allways escape character '\' for prevent uncertainty.   
      
      In FSP-1011.003 the escape method is specified as two hexadecimal   
      digits preceded with a backslash (e.g. a whitespace is   
      transmitted as "\20").  Some mailers have implemented that method.   
      It is advised to have a setting for specific nodes to sent escaped   
      characters using the incorrect method.   
      
      Any mailer SHOULD decode "\20" into space in file names for   
      compatibility purposes.   
      
      
     5.3 Non-ASCII Characters in Command Argument Symbol String   
     ----------------------------------------------------------   
      
      Generally, mailer SHOULD use only characters from the ASCII range   
      [32...126] in the symbol strings for command arguments.   
      Other characters MAY be used only in M_NUL command argument in   
      plain form.   
      Implementation recommendation: use isprint() function (ISO C).   
      
      
     5.4 File Name Issues   
     --------------------   
      
      In binkp commands that contain a file name, the file name MUST NOT   
      include a whitespace (ASCII value 20 hex). If name of file to send   
      contents space, it MUST be escaped. The file name SHOULD NOT   
      include symbols other than alphanumeric (A-Z,a-z,0-9) and safe   
      characters as defined below in BNF. All other symbols are to be   
      considered unsafe and SHOULD be escaped. Space and backslash (\)   
      MUST be escaped.   
      For example: file name "abcd e.0f@" must be transmitted in form   
      "abcd\x20e.0f@".   
      
      filename= *pchar   
      pchar   = plain | escaped   
      plain   = alpha | digit | safe   
      safe    = "!" | """ | "#" | "$" | "%" | "&" | "'" | "(" | ")" |   
                "*" | "+" | "," | "-" | "." | "/" | ":" | ";" | "<" |   
                "=" | ">" | "?" | "@" | "[" | "]" | "^" | "_" | "`" |   
                "{" | "|" | "}" | "~"   
      alpha   = "A" | "B" | ... | "Z" | "a" | "b" | ... | "z"   
      digit   = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"   
      escaped = "\x" HEX HEX   
      HEX     = digit | "A" | "B" | "C" | "D" | "E" | "F" | "a" | "b" |   
                  "c" | "d" | "e" | "f"   
      
      Note: some characters are illegal for file names in some OS such as   
      DOS or Windows. The protocol do not impose limitations for these   
      characters in file names and if mailer receives OS incompatible   
      file name then it's reaction determine on a implementation: mailer   
      may be destructive skip file, save file with some legal name or   
      other.   
      
      The protocol does not impose limitations on the file name length   
      other than those arising from the finite length of the binkp frame   
      itself. Really file name length can't exceed 32751 bytes.   
      
      
   Have nice nights.   
          Stas Mishchenkov.   
      
   --- ‘â à®áâì - íâ® ª®£¤  ¢¨¤¨èì á¨á쪨 ¨ ¢á¯®¬¨­ ¥èì, çâ® § ¡ë« ¬®«®ª  ªã¯¨âì   
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)   
   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/16 58 256 1124 5858 463/68 633/280 712/848 770/1   
   SEEN-BY: 770/100 340 772/210 220 230 2452/250 5054/30   
   PATH: 460/5858 58 280/464 770/1 317/3 229/426