TID: FMail-lnx64 2.3.2.4-B20240523   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: CP850 2   
   PID: GED+LNX 1.1.5-b20240604   
   MSGID: 2:280/464 681337c6   
   REPLY: 57968.sync_sys@1:103/705 2c794eaf   
   Hi Nigel,   
      
   On 2025-05-01 01:52:15, you wrote to GitLab issue in main/sbbs:   
      
    NR> open https://gitlab.synchro.net/main/sbbs/-/issues/920   
      
    NR> Not sure if this is a you thing or a Digital Man thing. Looks like more   
    NR> encoding issues.   
      
    NR> ![image](https://gitlab.synchro.net/main/sbbs/uploads/d6e37   
   86ab0a3765526934ad   
    NR> 224fa171/image.png){width=769 height=472}   
      
    NR> You can see this in the new MOSCOWTIMES group.   
      
   I don't think it's a Synchronet issue.   
      
   The originating system for the messages in the MOSCOWTIMES area had an issue   
   where the message contained a 'CHRS: CP850 2' kludge, but the message and   
   subject text could contain utf-8 characters. That was fixed yesterday. So new   
   messages shouldn't have this problem.   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.3.2.4-B20240523   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 8912 5054/30   
   SEEN-BY: 5075/35   
   PATH: 280/464 460/58 229/426