TID: Mystic BBS 1.12 A47   
   MSGID: 1:218/860 39f46cda   
   REPLY: 1:129/215 310ecdc0   
   TZUTC: 0000   
    g0> It sounds like you may have had some sort of corrupted packet of some   
    g0> type that Mystic couldn't gracefully "fail" with. Do you still have the   
    g0> file MUTIL was crashing on by chance or any of the files that were   
    g0> clogged up in your folder? I would like to see if I could use it to   
    g0> reproduce the crash and handle it more gracefully but I probably   
      
   I had hoped one of my automated backups had copies when I went to sleep in the   
   middle of the crisis, but apparently they don't.  Next time I will save them.    
   I didn't think much of the situation when it occurred since it was my fault.   
      
   In any case, things are working fine now.   
      
   Thanks for your response, and all of your work on Mystic all these years.  I   
   appreciate it.   
      
   --- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)   
    * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (1:218/860)   
   SEEN-BY: 1/123 10/0 1 90/1 102/401 103/1 705 105/81 120/340 123/131   
   SEEN-BY: 124/5016 129/305 153/757 154/10 203/0 218/0 1 410 530 700   
   SEEN-BY: 218/720 802 810 840 850 860 870 880 221/0 226/30 227/114   
   SEEN-BY: 227/702 229/424 426 428 452 550 664 700 981 1017 240/1120   
   SEEN-BY: 240/5411 5824 5832 5853 5890 6309 249/206 307 317 400 261/38   
   SEEN-BY: 280/464 5003 282/1038 292/854 8125 301/1 317/3 320/219 322/757   
   SEEN-BY: 342/200 396/45 633/280 2452/250 2454/119   
   PATH: 218/860 700 103/705 280/464 240/5832 229/426