TID: Mystic BBS 1.12 A46   
   MSGID: 1:275/99 c6a74b33   
   TZUTC: -0400   
   I've experienced (twice) a newscan issue with Mystic (at least with MY Mystic.)   
      
   I was reading messages in a public message base. Let's say I was at message   
   number 50 of 100.   
      
   I replied to message number 50, and I saved the message. Then I (J)umped to   
   message # 101 to make a quick edit to the message I just posted (the   
   reply.) After editing, I (Q)uit to get out of message reading.   
      
   I came back later to continue reading new messages, but this time Mystic has   
   my last read pointer set at message #101 (as if I already read 50-101.)   
      
   It seems like I tricked the system when I (J)umped to message # 101.   
      
   This isn't a big deal obviously - but has anyone else experienced this?   
      
   --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)   
    * Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)   
   SEEN-BY: 1/19 123 15/0 16/0 19/10 36 90/1 105/81 106/201 116/18 120/331   
   SEEN-BY: 120/340 123/130 131 140 128/2 129/305 142/799 153/757 7715   
   SEEN-BY: 203/0 218/700 221/0 1 6 242 360 226/30 227/114 702 229/101   
   SEEN-BY: 229/424 426 452 550 664 700 981 1016 1017 230/0 150 152 240/1120   
   SEEN-BY: 240/5832 249/206 307 317 400 250/1 261/38 100 266/512 267/155   
   SEEN-BY: 275/0 89 91 93 98 99 100 101 103 201 301 280/464 5003 282/1038   
   SEEN-BY: 282/1056 291/100 111 292/854 317/3 320/119 219 319 322/0   
   SEEN-BY: 322/757 340/400 341/66 342/200 396/45 423/81 633/0 267 280   
   SEEN-BY: 633/281 410 412 414 416 509 640/1138 1321 1384 712/848 801/161   
   SEEN-BY: 801/189 2320/105 3634/12 5020/1042   
   PATH: 275/99 100 261/38 320/219 221/1 640/1384 633/280 229/426