Bug 504636 (thread-index)
Summary: | [RHEL5] Mail sent via Red Hat Blackberry system breaks threading | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Joel Berman <jberman> | ||||
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
Status: | CLOSED WONTFIX | QA Contact: | desktop-bugs <desktop-bugs> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.5 | CC: | jberman | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-06-02 13:18:28 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: | |||||||
Attachments: |
|
Description
Joel Berman
2009-06-08 15:46:15 UTC
Can you post a sample reply message that was composed on the Blackberry? Evolution does threading based on "References" and "In-Reply-To" message headers, so I want to see if the Blackberry is generating either of them. Reporter, could you please reply to the previous question? Thank you. Created attachment 413684 [details] returned email Yes, this is very clearly problem on Blackberry's side. Instead of using standard In-Reply-To header it tries to follow Microsoft Exchange even in parts where Microsoft admits to have a bug (see http://support.microsoft.com/kb/908027/en-us?fr=1). Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in the last planned RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX. To request that Red Hat re-consider this request, please re-open the bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you. Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support). The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |