[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Mutt/locale question: charset=unknown-8bit causing problems for some MUAs?



I've got a correspondent who's reporting problems reading mail I'm
sending, because, he claims, of mutt's Content-Type encoding:

> 
> > Content-Type: text/plain; charset=unknown-8bit
> 
> Could you possibly specify a correct character set on your emails;
> Outlook/Exchange, for once, does something reasonable with unknown
> ones, see below.
> 
> > Content-Disposition: inline
> > Content-Transfer-Encoding: quoted-printable
> 
> unknown-8bit is the likely result of sending 8 bit text without
> specifying a character set (as us-ascii, the default, is 7 bit);
> you may be just be sending content-transfer-encoding: 8 bit, or you
> may be sending actual 8 bit characters.  (It could be that the
> list server requires a character set for MIME, or assumes that 
> quoted-printable implies non-ASCII.)  The fault, for once, is not
> with Outlook or Exchange.


I suspect a locale issue, unless, of course, the fault really *is* with
Outlook/Exchage.  Current results for 'locale':

    $ locale
    LANG=POSIX
    LC_CTYPE="POSIX"
    LC_NUMERIC="POSIX"
    LC_TIME="POSIX"
    LC_COLLATE="POSIX"
    LC_MONETARY="POSIX"
    LC_MESSAGES="POSIX"
    LC_PAPER="POSIX"
    LC_NAME="POSIX"
    LC_ADDRESS="POSIX"
    LC_TELEPHONE="POSIX"
    LC_MEASUREMENT="POSIX"
    LC_IDENTIFICATION="POSIX"
    LC_ALL=

Any mail / content-type gurus out there know what's going on, whose
mailer's puking on this, and/or what's wrong with my locale &/or mutt
settings?

Thanks.

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
   NextDraft:  Your Dinner Party Prep:  http://www.nextdraft.com/

Attachment: pgp65HqZIpWLL.pgp
Description: PGP signature


Reply to: