Re: MIME encoding of headers
Christer Borang <[email protected]>
| Newsgroups | gmane.mail.exmh.devel |
|---|---|
| Message-ID | <[email protected]> |
In message <[email protected]>, [email protected] wr= ites: >Hi. > >I've noticed what I think is a bug in the way exmh encodes 8bit stuff >in headers. I'm using 2.6.3 with nmh 1.1rc3 on Solaris 9. Scratch that, after rereading the RFC, I noticed that whitespaces between encoded-words sholdn't be displayed, and thus the _ is necessary. Looks like yahoos mail isn't quite RFC-compliant (surprise!). Mea culpa. However, in displaying this emails, exmh keeps the spaces (and newlines, where applicable). The scan listing looks fine, but in the actual display, there are extra spaces. And now for something completely different... 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? Quoted-printable default (automatic, always and never) either QP-encodes everything or nothing. //Christer -- | Sys admin @ MEDIC WWW: http://www.dtek.chalmers.se/ | | Email: [email protected] Phone: (0)31 772 5431, (0)707 53 57 57 | "I fought the loa and the loa won, I fought the loa and the loa won..." -- Dave Aronsson, a.s.r.