TID: Mystic BBS 1.12 A49   
   MSGID: 1:129/215 abd2f069   
   REPLY: <29014ff3-307a-4c78-8208-e09f94af5c2an@googlegroups.com> fbea0c87   
   TZUTC: -0500   
    TW> Eureka!  I found the permission issue.  My Mystic user was not a member   
    TW> of the Mystic user group that I had created.  As soon as I added the   
    TW> user to the group, everything works as you said with owner:group as   
    TW> user:user.   
      
   Thats great to hear and thanks for following up to let me know!   
      
    TW> That to say, there is nothing wrong with Mystic.   
      
   Even better news! :)   
      
   ... THE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK   
      
   --- Mystic BBS v1.12 A49 2023/01/17 (Windows/64)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/340 616 123/10   
   SEEN-BY: 123/120 131 129/215 305 153/7715 154/10 30 40 50 700 218/700   
   SEEN-BY: 218/840 220/70 90 221/6 226/17 18 30 70 100 227/114 201 229/110   
   SEEN-BY: 229/111 112 113 114 206 275 307 310 317 400 424 426 428 452   
   SEEN-BY: 229/470 550 664 700 250/5 8 266/512 267/800 280/464 282/1038   
   SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12   
   PATH: 129/215 154/10 770/1 317/3 229/426