MSGID: 2:280/464.47 5dad4d7a   
   REPLY: 2:221/1.11 dd918e11   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0200   
   TID: CrashMail II/Linux 1.7   
    TK> Oli wrote:   
      
    >> Is it possible to send a correct CHRS kludge with jamnntpd. My jamnntpd   
   server   
    >> always uses   
    >> CHRS: UTF-8 2   
      
    >> but the correct one would be   
    >> CHRS: UTF-8 4   
      
    TK> There is no level 4 support in JamNNTPd. No one has bothered to fix   
    TK> that. But it really doesn't matter, everything works ok even with that   
    TK> "UTF-8 2" kludge.   
      
   Why have standards, if they are ignored anyway? ;)   
      
   I already assumed that most software works fine with "UTF-8 2", but I was not   
   sure and it didn't feel right to have a non-conforming kludge in the message.   
   But if everyone says it's fine, I can relax.   
      
    TK> Btw, your JamNNTPd is sending only the first three letters of your name.   
   :)   
      
   It's not JamNTTPd fault, it uses the name from the From field. In another   
   network I'm using my nickname. Maybe I need to use separate NNTP accounts for   
   every network / different names. But why bother, everyone can read my messages   
   and my full name is in the pointlist ;).   
      
   ---   
    * Origin:  (2:280/464.47)   
   SEEN-BY: 1/123 15/2 154/10 203/0 221/0 227/114 229/354 426 452 1014   
   SEEN-BY: 240/5832 249/206 317 280/464 5003 5555 310/31 317/3 322/757   
   SEEN-BY: 342/200   
   PATH: 280/464 229/426