Bug 236741
Summary: | Broken From because of incorrect RFC 2047 encoding and decoding | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Bieringer <pb> |
Component: | thunderbird | Assignee: | Gecko Maintainer <gecko-bugs-nobody> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | mcepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-05-22 13:53:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Bieringer
2007-04-17 14:06:07 UTC
Yup, can confirm that the message is broken in Thunderbird, while mutt displays it just fine, thank you. We found that this bug has been already registered in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=254519) and believe that it is more approriate to let it be resolved upstream. Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. BTW: makes it sense to close bugs with "CLOSED UPSTREAM" while it's known that the bug isn't fixed in upstream yet? Probably a better status would be "WAITFOR UPSTREAM". It is not "CLOSED UPSTREAM", but CLOSED (reason being UPSTREAM), take a look at the definition https://bugzilla.redhat.com/bugzilla/page.cgi?id=fields.html#upstream And concerning WAITFOR UPSTREAM -- well, we are not that anxious, when it will be fixed upstream, it will come to us automagically, so for us working on this bug is basically finished. |