Closed Bug 239665 Opened 21 years ago Closed 17 years ago

displayed message header does not belong to displayed body (or vice versa)

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: hcvoges, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 This behaviour might be close related to bug #218123 or #230055. Occasionally, when I open a folder on an IMAP server (occurred on GMX.de imap most often), the displayed message header does not match the displayed message body. Whereas the header seems to be the right one but the body is either one of an formerly deleted message or another message that is not being displayed any more. A simple restart of TB does not help nor does taking TB offline and then online again. I deleted the TB's temporary mail data in documents and settings/[user]/application data/thunderbird/profiles/.../ImapMail to force TB reload all header data from the server. After that, I can again retrieve the correct header/body of the email. Reproducible: Sometimes Steps to Reproduce: Unfortunately, I could not find out a reliable way to reproduce the behaviour. However, the problem occurs always after a while of working.
This may related to 218123, 230055,234433, 260588, 257134 and 265268. Platform: Server: The server we used seems to be Lotus Workplace which seems to reboot from time to time - I am not in control of it. Client: TB 1.0 on NT4.0 The message body does not match the title. Not all titles are shown in the UI - I can see all title in outlook express. Set connection cache to 1 does not help(suggested in 230055)- I do have a lot of folders at server. Delete local TB temp file does not help. Reproducible: always
When I click on some message header, I receive the following error message: The current command did not succeed. The mail server responded: FETCH CLHAC0019E: Invalid message set
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Haven't seen this for quite a while (a few months now). So works for me. Currently using Thunderbird nightly trunk on Mac OS 10.4 but also haven't seen this anymore on the latest release versions of Thunderbird on Windows and Mac. All this with wu-imapd as the server.
Hmm, bugger. Should have read this automated message properly :) I shouldn't have responded. Sorry :D
Still the same problème under Thunderbird 1.5.0.5. I think there is a lot of bugs linked to that "mismatched bodies and headers" problem. This is a third one I see. Shouldn't all bug be linked together ?
Similar problem occurs reading news. Article body shown in mail window is different from that indicated by subject header, and turns out to be a completely different article in source view. This was noticed undr 1.0.7 and migrataed to a clean install of 3.0a1.
QA Contact: front-end
I do not experience the behaviour described above since (at least) Version 2.0.0.9 (20071031) of Thunderbird (platform mac os x 10.5.1). Works for me now.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Version: unspecified → 1.0
You need to log in before you can comment on or make changes to this bug.