TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 6b57c3e4   
   REPLY: 1:153/7083 6195f914   
   TZUTC: -0500   
    EW> I've toggled the "No Timeout" setting for my account (Mystic v1.12 A45   
    EW> 2020/08/26 (Linux/32)); but after sometime, the BBS would just boot me   
    EW> back out (if I was telnet'd) or back to the bash prompt (if I just use   
    EW> 'mystic -l').  I don't see any errors in the node?.log.   
      
   The No timeout flag disables the inactivity timeout (not time per day) but   
   there are some many possiblities as to why you might be getting disconnected,   
   anything from a bug to running out of time, to your ISP/router killing open   
   sockets because you're idle and it thinks they're stale (ie you would need a   
   telnet client if connected via telnet that sends NOOP to stay connected)...   
      
   If you are connected via ./mystic -l and it happens, that seems to point to   
   something else not client/router related.  If you ran out of time (ie minutes   
   per day) or were removed from inactivity, then it should have printed a   
   message or logged you out as you noted.   
      
   I don't really have a good explaination for you at the moment to be honest.   
      
   ... Help! I can't find the "ANY" key.   
   --- Mystic BBS v1.12 A47 2021/11/06 (Windows/32)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 30/0 80/1 90/1 103/705 105/81 120/340 457 616 123/10   
   SEEN-BY: 123/131 129/215 305 154/10 30 40 50 700 203/0 218/700 220/80   
   SEEN-BY: 220/90 221/1 6 226/18 30 227/114 201 702 229/310 424 426   
   SEEN-BY: 229/428 452 550 664 700 981 240/1120 5832 249/206 307 317   
   SEEN-BY: 249/400 261/38 280/464 282/464 1038 292/854 301/0 1 101 113   
   SEEN-BY: 317/3 322/757 335/364 341/66 342/200 633/280 712/848 770/1   
   SEEN-BY: 920/1 3634/12 5020/1042 5058/104   
   PATH: 129/215 154/10 301/1 229/426