Closed Bug 467603 Opened 17 years ago Closed 17 years ago

yahoo webmail shows confusing characters rather than html on some emails, such as invoices from newegg.

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: skuraq, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20081201 Shredder/3.0b1pre I click on an email from newegg, an invoice or info, I get characters like this: �`�L��P����/� 0�L���T�j{"�*'j_��m����0ފ��4�٥��h�ǝ��m�X^i�b�W�{���&�ح���y�[�ܬ�)^3�Ҝmi�^q�eJ���x�ǥ��v)�Lv���('ǵ�ۢ�^� n�r��]���z�r��9�E=)���FD��OJq�C�?Jq<�L�4�ҜA9�D�OJq<�jQޖ�Ƭj{,z��q�eJ���x�ǥ��v)�Lv���('ǵ�ۢ�^� n�r��]�'m� �0J��f������� ��� r���w^ū)�y�p0$���b��i�"�I��ri�p0$���b��i�"�J�u�� { I can fix it temporarily by going into View-Character Encoding-Auto Detect-Universal. I get header info that should be hidden and the html body of email. If I go to a different email and back to this, it becomes gibberish again. This has been happening since 2.0.0.16 or earlier. Note, the current yahoo webmail does not work with the current build, so I cannot get new emails. Reproducible: Always Steps to Reproduce: 1.get email from newegg 2. open to view, gibberish 3.View-Character Encoding-Auto Detect-Universal and it is temporarily fixed, reverts back Actual Results: �`�L��P����/� 0�L���T�j{"�*'j_��m����0ފ��4�٥��h�ǝ��m�X^i�b�W�{���&�ح���y�[�ܬ�)^3�Ҝmi�^q�eJ���x�ǥ��v)�Lv���('ǵ�ۢ�^� n�r��]���z�r��9�E=)���FD��OJq�C�?Jq<�L�4�ҜA9�D�OJq<�jQޖ�Ƭj{,z��q�eJ���x�ǥ��v)�Lv���('ǵ�ۢ�^� n�r��]�'m� �0J��f������� ��� r���w^ū)�y�p0$���b��i�"�I��ri�p0$���b��i�"�J�u�� { Expected Results: view html based email work like it does on the yahoo mail website.
Bugzilla is for the tracking of bugs in Thunderbird and other mozilla applications. The Yahoo webmail add-on is not part of Thunderbird and you should contact the authors about your issues.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.