If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Incorrect Mail Body Displayed

RESOLVED INCOMPLETE

Status

Thunderbird
Message Reader UI
RESOLVED INCOMPLETE
6 years ago
5 years ago

People

(Reporter: nigelord, Unassigned)

Tracking

(Blocks: 1 bug)

9 Branch
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

186.71 KB, application/octet-stream
Details
(Reporter)

Description

6 years ago
Created attachment 587698 [details]
Screen Dump to Explain Issue

I have reported this behaviour previously (1-2 years ago) on an older version of TB but cannot find Bug Ref. Also it is similar to #239665 but I have reposted as that bug flagged as Resolved.

When I select an email from the Inbox a different mail is displayed in the bottom pane and also in the eMail tab if the mail is double clicked. See attachment: the mail selected has subject starting "Ask Leo! #317..." The mail actually displayed is the one 2 items above it in the Inbox with subject starting "The Latest Job on IT Computing".

TB v9.0.1
Win XP SP3
Email account is POP3

Comment 1

6 years ago
(In reply to nigelord from comment #0)
Please start Thunderbird in safe-mode and check: http://support.mozillamessaging.com/en-US/kb/Safe-Mode
(Reporter)

Comment 2

6 years ago
Problem persists in safe mode.
Does compacting the folder and rebuilding it's indexes solves the issue ?
(Reporter)

Comment 4

6 years ago
No - I've done a compact and it is still the same.
(In reply to nigelord from comment #4)
> No - I've done a compact and it is still the same.

and did you rebuild the folder too ? (folder -> properties : repair folder)
(Reporter)

Comment 6

6 years ago
(In reply to Ludovic Hirlimann [:Usul] from comment #5)
> (In reply to nigelord from comment #4)
> > No - I've done a compact and it is still the same.
> 
> and did you rebuild the folder too ? (folder -> properties : repair folder)

No I didn't. I've since inadvertently moved the email which was causing the issue to another folder so cannot now reproduce the problem. In its new folder it displays correctly.
(In reply to nigelord from comment #0)
> When I select an email from the Inbox a different mail is displayed in the
> bottom pane and also in the eMail tab if the mail is double clicked. See
> attachment: the mail selected has subject starting "Ask Leo! #317..." The
> mail actually displayed is the one 2 items above it in the Inbox with
> subject starting "The Latest Job on IT Computing".

This indicates that Tb thinks offset where mail of '2 items above it in the Inbox with subject starting "The Latest Job on IT Computing"' is located == offset of mail of "Ask Leo! #317...".
Phenomenon like it can easily be reproduced by next tests;
(1) test with drafts mails of same size.
    deleted draft mail at offset=A,     mail size=M,
    draft mail-1       at offset=A+M,   mail size=M,
    draft mail-2       at offset=A+2*M, mail size=M,
    edit draft of mail-1 at offset=A+M
    compact Drafts => mail-1 is moved to offset=A, mail-2 is moved to offset=A+M
    save new version of draft mail-1
    => tb deletes previous version of mail-1 at offset=A
    => mail-2 at offset=A+M is deleted
(2) Replace mail folder content without file size change.
    mail-x is placed at offset-X of file named FolderX,
    FolderX.msf is recreated by Repair Folder.
    While Tb isrunning and FolderX is opeed, edit file named FolderX,  
    move other mail's data(call mail-y) to offset=X
    without file size change of FolderX file. (timestamp only is changed)
    Click mail-x at thread pane => data of mail-y is shown.

Phenomenon you saw looks very similar to above (2).
Show "Order Received" column(offset of mail data in mail folder file if local mail folder) and sort by "Order Received" column. What value is shown for the two mails?

Above (2) occurs due to mail.db_timestamp_leeway(default=4000, perhaps in seconds). "Outdated msf condition" occurs only when "(a) folder file size is changed" && "(b) difference of file's timestamp >= db_timestamp_leeway". (b) is for workaround of issue in network file system.
In above (2), if "Repair Folder"(Rebuild Index) is invoked, proper mail's offset is obtained again.
Even if such problem occurs, rebuild-index will be invoked sooner or later if mail folder file size is changed by append of another mail data, and correct mail data will be shown sooner or later, unless Compact is executed while such mismatch between folderX and folderX.msf exists.

It may be next;
- Compact is executed
- End of compact is not notified to mail window,
  or mail window fails to detect End of Compact,
  or mail window fails to detect modification of mail folder file content
  when mail folder file size is not changed after Compact
  due to existence of db_timestamp_leeway.
  (e.g. Just after file size was reduced X MB, mail of X MB was appended)

What happens if you execute same test as above (A) when you saw your problem?

What is auto-compact related setting?
  mail.prompt_purge_threshhold
  mail.purge_threshhold_mb
  mail.purge.ask

If you don't use network file as Tb's mail folder file and use local HDD only for Tb's mail folder file, and if you don't share the local HDD by Win, Linux, Mac OS(dual boot, share using Virtual Machine), mail.db_timestamp_leeway=0 is a workaround of phenomenon like above (2).

By the way, please don't use Word document for merely attaching screen shot or text data to bug of B.M.O. Save as widely used .jpg, .png, .tif, .txt .htm, .eml etc. and attach, please.

Updated

5 years ago
Blocks: 714489

Updated

5 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(nigelord)
Resolution: --- → INCOMPLETE
(Reporter)

Comment 8

5 years ago
I don't know what more I can add. As explained above I have deleted the offending emails. The original problem occurred almost a year ago and has not recurred since. Also I am now on a later version of Tb (15.0.1). 
WADA's detailed response indicates he think he knows how it could have happened and that he thinks he can reproduce it. Unfortunately because I have now deleted the mails that originally caused the problem I cannot offer proof that this was indeed the cause.
Flags: needinfo?(nigelord)
You need to log in before you can comment on or make changes to this bug.