392520 - messages labeled and unlabeled before 2.0 are now displayed like tagged but aren't actually tagged

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Jason Brodsky]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: 2.0.0.6 (20070728)

Previous to upgrading to 2.0, I regularly used labels.

Today, when I upgraded, some messages are
a) colored according to tag
b) sorted with tagged messages
c) tag name appears in the tag column
but:
1) although I had once labeled these messages, I had since unlabeled them.  They were not labeled at the time of upgrade
2) pressing 0 or selecting remove tag will not cause these messages to appear untagged
3) the message header does not display a "tags:" entry (like other tagged messages do).
4) If the message appears to be tagged Important, and I press 1 or select Tag->Important, the word important appears twice in the tag column.


Messages that were labeled when I upgraded are now tagged correctly.  Messages that I tag now appear to behaving fine.

Reproducible: Sometimes

Steps to Reproduce:
No steps--I didn't do anything, it was like that as soon as I upgraded.  That said, another email account did not show this problem--all emails that appear tagged on this other account are working fine.
Actual Results:  
See "Details"

Expected Results:  
Emails that I labeled a long time ago and then unlabeled should no longer appear any different than other emails.  I should be able to remove this pseudo-tagged status from emails showing it.

Comment 1

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #0)
> 3) the message header does not display a "tags:" entry (like other tagged
> messages do).

See Bug 377986 & Bug 380545. See also Bug 383846 and Bug 392510. 

> 4) If the message appears to be tagged Important, and I press 1 or select
> Tag->Important, the word important appears twice in the tag column.

Similar phenomenon to Bug 380598?
Or problem just after upgrade? (possibly garbage of old label data)

Old label of Important is kept in X-Mozilla-Status(or 2):, and tag of $label1(Important) to  $label5(Later) are created when upgrade in order to convert old label to new tag (see this via "config editor" in Option/Advanced). 
And, because old mails don't have X-Mozilla-Keys: until folder is compacted, new $lablel information is held in .msf only.

(Q1) Is dup'ed Important displayed for the mail even after restart of Thunderbird?
(Q2) (After restart) What X-Mozilla-Keys: header will be generated for the mail with dup'ed tags when "Compact Folder" is executed?
(To force execution of compact, move a mail to other folder and move back again.)

Comment 2

[Jason Brodsky]

Answers:

(Q1)  Yes, the message still displays "Important Important" in the tags column.

(Q2)I'm not sure how to find what you're talking about.  Can you give more precise instructions?  I'll do my best.

Comment 3

[WADA:World Anti-bad-Duping Agency]

1. Terminate Thunderbird
2. Keep back up of ".msf" file for mail folder contains mail of dup'ed Important
   (When Inbox folder, file named "Inbox.msf", not "Inbox")
3. Restart Thunderbird
4. Click mail folder(open) which have the mail of dump'ed Important
5. Move a mail from the mail folder to other mail folder, then move back
6. "Compact Folder"
7. Click other mail folder, and click the mail folder (to avoid unwanted bugs)
8. View the mail of dup'ed Important label
9. View/Message Source (Ctrl+U)
What is written in X-Mozilla-Keys: header?

Comment 4

[Jason Brodsky]

I cannot find an X-Mozilla-Keys header while viewing the source of any of my messages, including ones whose tags appear to be working fine, on either of my accounts.  I should mention that both accounts are IMAP.

Comment 5

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #4)
> I should mention that both accounts are IMAP.

Oh, IMAP case...
When IMAP, phenomenon depends on whether your IMAP server supports keyword(flag which is not predefined by RFC 3501) or not. http://www.faqs.org/rfcs/rfc3501.html
Get IMAP protocol log first, please.
  http://kb.mozillazine.org/Session_logging_for_mail/news
  http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
  http://www.mozilla.org/projects/netlib/http/http-debugging.html
"SET NSPR_LOG_MODULES=imap:5" is sufficient for initial analysis.
Attach log file to this bug(text/plain if size is accepted. never paste.)

(0) Keep back up of ".msf" file for later problem analysis.
(1) Start Tb with NSPR logging enabled.
(2) Copy the mail to a local mail folder.
(3) Terminate TB
(4) Restart Tb(no need of NSPR logging)
(5) View the mail in local mail folder
(6) View/Messsage Source
    (If no X-Account-Keys: is generated at this step, move a mail)
    (then move back, and do compact folder, please)

Comment 6

[Jason Brodsky]

I'll be away on vacation 'till the end of the month.  I'll do this procedure once I'm back.

Comment 7

[Magnus Melin [:mkmelin]]

Bug 392371 might be related.

Comment 8

[[:Aureliano Buendía]]

Jason any reply to comment #5?

Comment 9

[Joshua Cranmer [:jcranmer]]

RESO INCO due to lack of response to last question. If you feel this change was in error, please respond to this bug with your reasons why.