GNOME Bugzilla – Bug 496390
email header was not decoded right in some mails
Last modified: 2013-09-13 00:59:57 UTC
https://bugzilla.novell.com/show_bug.cgi?id=338747 The subject was not decoded right in Evolution. I pasted the subject text here. Subject:=?UTF-8?Q?=20File=20=E2=80=9CFolder=2DTree=2D?= =?UTF-8?Q?Expand=2DState?=.=?UTF-8?Q?Xml=E2=80=9D=20Holds=20Proxied=20?= =?UTF-8?Q?Folder=20As=20Last=20Folder?= Could be gtkhtml rendering issue.
Created attachment 99012 [details] Mbox file which causes problem
Yeah, because the subject string is not RFC2047-compliant. not a bug at all.
Yes, it is not RFC2047-compliant. Also there is an instruction on these kind of problems, see the following words: http://www.faqs.org/rfcs/rfc2047.html 6.3 A mail reader need not attempt to display the text associated with an 'encoded-word' that is incorrectly formed. However, a mail reader MUST NOT prevent the display or handling of a message because an 'encoded-word' is incorrectly formed. But the fact is some mail servers or mail clients do not strictly following the RFC, especially in this bug. I know it is not the fault of Evolution, but isn't it better to encode such mis-decoded strings? Maybe we can take this as an usability problem.
(In reply to comment #3) > but isn't it better to encode such mis-decoded strings? if you tell me about the algorithm who can guess how to decode such malformed strings... ;-)
the problem is that no matter how hard you try, you'll never be able to handle all forms of brokenness otu there that some mail client or another might send. It gets even harder when you have to make sure that you correctly handle valid encodings.
*** Bug 501151 has been marked as a duplicate of this bug. ***
*** Bug 502178 has been marked as a duplicate of this bug. ***