From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Tue, 30 Oct 2007 13:39:43 -0700 Subject: [sup-talk] Also, seems to be throwing lots of invalid encoding errors In-Reply-To: <671354B2-98BF-4CE7-B8AC-7C55581C46BB@foundinteractive.com> References: <671354B2-98BF-4CE7-B8AC-7C55581C46BB@foundinteractive.com> Message-ID: <1193776545-sup-5951@south> Excerpts from Timothy Johnson's message of Fri Oct 12 10:51:41 -0700 2007: > Any fixes for this error? > warning: error decoding message body from "iso-8859-1": invalid > encoding ("utf-8", ""iso-8859-1"") > and variations on that message. I'm pretty sure this is just iconv being finnicky. I think it happens when there's something about the message that it doesn't like when converting between those two character sets. At any rate, it's not fatal and I'm not sure that there's really a good solution without rewriting the Ruby iconv bridge, which is basically a one-method API. -- William