TID: Mystic BBS 1.12 A46   
   MSGID: 1:129/215 1c2802bf   
   REPLY: 1:261/1304 5EECB567   
   TZUTC: -0400   
    MH> I tried GameSrv (TelnetDoor) and had the same issue so it must not be   
    MH> creating a binary connection, either.  It wasn't clear as to just being   
    MH> a "double telnet" related issue or something else.   
      
   There is no such thing as "creating a binary connection" via telnet.   
      
   Telnet options are negotiated after the connection.  Binary mode is something   
   the server would request and the client would respond to.   
      
   One way to test Mystic specifically is if you use the outbound telnet to   
   connect to your own Mystic BBS again.  The transfers still work even when you   
   connect through multiple telnet connections.  I just tested that again in the   
   latest Windows build and the transfers were working fine with NetRunner   
   Zmodem.   
      
   --- Mystic BBS v1.12 A46 2020/06/11 (Windows/64)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 18/200 90/1 120/340 601 123/131 226/30 227/114 702   
   SEEN-BY: 229/101 424 426 452 664 1014 240/5832 249/206 317 400 317/3   
   SEEN-BY: 322/757 342/200 633/280   
   PATH: 129/215 154/10 280/464 229/101 426