Open
Bug 671472
Opened 13 years ago
Updated 4 years ago
Message threading does not correlate message replies
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: commander4bugs, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:5.0) Gecko/20110706 Firefox/5.0 SeaMonkey/2.2
Build ID: 20110706120824
Steps to reproduce:
Received an email (IMAP account) in the Inbox, then replied to this email.
The mail was configured to save the reply in the same folder as the original
(Inbox), which happened correctly. The Inbox folder was set to sort
the messages by the arrival time and the message thread.
Here is the header for the original message:
Received: from exch-mbx-111.vmware.com ([10.128.152.211]) by
wdc-ht01.vmware.com ([10.128.152.106]) with mapi; Wed, 13 Jul 2011 17:57:03
-0700
From: Deepak Bobbarjung <CENSORED>
To: Aleksey Pershin <CENSORED>
Date: Wed, 13 Jul 2011 17:57:01 -0700
Subject: regarding purify installation
Thread-Topic: regarding purify installation
Thread-Index: AcxBwPECUnKzc3wERsGZfWlYmSJrZw==
Message-ID:
<87A97D95084A5240AC69A0EE6FDF775103007084F6@exch-mbx-111.vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-MS-Exchange-Organization-AuthSource: wdc-ht01.vmware.com
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_87A97D95084A5240AC69A0EE6FDF775103007084F6exchmbx111vmw_"
MIME-Version: 1.0
Here is the header from the reply message (composed by me):
From: Aleksey Pershin <CENSORED>
To: Deepak Bobbarjung <CENSORED>
Date: Wed, 13 Jul 2011 19:17:12 -0700
Subject: Re: regarding purify installation
Thread-Topic: regarding purify installation
Message-ID: <4E1E51A8.7010501@vmware.com>
References:
<87A97D95084A5240AC69A0EE6FDF775103007084F6@exch-mbx-111.vmware.com>
In-Reply-To:
<87A97D95084A5240AC69A0EE6FDF775103007084F6@exch-mbx-111.vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110706 Firefox/5.0
SeaMonkey/2.2
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
As far as I can tell, the reply contains the same subject (except for Re:)
and the "References" and "In-Reply-To" tags appear to have the correct
IDs matching the "Message-ID" tag of the original message.
Actual results:
The reply message was saved in the Inbox but was not shown as a "child"
message in the tree of messages for the original message. The reply was
simply shown as a new "root" message unrelated to the original.
Expected results:
The reply should be shown as a "child" of the message it was replied to.
Adding a screenshot. The red bar shows the wrong way
to display the reply. The green bar shows the right way
to display the reply.
Comment 2•13 years ago
|
||
wsmwk says this might be a duplicate and that I should cc: :aurelia
Comment 3•13 years ago
|
||
I am seeing the same thing in TB5 but with replies to threads from other people, not my own replies saved to my Inbox.
-- Jeff
This is still reproducible with SeaMonkey 2.3.
Here is another example of a pair of related messages that were not matched.
Original message
----------------------------------------------------------------------
Received: from exch-mbx-111.vmware.com ([10.113.190.111]) by
pa-excaht03.vmware.com ([10.113.81.154]) with mapi; Wed, 17 Aug 2011 21:26:50
-0700
From: Suresh Ravoor <CENSORED>
To: Aleksey Pershin <CENSORED>
CC: Ilya Languev <CENSORED>
Date: Wed, 17 Aug 2011 21:26:49 -0700
Subject: memory leak issue ...
Thread-Topic: memory leak issue ...
Thread-Index: AcxdXwwV9fn/s3QCRceOWaMAa7VdVA==
Message-ID:
<2E9DFD00E8458D43A9457BABE98F2FC9021BC959CF@exch-mbx-111.vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 04
X-MS-Exchange-Organization-AuthSource: pa-excaht03.vmware.com
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_2E9DFD00E8458D43A9457BABE98F2FC9021BC959CFexchmbx111vmw_"
MIME-Version: 1.0
Reply
----------------------------------------------------------------------
From: Aleksey Pershin <CENSORED>
To: Suresh Ravoor <CENSORED>
CC: Ilya Languev <CENSORED>
Date: Thu, 18 Aug 2011 15:30:40 -0700
Subject: Re: memory leak issue ...
Thread-Topic: memory leak issue ...
Message-ID: <4E4D9290.4060009@vmware.com>
References:
<2E9DFD00E8458D43A9457BABE98F2FC9021BC959CF@exch-mbx-111.vmware.com>
In-Reply-To:
<2E9DFD00E8458D43A9457BABE98F2FC9021BC959CF@exch-mbx-111.vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110813 Firefox/6.0
SeaMonkey/2.3
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Comment 5•13 years ago
|
||
The latest Earlybird 8.0a builds fix the problem I was having.
Comment 6•13 years ago
|
||
Thunderbird 8.0a corresponds to SeaMonkey 2.5a.
Commander can you try 2.5a?
<http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/>
(In reply to Philip Chee from comment #6)
> Thunderbird 8.0a corresponds to SeaMonkey 2.5a.
> Commander can you try 2.5a?
> <http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-
> central-trunk/>
I have tried the latest trunk build of SeaMonkey 2.5a (version 8.0.0.4245,
buildID 20110816003027. The issue is still reproducible.
Here is what I did:
1. Backed up my SeaMonkey 2.3 profile
2. Renamed my SeaMonkey 2.3 installation directory
3. Extracted the nightly build into a clean directory with the same name
as SeaMonkey 2.3 used to be
4. Started SeaMonkey and went to the mail
5. Everything opened fine.
6. When I was still using 2.3, I had several problematic messages
in my inbox. They were grouped like this (in 2.3):
* Original message
* My reply
** Somebody else's reply to the original message
** Somebody else's reply to my reply to the original message
Notice that the replies were grouped together but separately from
the original message.
7. The above 4 messages were grouped the same way (replies together but
separate from the original) in SeaMonkey 2.5a
8. While still using SeaMonkey 2.5a replied to the original message
(but addressed the reply only to me to avoid confusing others).
9. The new reply was saved in Inbox but grouped with other replies,
NOT the original message.
10. My reply came back to me from the email server (remember, my reply
was addressed only to me) and was also grouped with other replies,
NOT the original message.
(In reply to Commander from comment #7)
> 9. The new reply was saved in Inbox but grouped with other replies,
> NOT the original message.
>
> 10. My reply came back to me from the email server (remember, my reply
> was addressed only to me) and was also grouped with other replies,
> NOT the original message.
Forgot to mention, just to make the experiment clean, I deleted ALL
the replies (leaving only the original message) and then repeated steps
9 and 10. The result was the same: the replies were grouped together
but separate from the original message.
BTW, I am not sure if this matters or not, 2.5a started displaying
tiny blue arrows on the message icon. I assume this is to indicate
messages I replied to. When I opened my inbox in 2.5a, the original
message was correctly shown with this blue arrow, even though the replies
were not grouped with it (as described in comment #7). I suspect
that these things are independent of each other.
Comment 9•4 years ago
|
||
NOT (no longer?) reproducible with installation of unofficial (by wg9s) De SeaMonkey 2.53.4beta 1 pre Mozilla/5.0 (NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Build 20200604210008 (Default Classic Theme, newly created User Profile) on German WIN7 64bit and a single test mail I tried.
I am not sure, was the problem a general one or related to particular mails?
You need to log in
before you can comment on or make changes to this bug.
Description
•