TID: Mystic BBS 1.12 A47   
   MSGID: 1:134/303 5ce1031c   
   REPLY: 1:129/215 ef2fdc85   
   TZUTC: -0600   
    g0> This doesn't mean its corruption (although it could).  It could be that   
      
   You're right, I suppose in most cases corrupt could likely lead to Mystic   
   being completely unable to read the data files.   
      
    g0> the message is marked as a private message or is twit filtered, search   
    g0> filtered, etc.   
    g0> It could be also be a bug in A46 that was fixed in A47 but I can't   
    g0> remember off the top of my head if something like that was fixed! :)   
      
   Without having any real proof, I suspect the last one in this case. My only   
   reasoning being that when new messages were received in an echomail area, the   
   issue I had went away.   
      
   At any rate, I'm on A47 now so I'll just have to wait and see if I run into   
   this again.   
      
   Thanks!   
      
   ... The seminar on time travel will be held two weeks ago   
   --- Mystic BBS v1.12 A47 2021/08/29 (Raspberry Pi/32)   
    * Origin: New Mystic BBS (1:134/303)   
   SEEN-BY: 1/123 30/0 90/1 103/705 105/81 120/340 123/131 124/5016 129/305   
   SEEN-BY: 134/0 100 101 303 153/105 757 802 154/10 203/0 218/700 221/0   
   SEEN-BY: 221/1 6 226/30 227/114 702 229/424 426 428 452 550 664 700   
   SEEN-BY: 229/981 1017 240/5832 249/206 307 317 400 261/38 280/464   
   SEEN-BY: 280/5003 282/1038 292/854 8125 301/0 1 101 317/3 322/757   
   SEEN-BY: 342/200 396/45 633/280 712/848 2452/250   
   PATH: 134/303 101 100 153/757 280/464 301/1 229/426