@MSGID: 11826.fidotest@1:154/700 2dd5642e
@REPLY: 1:153/149.42 6F990A2A
@TZUTC: -0600
@PID: Synchronet 3.21b-Linux master/f6746e937 Jan 19
2026 GCC 15.2.1
@TID: SBBSecho 3.34-Linux master/f6746e937 Jan 19
2026 GCC 15.2.1
@BBSID: PHARCYDE
@CHRS: UTF-8 4
@FORMAT: flowed
@NOTE: Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:140.0) Gecko/20100101Thunderbird/140.7.0
Hey Matthew!

On Tue, Jan 20 2026 03:35:17 -0600, you wrote:

> This message should have the CHRS UTF-8 kludge.   Not sure this is
> the right approach though, maybe just plain old ASCII?

Yep, it has the CHRS kludge.

 However, if you want to get technical, you should send the CHRS
kludge that coincides with the message written. If the message includes
UTF-8, then send the CHRS: UTF-8 kludge. If it contains CP437 characters,
then it should be sent with the CHRS: CP437 kludge, etc.

 UTF-8 also works for, and completely covers ASCII.. so it is still
valid in this case.

 In most of my setups outside of my BBS itself, I just convert
everything to UTF-8, and always send that kludge. YMMV, though.

Regards,
Nick

... Sarcasm, because beating people up is illegal.
--- SBBSecho 3.34-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
SEEN-BY: 19/10 50/109 104/117 119 114/10 120/616
153/757 154/10 30 50 700
SEEN-BY: 218/840 220/20 90 221/1 6 360 226/18 44
50 1701 280/464 301/1
SEEN-BY: 335/364 341/66 234 460/58 463/68 2320/105
3634/12 5000/111 5015/46
SEEN-BY: 5020/715 846 848 1042 4441 12000 5030/49
1081 5058/104 5060/900
SEEN-BY: 5061/133 5075/128 5083/444
@PATH: 154/700 10 221/6 5020/1042 4441