Hi g00r00,

When a mystic session times out whilst waiting on a "[�] More: (Y)es, (N)o, (C)ontinuous?" prompt, it appears to dump the pending list's contents to the client before terminating.

I've overridden the default inactivity prompt (#136) in an attempt to display
a custom time out screen, but a paused list still appears to get dumped
before the session is terminated.

Do you know a way to prevent further output once prompt #136 has been displayed?

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)

Re: Inactive connection
By: LEE WESTLAKE to g00r00 on Thu Mar 18 2021 12:22 am

When a mystic session times out whilst waiting on a "[�] More: (Y)es, (N)o, (C)ontinuous?" prompt, it appears to dump the pending list's contents to the client before terminating.

i responded to one of Lee's apposed (i think elsewhere.. maybe not?!) and can reproduce this behavior as well.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

When a mystic session times out whilst waiting on a "[�] More: (Y)es, (N)o, (C)ontinuous?" prompt, it appears to dump the pending list's contents to the client before terminating.

What list are you speaking of? The exit isn't always immediate but if you let me know the specific place I can try to improve it for you.

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

What list are you speaking of? The exit isn't always immediate but if
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)

Re: Re: Inactive connection
By: g00r00 to LEE WESTLAKE on Fri Mar 19 2021 10:15 am

What list are you speaking of? The exit isn't always immediate but if you g0> let me know the specific place I can try to improve it for you.in my case, being dumped while at the "read this new email?" prompt will result in a yes, close the session, and possibly result in me forgetting the email was ever there ;)

--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

The user listing would be one such example:

Okay thanks I've changed the user list so it won't bleed text on inactivity. If you notice anywhere else let me know!

--- Mystic BBS v1.12 A47 2021/02/12 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

Okay thanks I've changed the user list so it won't bleed text on inactivity. If you notice anywhere else let me know!

Many thanks g00r00, very much appreciated.

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)