User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 Hello, Happens on both Windows and GNU/Linux client, version 1.5.0.5 Sample headers that should be displayed in Hebrew: =?UTF-8?B?15TXqNep157XqiDXkden16jXmdedINei16bXnteZ16o==?= =?UTF-8?B?15PXl9eZ15nXqiDXlNeW157XoNeqINeR15nXp9eV16jXqjog15PXldeq158g157XlteV16gsINen16DXmdeV158g16jXnteqINeQ15HXmdeR=?= The given link shows that this is a long-time problem. The same Emails are received correctly in Outlook and Outlook express. The content displays correctly. http://mail.python.org/pipermail/python-bugs-list/2004-December/026589.html Reproducible: Always Steps to Reproduce: This is some encoding problem, that happens only with certain Hebrew Emails. Tried to tell TB to force encoding of UTF-8 in *all* incoming mail, but it still shows wrong. I have put it as a major severity bug, since a message subject is most important, and this specific problem has been here for a long time. May be related to this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=345580

Probably a dupe of bug 227290

Yes, it is. Both encoded words have an extra '=' at the end. The first is an example of case 1 (in bug 227290 comment #11) and the second is an example of case 3 *** This bug has been marked as a duplicate of 227290 ***

Yes, it is. Both encoded words have an extra '=' at the end. The first is an example of case 1 (in bug 227290 comment #11) and the second is an example of case 3. As for the Python bug mentioned in comment #0, Python mail module has two bugs. One is that it uses RFC 2047-style encoding in C-D header field where it MUST use RFC 2231-style encoding. (that is not related to this bug directly). The other is that it adds a superfluous '=' at the end when using B-encoding. Please, tell Martin V. Lowes to fix *his* bug (if he's in charge).

(In reply to comment #3) > As for the Python bug mentioned in comment #0, Python mail module has two bugs. > One is that it uses RFC 2047-style encoding in C-D header field where it MUST > use RFC 2231-style encoding. (that is not related to this bug directly). The > other is that it adds a superfluous '=' at the end when using B-encoding. Reading the python bug report more carefully, I realized that I was wrong about the second bug of Python mail module. The problem is that it apparently does not have an API to deal with a mail header field with parameters. It needs something like |add_header_with_parameter(string, dict)| where 'dict' is a dictionary of parameter and its value and 'string' is the name of a header field. > Please, tell Martin V. Lowes to fix *his* bug (if he's in charge). This is still the case. It's not us but Python mail module that needs to be fixed.