I did a couple of tests myself. It seems that the error message is just badly chosen - the problem is not that gnubiff cannot convert us-ascii to UTF-8 but that the conversion fails because the original message isn't in the charset it claims to be (in that case us-ascii). Here are the testmails:
From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Testmail 1 blaaa works fine. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Testmail 2 blaaaä with UMlaut does not work. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Testmail 3 blaaaä with UMlaut works, simply deletes the invalid character. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Testmail 4 blaaa works. -- Can't convert us-ascii to UTF8 https://bugs.launchpad.net/bugs/161831 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
