TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 ec13f498   
   REPLY: 2:201/137 a92f438d   
   TZUTC: -0400   
    BW> I just noticed that the MC (check e-mail) function appears to "miss"   
    BW> unread e-mails in its listing -- it only displays (lists) e-mails that   
    BW> are unread *and* new -- however the counter (prompt 127 &2) correctly   
    BW> displays the number of unread e-mails.   
      
   The e-mail base is not a message base, so throw out the idea of "new messages"   
   and "last read pointers" in this case. MC lists all of the e-mails in your   
   mailbox, and optionally hides the ones which you've read before if you use the   
   /unread option.   
      
    BW> I exit with G (as my Private Messages is mandatory reading and it will   
    BW> prevent me from exiting with Esc, apparently as long as there are new   
    BW> (N) messages left).   
      
   This is a bug and will be fixed in the next build.  You shouldn't be able to   
   use G to exit in that case.  If a base is mandatory read you should never be   
   able to exit unless you've seen the last message.  Nice catch!   
      
    BW> Here it misses displaying #34, even though I haven't read it. (It is not   
    BW> new, but still unread.) Notice that the prompt correctly says 2 unread   
      
    BW> Notice no listing of the only unread message (#34), despite a correct   
    BW> counter (1 unread). The completely empty list confuses the user (= me).   
    BW> :-D   
      
   The prompt you are showing is not the default so I don't know what prompt code   
   you are using (that prompt has two prompt codes that give different values).    
   It does look like a bug in that its either not displaying the first message   
   when it should or its displaying the "list" prompts when it should be showing   
   nothing at all. However I cannot seem to produce any problem here...   
      
   If you can give steps on how to reproduce a problem with MC without all of the   
   stuff with the reader/lastread/new messages/etc I think that would be less   
   confusing and more helpful for me.  In the meantime I will try to do some more   
   tests based on your original message to see if I can find a way to reproduce a   
   problem!   
      
   I am putting up a new build now with the 'G' mandatory fix in there so it   
   might be helpful to make sure we're both using that version when we try to   
   narrow this issue down.  Thanks for the feedback!   
      
   ... Running Windows is better than washing them!   
   --- Mystic BBS v1.12 A47 2021/07/28 (Windows/64)   
    * 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/101 310 424   
   SEEN-BY: 229/426 428 452 550 700 981 1016 1017 240/1120 5832 249/206   
   SEEN-BY: 249/307 317 400 261/38 280/464 282/464 1038 292/854 301/0   
   SEEN-BY: 301/1 101 113 317/3 322/757 335/364 341/66 342/200 633/280   
   SEEN-BY: 712/848 770/1 920/1 3634/12 5020/1042 5058/104   
   PATH: 129/215 154/10 301/1 229/426