TZUTC: -0600   
   MSGID: 264.tuxpower@1:154/700 2bfd6729   
   REPLY: 2:280/464.113 6796e534   
   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 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)   
   SEEN-BY: 10/0 1 103/705 104/119 105/81 106/201 120/616 124/5016 128/187   
   SEEN-BY: 153/757 7001 7715 154/10 30 50 110 700 203/0 214/22 218/0   
   SEEN-BY: 218/1 601 700 840 850 860 880 940 220/20 90 221/0 6 226/18   
   SEEN-BY: 226/30 44 50 227/114 229/110 114 206 300 317 400 426 428   
   SEEN-BY: 229/470 664 700 705 240/1120 5832 266/512 280/464 5003 291/111   
   SEEN-BY: 292/8125 301/1 310/31 320/219 322/757 341/66 234 342/200   
   SEEN-BY: 396/45 460/58 467/888 633/280 712/848 770/1 902/26 2320/105   
   SEEN-BY: 3634/12 5020/400 5075/35   
   PATH: 154/700 10 280/464 103/705 218/700 229/426