79458 - Subject mixup between mails

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Francisco León]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.4 i686; en-US; rv:0.9) Gecko/20010505
BuildID:    2001050521

I was receiving an email from bugzilla but it showed up
the subject of the prior message i was reading

Reproducible: Didn't try
Steps to Reproduce:
1.Read a normal mail
2.Get new mail automatically (not manually)
3.Read the new mail

Actual Results:  I saw the new mail with the other message's subject

Expected Results:  Expected to see the subject of the mail i was reading.
After clicking on another message and clicking back on the
one that had problems, got fixed

Not really an important one, but i saw this one as i was getting
replied from another bug :)

Comment 1

[timothy.keitt]

I also get this behavior, mostly when reading folders that have had messages
appended by procmail.  It seems that mozilla is failing to scan and do sanity
checks on IMAP (and other?) mail folders, i.e., it assumes that only mozilla is
touching these files, which is a poor assumption.  Build = 2001060713

Comment 2

[Francisco León]

I saw this on pop mail, never have used local mail or imap mail
This one is really hard to reproduce, i have seen it like 3 times in 2 months,
it's really not bothering me, but it still is a bug and i posted it for people
to know

This may be fixed then mail headers are reworked (too bad this will only happen
in 1.0)

Comment 3

[timothy.keitt]

The problem is actually worse.  I'm getting the wrong message body attached to
new incomming emails, such that I cannot read them!  I think what is happening
is that email marked as deleted, but not expunged, is still getting read in a
message bodies, but the header is not picked up because its marked deleted.  The
result is more message bodies than headers.  Sometimes after deleting all
messages in a folder, I get left-over header-less message bodies that I can't
delete.

Comment 4

[Francisco León]

Yes, i have had the same behavior you describe, but as i said, very hard to
reproduce. Havent seen it in weeks

Comment 5

[Oskar Berggren]

I'm seeing this as well (mz0.9.6 and build id 2001121221 tested). A few (three) rows in the mail summary pane (of my INBOX) show data that apply to
messages that have already been deleted and expunged (by another mail client).
When clicking on them, the message pane shows the header and body of three
different messages. These "displayed" messages are messages that I know do 
exist in the folder and they are not shown on any other row. Using 
quicksearch after a word included in the subject of the displayed message _does_not_ give any matches.

I'm using IMAP(SSL).

Using pine to access the folder directly gives expected result. Examining
the mail folder in an editor reveals that the deleted/expunged messages is
in fact expunged. I can find no traces of it in the folder file.

However, if I examine ~/.mozilla/default/ImapMail/<secret>/INBOX.msf I
am able to locate the header of the deleted message. On the other hand I
can only find the header of one (out of three) of the displayed messages
in that file.

Comment 6

[Scott Davis]

Is anybody working on this bug? I've seen it a few times (on Solaris), but have
never worked out how to reproduce it on demand. The latest time is on Mozilla
1.0RC3 (build ID 2002052414).

This time, I got bitten by replying to the mail with the older header, and the
response was sent to the originator of the header, not the send of the mail I
was responding to :-( This could be a MAJOR enbarrassment/stuffup (the mail I
was responding to was from my wife - the recipient was a colleague).

Comment 7

[Tony Mechelynck [:tonymec]]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1pre) Gecko/2008062001 SeaMonkey/2.0a1pre

WFM.

Anyone still seeing this?

Comment 8

[Tony Mechelynck [:tonymec]]

Resolving WORKSFORME for lack of any response to comment #7 after more than two months. If you want to REOPEN, please copy the "build identifier" from the about: page of the _current_ build in which you see the bug.