On Tue, 2009-12-15 at 13:15 -0800, John Hardin wrote:
> On Tue, 15 Dec 2009, Martin Gregorie wrote:
>
> > BTW John, why does your MUA emit a textual MIME part with an X-UNKNOWN
> > charset every so often? Its pretty rare and so far I haven't been able
> > to see a pattern to it. Do you occasionally use a different MUA?
>
> I generally use PINE; occasionally I use Evolution, usually only if I want
> to look at image attachments without exporting them first.
>
> {researches a bit} Hmmm. It only appears to happen when non-ASCII
> characters are in the message I'm replying to. I have my locale set to
> en_US.utf8, maybe PINE doesn't try to figure out the right thing to do
> when I reply to a non-UTF8 message with accented characters or some such.
>
> I'll switch back to iso8859-mumble for a while and see if it happens
> again.
>
I just found an old message I've kept from April this year. It was sent
from PINE LNX 4.64. Its just the one text/plain MIME part that uses an
X-UNKNOWN charset. It it you were replying to Karsten Br<E4>ckelmann: as
you can see, there's an e umlaut in the attribution line, so that's most
likely the cause.
FWIW JavaMail 1.4.2 trips over it despite my use of a CharsetProvider to
substitute iso-8859-1 for it, which works if the charset is defined in
the mail headers but not if its in a MIME part. I notice that JavaMail
1.4.3 is now out, so I'll see if upgrading fixes the problem for MIME
parts. Your saved message will make a good real-world test.
Martin
