On Tue, Dec 09, 2003 at 04:36:53PM -0500, David Yitzchak Cohen wrote: > On Tue, Dec 09, 2003 at 01:25:18PM -0200, Carlos Laviola wrote: > > On Tue, Dec 09, 2003 at 04:07:08AM -0500, David Yitzchak Cohen wrote: > > > > > > Can you try sending me a problematic email? I get loads of email from > > > all kinds of sources, and I haven't noticed any trouble with most mails > > > that aren't deliberately mislabeled by the sending MUA (like Outlook > > > likes to do, for instance). Mutt simply assumes ISO-8859-1, AFAIK. > > > > Well, sure. There's a compressed maildir folder at > > > > http://carlos.sna.cx/mutt/problematic_message.tar.gz > > I took the message from there, and sendmail(1)ed it to myself. > Sure enough, it didn't display properly, so I had to ^E on it. > Even with that, though, the subject doesn't show up properly. (I have > rfc2047_parameters set, BTW. The subject isn't individually encoded, > though, so that has no effect here.) Notice that the message itself > isn't in MIME at all, so I believe a recent post (with a patch) to the > mutt-dev list applies here: without MIME, Mutt essentially doesn't allow > internationalized headers, unless you apply his patch (which uses the > body charset for the header). If you want, I'll forward you the post. > (The web-based archives for this list suck, so you're almost certainly > better off letting me forward the copy from my own archives to you.) I'd really appreciate that patch. I could also forward it to Debian's mutt maintainer. > > Notice it lacks Content-Type, for instance... > > It lacks MIME, plain and simple. It's technically a pre-MIME message, > and Mutt has a totally different set of rules for it :-( Oh, I see. I should read the appropriate RFCs... > > Yeah, that might be a bug in the version I run. (that has been fixed > > already?) > > beats me ... if you can forward me a sample message, I can try doing > \e\n on it and report what happens. . . > > > I guess I'll just compile mutt by hand and find out for myself, but > > please check anyway :-) > > done :-) I've checked that same message against mutt cvs head and the problem persists, so... Please send me the patch :-) Thanks again, -- Carlos Laviola <carlos@xxxxxxxxxxx>
Attachment:
signature.asc
Description: Digital signature