BW> * If someone exceeds the maximum login attempts (enters an incorrect
 BW> password multiple times), gets prompt #538 (if the e-mail reset feature
 BW> has been enabled) and then hangs up at that prompt, Mystic appears to
 BW> send the password reset e-mail despite the fact that the user hung up --

I have cleaned this up so it will simply shut down the node and do nothing, since the user never actually asked for the e-mail.

 BW> * If a user attempts to deselect a (single) message base from new scans
 BW> or QWK new scans, which has New Scan: Forced or QWK Scan: Forced,
 BW> prompts #302/#406 do not seem to be shown any longer. (I know these

I think I might have it right this time in the next build.

 BW> * If someone exceeds the maximum login attempts, gets prompt #538, denies
 BW> e-mail reset, gets prompt #475, chooses to send a password inquiry to the
 BW> SysOp and then aborts the message from within the full screen editor, the
 BW> recipient of the automatic hackwarn message appears to be set to be the
 BW> SysOp rather than the potentially hacked user.

Should be fixed in the next build thank you!

... Everyone is entitled to my opinion!

--- Mystic BBS v1.12 A48 2022/07/11 (Windows/64)