TZUTC: -0700   
   MSGID: 51986.syncprog@1:103/705 2c3b00cf   
   PID: Synchronet 3.20e-Linux master/cc717b402 Mar 08 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/69f4a097d Mar 12 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/commit/8010070c0bc86aaf8104a144   
   Modified Files:   
   	src/sbbs3/sbbsecho.c   
   Log Message:   
   Take the configured origin line chars into account when determining charset   
      
   and if the message is UTF-8, encode the origin line as UTF-8 too.   
   If the message is straight ASCII (e.g. the sub-board is configured as ASCII   
   only), convert the configured origin line to ASCII, before appending.   
      
   At this time, only ASCII and CP437 encodings of originlines are supported   
   in Synchronet (imported and exported origin lines can contain UTF-8).   
      
   This should address the issue raise by Sergey Dorofeev (2:5020/12000) in the   
   FidoNet UTF-8 echo whereby messages exported from Synchronet systems   
   (presumably using SBBSecho) could contain a mixture of CP437 and UTF-8   
   encodings (!) when the sysop had CP437 chars in their configured origin line.   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   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 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 467/888 633/267   
   SEEN-BY: 633/280 384 418 420 2744 712/848 770/1 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 633/280 229/426