-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday, August 13 at 05:36 PM, quoth Kai Grossjohann:
>Here is the entire header listing, as printed by 'h'. I've replaced
>the values of the irrelevant headers with -snipped-.
>
>Received: -snipped-
>Received: -snipped-
>Delivered-To: -snipped-
>Received: -snipped-
>Message-ID: -snipped-
>From: -snipped-
>To: -snipped-
>Subject: -snipped-
>Date: -snipped-
>Mime-Version: 1.0
>Content-Type: text/plain; format=flowed
>Content-Transfer-Encoding: 8bit
>
>In this case, the message is in UTF-8 encoding.
How truly bizarre. Any idea what messed-up client sent this?
I'm not sure why assumed_charset is being ignored here... my only
guess is that because it's got a Content-Transfer-Encoding header, the
assumed_charset list isn't being consulted (which seems an odd choice
for mutt to make). I'd ask the author of the assumed_charset patch,
Takahashi Tamotsu; it *may* be a bug.
~Kyle
- --
Unthinking respect for authority is the greatest enemy of truth.
-- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFGwIMdBkIOoMqOI14RAgq6AJ0Uq/cVnQ0vBxXHnVdKVPU+me6k5QCfa1Lb
g2j4CJaoesymEIA0j7Sq4kw=
=R9dZ
-----END PGP SIGNATURE-----
