MSGID: 2:5020/12000 4f539241   
   REPLY: 1:154/10 67d4c548   
   TZUTC: 0300   
   CHRS: UTF-8 4   
   Hello Nicholas,   
      
   orig.message to echo UTF-8 on 14 Mar 25  18:52:22   
    NB> This is true, however.. that's the fault of those sysops. I've found the   
    NB> best working method has been to 'assume' any message with *no* chrs kludge   
    NB> is CP437, since it probably comes from a BBS package with ANSI support.   
      
   Not so easy for me. At first, I must distinguish CP866 and CP437.   
   At second, there is a little fraction of messages with latin-1 encoding - not   
   so serious, but some symbols got trashed if wrong charset choosed.   
   There was messages in encoding that I call "fido-relics" - with 8D byte used   
   as soft-CR.   
   And some amount of messages with encodings such as CP1125 - if decoded as   
   CP866 some letters are displayed wrong.   
   Using that fact that each echo area has own language - I use per-echo default   
   encodings.   
      
   Sergey   
      
   ... vim   
   --- PyFTN   
    * Origin: fluid.fidoman.ru (2:5020/12000)   
   SEEN-BY: 4/0 50/109 90/0 105/81 106/201 128/187 153/7715 154/110 218/700   
   SEEN-BY: 221/1 6 226/30 227/114 229/110 114 317 426 428 470 700 705   
   SEEN-BY: 280/464 291/111 301/1 113 812 320/219 341/66 234 900/0 902/0   
   SEEN-BY: 902/26 905/0 5015/46 5020/715 830 848 1042 2065 4441 12000   
   SEEN-BY: 5030/49 1081 1474 5058/104 5061/133 5097/31   
   PATH: 5020/12000 4441 1042 301/1 341/66 902/26 229/426