REPLY: 1:154/10 65f5c0fc
MSGID: 1:153/7001 65f5c42f
CHRS: UTF-8 4
Hey Nicholas!

 NB> I believe this client forces utf-8 when posting, which is fine.

From the PID I am gathering the client is nttp based.  I've run across similar
strategies here and there.  The output looks fine from this angle.

 NB> I do have other clients for testing purposes that can send it back
 NB> in CP866, but why?

Because we can?  Besides CP866 is one of the few encodings that they - whoever
'they' are - get right.

 NB> Be prepared to be in the fight for the long haul. :)

I've been doing so off and on and probably will continue as long as I have a
haul nevermind a long one.

Besides it isn't the size of the haul but the quality.  ;-)

Life is good,
Maurice

-o   -o    o-   o-  -o   -o    o-  -o    o-  -o   -o   -o    o-  -o   -o   -o
 (\   (\  /)   /)    (\   (\  /)    (\  /)    (\   (\   (\  /)    (\   (\   (\
 ^^   ^^  ^^   ^^    ^^   ^^  ^^    ^^  ^^    ^^   ^^   ^^  ^^    ^^   ^^   ^^
... Monig biþ uncuþ treowgeþofta, teorað hwilum.
    Many a trusted friend will prove to be unknown, will fail at times.
--- GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016
SEEN-BY: 128/260 135/225 153/757 7001 7715 154/10 30 40 50 700 203/0
SEEN-BY: 214/22 218/0 1 601 700 820 840 850 860 870 880 930 940 220/90
SEEN-BY: 221/0 6 226/18 30 70 227/114 229/110 112 113 206 307 317
SEEN-BY: 229/400 426 428 470 664 700 240/1120 5832 266/512 280/464
SEEN-BY: 280/5003 282/1038 291/111 292/8125 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 460/58 467/888 633/280 712/848
SEEN-BY: 770/1 2320/105 3634/12 5020/400 5075/35
PATH: 153/7001 154/10 280/464 103/705 218/700 229/426