TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 32a7341c   
   REPLY: 1:317/3 2a380b7a   
   TZUTC: -0500   
    BP> I'm currently working on updating a MPL from a few years ago, and it   
    BP> keeps it own log file. The log file is now getting renamed to   
    BP> 'conflicted'.   
    BP>    
    BP> unopened? Is this a general 'catch-all' type of event that happens when   
    BP> there is an error somewhere? It would just give me somewhere to start   
    BP> looking for the problem. :)   
      
   There is nothing in Mystic that does this that I can think of anyway.  Are you   
   using a networked file share of some sort that could be doing this while there   
   are conflicts in files?  Or a VMware with shared directories or anything like   
   that?   
      
   ... As a matter of fact, it IS a banana in my pocket!   
      
   --- Mystic BBS v1.12 A47 2021/11/24 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 457 616 123/10 131 124/5016   
   SEEN-BY: 129/215 305 153/757 154/10 30 40 50 700 203/0 220/80 90 221/0   
   SEEN-BY: 221/6 226/18 30 227/114 201 229/310 424 426 428 452 550 664   
   SEEN-BY: 229/700 240/1120 5411 5824 5832 5853 5890 6309 249/206 307   
   SEEN-BY: 249/317 400 280/464 5003 282/1038 292/854 8125 301/1 317/3   
   SEEN-BY: 320/219 322/757 341/234 342/200 396/45 633/280 770/1 2452/250   
   SEEN-BY: 2454/119 3634/12   
   PATH: 129/215 154/10 280/464 240/5832 229/426