Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    JAMNNTPD    |    Support for the JAMNNTPD software client    |    2,630 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,945 of 2,630    |
|    Tommi Koivula to Fabio Bizzi    |
|    Unsupported Charset    |
|    30 Jul 19 12:07:36    |
      MSGID: 2:221/6.0 5d4008d2       REPLY: 2:335/364.1 5d3ff117       PID: SmapiNNTPd/Linux/IPv6 1.3 20190718       CHRS: UTF-8 2       TZUTC: 0300       TID: hpt/lnx 1.9.0-cur 2019-07-09        >>> From Fabio Bizzi To All        > Hello All!        > 29 Jul 19 15:04, I wrote to you:        > FB> I'm doing tests with smapinntpd, I switched from Thunderbird to PAN to        > FB> see if the TO: field is ok with PAN but when I try to post a message I        > FB> get this in the log of the server:        > FB> POST failed (Unsupported charset "UTF-8")        > FB> How can I do to support the UTF-8 charset?        > Ok, RTFM always works. :)        > UTF-8 posting is always unsupported! :(        > And PAN has a bug, also if you set another charset it posts always in utf-8.        > Now I'll try with another reader. Any Suggestion? (Platform Linux).       Nope, docs are outdated, posting utf8 works fine. See my kludges.              I'll post my config asap. Now mobile only.              You may try claws mail or sylpheed. I like sylpheed. ;)              --- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1557368964000       HotdogEd/2.13.5        * Origin: smapinntpd/linux @ nntps://news.fidonet.fi (2:221/6.0)       SEEN-BY: 1/123 15/2 154/10 203/0 221/0 1 6 360 226/17 227/114 229/354       SEEN-BY: 229/426 452 1014 240/5832 249/206 317 280/464 5003 5555 310/31       SEEN-BY: 317/3 322/757 342/200       PATH: 221/6 1 280/464 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca