TZUTC: -0600
MSGID: 266.tuxpower@1:154/700 2bfeb5bc
REPLY: 2:280/464.113 6798479e
PID: Synchronet 3.20c-Linux master/1cce91446 Jan 26 2025 GCC 14.2.1
TID: SBBSecho 3.23-Linux master/1cce91446 Jan 26 2025 GCC 14.2.1
BBSID: PHARCYDE
CHRS: ASCII 1
NOTE: NeoMutt/20250113-dirty
Hey Maurice!

On Tue, Jan 28 2025 02:57:34 +0000, you wrote ..

>> This one will probably go out as ascii
 
> That is what I see.  Near as I can tell my reply to you is also ascii 
> but given that 7-bit ascii is part of utf-8 this isn't really an issue 
> as this reply is evidence of.

Yep, understood. However, if whatever I'm using wants to auto-detect and slap
the proper charset on the message, so be it (as long as it's correct, of
course). This has been the case so far with slrn, tin, and now neomutt (and I
think I like the latter the best, so far.. probably because it's the only one
of the three that does email *and* nntp).
 
>> I have working email client that supports html in my Linux console
>> (automatically viewing in lynx)
 
> Excellent!  links should also work straight out of the box.  I have 
> both here.

Which do you prefer? Do you have an 'off the top of your head' list of pros
and cons as your reasoning for keeping both around? Or, is it just to have
options? :)

Regards,
Nick

... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
SEEN-BY: 4/0 80/1 90/0 93/1 103/705 104/119 105/81 106/201 120/616
SEEN-BY: 124/5016 128/187 153/757 7001 7715 154/10 30 50 110 700 203/0
SEEN-BY: 218/700 220/20 90 221/0 6 226/18 30 44 50 227/114 229/110
SEEN-BY: 229/114 206 300 317 400 426 428 470 664 700 705 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 291/111 292/8125 301/1 310/31
SEEN-BY: 320/219 322/757 341/66 200 234 342/200 396/45 460/58 467/888
SEEN-BY: 633/280 712/848 770/1 900/0 102 106 902/0 19 26 905/0 2320/105
SEEN-BY: 3634/12 5020/400 5075/35
PATH: 154/700 10 280/464 341/66 902/26 229/426