TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 87990918   
   REPLY: 1:14/5@fidonet 6030ea5f   
   TZUTC: -0500   
    JS> + 02.19.2021 21:05:34  1-RB Socket read status 113   
    JS> + 02.19.2021 21:05:34  1-Connection lost   
    JS> + 02.19.2021 21:05:34  1-Authorization failed   
      
   If you Google read status 113 you get this:   
      
   The problem is triggered by the EHOSTUNREACH error (113) while reading the   
   data from the socket.  Normally, the EHOSTUNREACH error is given when writing   
   to a socket, however, for some reason, LINUX socket implementation returns   
   that error when reading from the socket under some unknown conditions. Since   
   we don't how to handle such error  (i.e.retry later or close the socket), it   
   was returned as an 'unknown' network error.   
      
   In translation, it sounds like something that could be firewall related?   
      
   --- Mystic BBS v1.12 A47 2021/02/12 (Windows/64)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/19 120 123 15/0 16/0 18/0 19/36 90/1 103/705 105/81 106/201   
   SEEN-BY: 116/18 116 120/331 340 457 123/0 10 25 35 40 115 130 131   
   SEEN-BY: 123/140 150 170 180 190 755 124/5016 128/2 129/215 305 135/300   
   SEEN-BY: 142/799 153/757 7715 154/10 30 40 50 700 201/0 203/0 124   
   SEEN-BY: 218/700 220/50 80 90 221/0 1 226/30 227/114 201 702 229/100   
   SEEN-BY: 229/101 310 424 426 452 550 664 981 1016 1017 230/0 150 152   
   SEEN-BY: 240/1120 5832 249/110 206 307 317 400 250/1 261/38 100 266/512   
   SEEN-BY: 267/155 275/100 280/464 5003 282/1031 1056 291/100 111 292/854   
   SEEN-BY: 292/8125 299/6 300/4 317/3 320/119 219 319 322/0 757 340/400   
   SEEN-BY: 341/66 342/200 396/45 633/280 640/1321 712/848 801/161 189   
   SEEN-BY: 2320/105 2452/250 3634/0 12 15 24 27 50 119 5020/1042   
   PATH: 129/215 154/10 3634/12 261/38 320/219 203/0 280/464 229/101   
   PATH: 229/426