Hello mark!   
      
   31 Mar 2012 14:00, mark lewis wrote to Tommi Koivula:   
      
    ml> X-JAM-FTSKLUDGE: CHRS: UTF-8 2   
    ml> Content-Type: text/plain; charset=iso-8859-1; format=flowed   
    ml> Content-Transfer-Encoding: 8bit   
      
   the above is an example on not working jamnntpd setup, oh no no no no :=)   
      
   ftn user posted unicode, and you toold jamnntpd to send it to nntp client as   
   latin-1   
      
   this will never work   
      
   better is to let utf-8 to utf-8 in jamnntpd so if ftn user post unicode any   
   nntp client can read it without any problem, but nntp client must newer post   
   in unicode, since jamnntpd / fidonet does not support it, even if it did, we   
   would loose chars in trying to, i love the reject on posting utf-8 in jamnntpd   
   :)   
      
      ----- post-rejected.txt begins -----   
   14-Mar-12 06:41:09 (127.0.0.1:39751) POST failed (Unsupported charset "UTF-8")   
      ----- post-rejected.txt ends -----   
      
      
    Regards Benny   
      
   ... there can only be one way of life, and it works :)   
      
   --- Msged/LNX 6.2.0 (Linux/3.1.10-gentoo-r1 (i686))   
    * Origin: home.junc.org where qico is waiting (2:230/0)