TID: Mystic BBS 1.12 A49   
   MSGID: 1:129/215 83b2be58   
   REPLY: <86a1b7d3-fd55-4e99-953d-9ac831488815n@googlegroups.com> 28fe98fb   
   TZUTC: -0400   
    gk> Sound like sending UTF8 TO the BBS is not working    
    gk> or still expected CP437. As when I switch my UTF8 session to    
    gk> to CP437 the chars working instantly (but as well well the rest is ugly   
    gk> as BBS sending in UTF8.   
      
   Yes this is currently broken.  I am planning to reamp and fix this after the   
   A49 release which will hopefully be soon.   
      
   Sorry for the inconvenience   
      
   ... My reality check just bounced   
      
   --- Mystic BBS v1.12 A49 2023/04/30 (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/616 123/10 120   
   SEEN-BY: 123/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/112 113 206 275 307 310 317 400 426 428 452 470 550 664   
   SEEN-BY: 229/700 250/5 8 266/512 267/800 280/464 282/1038 292/854   
   SEEN-BY: 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200 396/45   
   SEEN-BY: 460/58 633/280 712/848 770/1 2320/105 3634/12   
   PATH: 129/215 154/10 770/1 317/3 229/426