Re: MIME encoding of headers

On Sun, 23 May 2004 18:44:13 +0200, Christer Borang <[email protected]>  said:
> I would like to tell exmh to use 8bit encoding in the body, but still
> have it qp-encode headers that need it. Unfortunately, it seems I
> can't do one without the other?

Blargh.

Unless somebody snuck an update to RFC2822 past me while I was out looking for
my morning caffeine, non-7-bit-clean headers must *always* be encoded (either
QP or =B or something), since there's no other way to pass the charset
information for a non-ascii glyph.

I haven't looked at the code yet, but this really should be refactored into two
parts - one for the body and one for headers.  I'm perfectly content to have
the default for bodyparts be "none", since my MTA is able to do conversion as
needed.  But "none" isn't acceptable for the headers unless the MTA and exmh
have a pre-existing agreement about what charset is in use...

(And I'm going to LART the first person who points out that "none" really isn't
an acceptable default for bodyparts because of the distinction between "binary"
and "8bitmime" ;)

_______________________________________________
Exmh-workers mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-workers

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFAshpPcC3lWbTT17ARAra+AJ0azqvvn0cfqlxVXJv/2ahEPiPqbACguzqn
TR8lOjrAMAP5/cRZXpfl8H8=
=0ttn
-----END PGP SIGNATURE-----