Subj : Re: quoting..
To   : Maurice Kinal
From : Nick Boel
Date : Mon Jan 27 2025 19:17:21

Hey Maurice!

On Mon, Jan 27 2025 01:45:24 +0000, you wrote ..

>> Last reply, I think I found a configuration error in .neomuttrc. So 
>> here goes another. :)
 
> Much better although no iconv was required since you are successfully 
> claiming UTF-8 which happens to be my default on everything I am 
> currently using for EVERYTHING, including the MSG format.

Yep. I noticed the issue in the first message, so I changed up my .neomuttrc by removing:

set send_charset "us-ascii:ibm437:iso-8859-1:utf-8"

Apparantly all of those characters were able to be translated to ISO-8859-1/LATIN-1 before it got to UTF-8. I understand the order I provided, but Synchronet gave it a CHRS: CP437 kludge for some reason. That's about the jist of what happened. Seems to be working better now with:

set assumed_charset = "ibm437"

... basically anything without a kludge or a Content-Type header would be assumed to be that, since I'm only using NNTP for FTN related things, anyways.

set charset = "utf-8"
set newsgroups_charset = "utf-8"

Incoming cp437 is still translates correctly by iconv, so as long as I reply to it correctly I should be off to a good start. Neomutt should auto-detect my outgoing message and slap a proper content-type header on it, which Synchronet should be able to read and apply the proper CHRS kludge for FTN. This one will probably go out as ascii, since there is no CP437 or UTF-8 in the message.

By the way, Neomutts provided neomuttrc is over 7k lines. I didn't realize I was punishing myself when I decided to install it and give it a go. :)

Either way, now I have working email client that supports html in my Linux console (automatically viewing in lynx), as well as a nice console NNTP client that supports mime. So a win for me, in my opinion! :)
 
Regards,
Nick

.... He who laughs last, thinks slowest.
--- SBBSecho 3.23-Linux
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

.