TID: Mystic BBS 1.12 A46   
   MSGID: 2:250/6 bb9946a7   
   REPLY: 1:129/215 a929b05e   
   TZUTC: 0000   
    g0> What list are you speaking of?  The exit isn't always immediate but if   
    g0> you let me know the specific place I can try to improve it for you.   
      
   The user listing would be one such example:   
      
   If the user list extends across multiple screens and the session happens to   
   timeout whilst waiting on the "[þ] More: (Y)es, (N)o, (C)ontinuous?" prompt,   
   the pending user data is dumped to the client after the inactivity prompt   
   (#136) has already been invoked.   
      
   Ideally, prompt #136 should be the last data sent to the client prior to   
   session termination.   
      
   Many thanks for looking into this issue.   
      
   Best Regards   
      
   |01°|09²²²²² |01³|09 Lee Westlake |01(aka TALIADON)   
   °|09²|01°|09²|01°|09² |01³|09 TALIADON BBS |01(taliadon.ddns.net)   
     °|09²|01   ³ E-Mail: taliadon-bbs@mail.com   
    °|09²²²|01  ³ fsxNet: 21:3/138 ù FidoNet: 2:250/6   
      
   --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)   
    * Origin: TALIADON BBS (2:250/6)   
   SEEN-BY: 1/123 10/0 1 15/0 19/36 25/0 21 90/1 102/401 103/705 105/81   
   SEEN-BY: 106/201 116/18 120/331 340 123/131 140 124/5016 128/2 129/305   
   SEEN-BY: 153/757 7715 154/10 203/0 214/22 218/0 1 109 401 410 530   
   SEEN-BY: 218/700 720 802 810 840 850 221/0 226/30 227/114 702 229/101   
   SEEN-BY: 229/424 426 452 550 664 700 981 1016 1017 230/150 152 240/1120   
   SEEN-BY: 240/5411 5824 5832 5853 6309 249/206 307 317 400 250/0 1   
   SEEN-BY: 250/2 3 4 5 6 7 8 32 261/38 100 263/0 266/512 267/155 275/100   
   SEEN-BY: 280/464 5003 282/1038 1056 291/100 111 292/854 8125 317/3   
   SEEN-BY: 320/119 219 322/757 340/400 341/66 342/200 396/45 633/280   
   SEEN-BY: 640/1321 712/848 801/161 189 2320/105 2452/250 2454/119 3634/12   
   SEEN-BY: 5020/1042   
   PATH: 250/6 1 261/38 218/700 103/705 280/464 240/5832 229/426