215677 - Slow arriving e-mail message not getting into proper thread hierarchy.

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[ISHIKAWA, Chiaki]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624

I have a subscription to a mailing list which delivers e-mail
messages rather slowly.
Sometimes, due to mail delivery strangeness, an e-mail
posted earlier arrived LATER than messages posted after it.

When an e-mail that starts a thread
arrives LATER than the responses to this
email, then
the thread hierarchy does not get started
and the responses to the original e-mail
are shown as orphaned messages without successor.

 (missing original that has not arrived)
 response-1  
 response-2
 response-3
 response-4

But this persists EVEN AFTER the original message
that starts the thread arrives in my mailbox.

 original-message-finally-arrived.  (but the resposes are not groupd as thread)
 response-1
 response-2
 response-3
 response-4

Follow-ups to the original message 
that arrive in my mail box AFTER the original message
arrived IS shown as proper descendents in the thread hierarcy.

 original-message-finally-arrived
  |
  +- response-5   (this arrived AFTER the original message.)
 response1
 response2
 response3
 response4

Response-1 to 4 are not shown as the descendents of the original
message.

I checked that all the responses 
have proper Reference header line
that points back to the original message, which arrived
after responses 1-4 above, and before resonse 5.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Expected Results:  
After all the messages arrive, I would like to see the
following thread hierarchy where
the responses to the original message are displayed
properly as descendents of the original message.

 original-message-finally-arrives
 +- response1
 +- response2
 +- response3
 +- response4
 +- response5.




If automatic re-threading is impossible or too
cumbersome, maybe we may want to
have "re-thread" menu or something so that
this situation, where messages in a 
thread arrive in time-warped manner
 can be taken care of in a batch mode.

Comment 1

[Gervase Markham [:gerv]]

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/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.