http://bugzilla.spamassassin.org/show_bug.cgi?id=3348
------- Additional Comments From [EMAIL PROTECTED] 2004-05-04 07:53 ------- Subject: Re: New: base64 encoded html messages seem to confuse get_uri_list On Mon, May 03, 2004 at 09:37:23PM -0700, [EMAIL PROTECTED] wrote: > I suspect it could be due to base64 encoding of the text/html message Hrm. Well, the problem is that it's an invalid message. The message headers say text/html that's base64 encoded, but the message body has a MIME boundary with headers saying text/html and base64. So our system goes "oh, the whole thing is base64 encoded" (which is what it's supposed to do) and tries to decode it, which will including trying to decode the invalid MIME boundary, then everything goes to hell. Here we go again with MUAs not simply doing what they're supposed to do (treat this as invalid), but trying to look through the part to display anything possible to the user. <grrr> MUA Behavior ----------------------- ----------------------------- Mutt Binary boundary, then HTML, then binary boundary Pine Binary boundary, then HTML, then binary boundary Apple Mail Text boundary, then HTML, then text boundary Outlook Express Binary gibberish Exchange WebMail Binary gibberish Opera Binary gibberish, includes "errors while decoding" msg As far as I can tell, this tells you how different MUAs do decoding. Mutt and Pine seem to go line by line. Apple Mail seems to also go line by line, but checks that the line is validly encoded first. The Windows-based MUAs (OE, WebMail, and Opera) all seem to just take the message body as a chunk and decode it, like we do. So... Anyone have thoughts about this? Part of me is inclined to leave things as they are, and the other part of me says we should emulate Apple Mail here and make as much valid/visible text as possible. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
