TID: Mystic BBS 1.12 A46   
   MSGID: 1:134/303 09d08fbd   
   TZUTC: -0600   
   Does anyone have any strategies for dealing with Message Base corruption? For   
   me, it always seems to happen with Fidonet Echomail message bases. Most often   
   the Allfix File Announce conference but most recently in FidoNet Sysops.   
      
   What I am seeing is this:   
      
   Occasionally I'll have a message base where the interactive reader always   
   sees new messages. But there will be messages that I can't view. For example   
   the last message when opened will show something like 264 of 265. But there   
   is no 265 displayed.    
      
   I've tried packing and purging but those don't seem to help in this   
   situation. If it's an active message base, when new messages arrive things   
   seem to repair themselves. But if the base is quieter then it could be a long   
   time before new messges come in.   
      
   Is there any other way to deal with issues like this?   
      
   --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)   
    * Origin: CaNerDUH BBS (1:134/303)   
   SEEN-BY: 1/123 90/1 105/81 120/340 123/131 129/305 134/0 100 101 303   
   SEEN-BY: 153/105 757 802 154/10 218/840 221/6 226/30 227/114 702 229/424   
   SEEN-BY: 229/426 428 452 550 664 700 981 1017 240/5832 249/206 307   
   SEEN-BY: 249/317 400 261/38 280/464 282/1038 292/854 301/1 317/3 322/757   
   SEEN-BY: 342/200 633/280 770/1   
   PATH: 134/303 101 100 153/757 221/6 229/664 426