MSGID: 2:5020/12000 4f5391a7
REPLY: 2:280/5555 7b7b7a60
TZUTC: 0300
CHRS: UTF-8 4
Hello Michiel,

can you please, if you mark your message as "UTF-8", post erroneus string in
safe way, e.g. as hex dump, or replacing invalid codepoints with some
character like question mark?
If you copy from nodelist INVALID string with BINARY AS IS, it obviously makes
your message invalid too.
I was to forcibly mark your message as CP437 to read it, becouse trying to
decode it as UTF-8 ends with error.

orig.message to echo UTF-8 on 21 Feb 25  00:15:50
 MV> chkwf8 2.0.1 W32 UTF-8 well formed sequence test.
 MV> © 2015-2017, Michiel van der Vlist, PA0MMV (2:280/5555)
 MV>
 MV> File: dailyutf.052
 MV>
 MV> ,208,-=P=I=X=-,S?ve,Bj÷rn_Felten,46-31-960447,9600,CM,XA,V34
 MV> ^
 MV> 1430 lines read.
 MV> 1411 lines found with ASCII only.
 MV> 18 lines found with well formed UTF-8 sequences.
 MV> 1 line found with an ill formed UTF-8 sequence.
 MV> 0 lines found with a BOM.

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 124/5016 128/187
SEEN-BY: 142/104 153/757 7715 154/10 30 110 203/0 218/700 221/0 1
SEEN-BY: 221/6 226/30 227/114 229/110 114 317 426 428 470 700 705
SEEN-BY: 240/1120 2411 5824 5832 5853 5854 280/464 5003 5006 5555
SEEN-BY: 291/111 292/854 8125 301/1 113 812 310/31 320/119 219 319
SEEN-BY: 320/2119 322/762 341/66 234 423/120 460/58 467/888 712/848
SEEN-BY: 770/1 902/26 5015/46 5020/400 715 830 848 1042 2065 4441
SEEN-BY: 5020/12000 5030/49 1081 1474 5058/104 5061/133 5097/31
PATH: 5020/12000 4441 1042 301/1 280/464 240/5832 320/219 229/426