MSGID: 2:5020/12000 4f53923a   
   REPLY: 1:154/10 67ce4e82   
   TZUTC: 0300   
   CHRS: UTF-8 4   
   Hello Nicholas,   
      
   orig.message to echo UTF-8 on 09 Mar 25  21:23:00   
    >> That's the thing that I do to keep all messages on my node in UTF-8...   
    >> without stable success though.   
    NB> What is unstable about it, if you don't mind me asking?   
      
   Not all sysops use correct CHRS kludge.   
   Moreover, there is some messages with two different charset (some SYNCHRO   
   users) - message itself in UTF-8, but tearline uses CP437-encoded   
   pseudographics.   
      
    >> or set the one and only encoding. Second way was chosen.   
    NB> Do you still translate all incoming mails to UTF-8 using iconv so they're   
    NB> readable?   
      
   Yes. But no external iconv, pyhton internal decode/encode.   
      
    >> May be it is duty of ZC, to drop invalid segment, and not "help" sysop   
    >> to publish errors, replacing them with any mark.   
    NB> I would love to see those "?" entries in DAILYUTF as "🖕" instead. At   
   least   
    NB> then it wouldn't cause errors. :)   
      
   😁   
      
   Sergey   
      
   ... vim   
   --- PyFTN   
    * Origin: fluid.fidoman.ru (2:5020/12000)   
   SEEN-BY: 1/19 16/0 19/37 50/109 105/81 106/201 123/130 128/187 142/104   
   SEEN-BY: 153/757 7715 154/10 110 201/0 203/0 218/700 840 221/1 6 242   
   SEEN-BY: 221/360 226/30 227/114 229/110 114 317 426 428 470 700 705   
   SEEN-BY: 230/0 240/5832 280/464 5003 291/111 292/854 301/1 320/119   
   SEEN-BY: 320/219 319 2119 322/762 335/364 341/66 234 423/81 902/26   
   SEEN-BY: 5015/46 5020/715 830 848 1042 2065 4441 12000 5030/49 1081   
   SEEN-BY: 5030/1474 5058/104 5061/133 5097/31   
   PATH: 5020/12000 4441 1042 221/6 1 320/219 229/426