TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 a5dea70d   
   REPLY: 2:201/137 db7fcaae   
   TZUTC: -0400   
    BW> * FTP uploads appear to corrupt the file base. If I scroll down the   
    BW> listing   (from the BBS) I see garbage like:   
      
   I am not able to reproduce this one at least not in Windows.   
      
    BW> * When creating a new user from within the User Editor, the Taglines   
    BW> setting   appears to always be set to Ask instead of following the   
    BW> Configuration -->   New User Settings 2 --> Taglines setting.   
      
   This should be fixed in today's build.   
      
    BW> * When a new user is created (from the User Editor or by the BBS), the   
    BW> Start   Menu setting appears to be copied from the value given by   
    BW> Configuration -->   General Settings Start Menu (prelogin in my case)   
    BW> instead of being empty   (letting the current security level's Start   
    BW> Menu setting or the   Configuration --> General Settings --> Start Menu   
    BW> value apply automatically   on each login).   
      
   This should be fixed.  It will now keep them blank for new users, which will   
   cause it to pull from the security profile first, then the default if the user   
   does not have a specific menu setup.   
      
    BW> * When a user sends an e-mail to another user, a system notification is   
    BW>   generated (prompts #179 + #465 + #180), i.e., Mystic will announce the   
    BW> fact   that an e-mail has been received to the receiving user. However,   
    BW> if the   receiving user has node message availability (user setting 18)   
    BW> turned off,   prompt #395 is displayed to the sending user, which he/she   
      
   This should be fixed in latest!   
      
    BW> * When a user launches a private chat (the NP command) and is prompted to   
    BW>   select the node to chat with (prompt #479), hitting Enter to   
    BW> leave/cancel   displays prompt #480. My suggestion would be that if the   
    BW> user enters an   empty value (or a value containing whitespace only),   
    BW> Mystic should simply   quit the command without displaying prompt #480.   
      
   Your suggestion should be in the latest build!   
      
    BW> * When logging in with a QWK account and choosing (S) to select the   
    BW> bases to   scan/include, i.e., (OS) with Data: /ALLGROUPS /QWKNET, the   
    BW> message base   numbering in the list does not appear to match what it   
    BW> expects me to enter.   I have Configuration --> Message Base Settings   
      
   All of the new scan settings bugs for QWK and regular users should be fixed up   
   in the latest build.  Please let me know if you still have issues with any of   
   them with compression on or off.   
      
    BW> * If leaving the Packet ID field for my "local" QWK network empty, the   
    BW>   resulting FTP file name is ".qwk" (".qwk"). The whatsnew.txt   
      
   The CFG will now require a packet ID to be non-blank when configuring a QWK   
   Network.   
      
    BW> * Accounts which have "Locked Out: Yes" can still access Mystic via FTP,   
    BW>   SMTP, POP3 and NNTP. I would have expected them not to be able to do   
    BW> that.   
      
   This should be fixed in the latest build.   
      
    BW> * OV in "FTP ACS" for a file base always returns false even though an   
    BW> account   *is* correctly validated.   
      
   Fixed in latest!   
      
    BW> * baduser.txt mentions that "The list should contain a single name per   
    BW> line   and can include a * wildcard", but I can't get wildcard to work.   
      
   I believe the issue was that it was case sensitive.  I have not tested this   
   one yet, but it should possibly be fixed in the latest.   
      
    BW> * In a private (user2user) chat, if one user hangs up, the chat   
    BW> continues and   the remaining party does not get notified of this.   
      
   Should be fixed!   
      
    BW> * When using the snoop (*3) function, if the user on the selected node   
    BW> isn't   available for node messages, one gets prompt #395. Shouldn't   
    BW> snooping be   available regardless of the node messaging availability   
    BW> status? As one   cannot interact with the user (as with NodeSpy).   
      
   I think the reason I did it this way is because in some operating systems or   
   door setups (for example in Windows when using DOOR32 doors) snooping doesn't   
   work.  I'll change this.   
      
    BW> * More detailed logging of scanning results for FTP upploads.   
    BW>   Currently:   
      
   This should be in the latest build.   
      
   As far as the rest of them I still need to look into them but almost   
   everything you mentioned or suggested should be addressed in the latest build!   
      
   ... Redundant book title: DOS For Dummies   
      
   --- Mystic BBS v1.12 A48 2022/07/07 (Windows/32)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/120 123 14/5 15/0 18/0 90/1 105/81 106/201 116/116 120/340   
   SEEN-BY: 120/616 123/0 10 25 115 131 180 200 525 755 129/215 305 330   
   SEEN-BY: 129/331 134/100 135/300 153/757 7083 7715 154/10 30 40 50   
   SEEN-BY: 154/700 218/700 840 220/90 221/6 222/2 226/18 30 227/114   
   SEEN-BY: 227/201 229/110 111 112 113 206 307 310 317 400 424 426 428   
   SEEN-BY: 229/452 470 550 664 700 240/1120 250/1 266/512 275/1000 280/464   
   SEEN-BY: 282/1038 292/854 299/6 300/4 317/3 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 712/848 1321 2320/105 3634/0 12 15   
   SEEN-BY: 3634/27 50 56 119 5020/1042   
   PATH: 129/215 154/10 3634/12 153/757 221/6 229/664 426