522935 - "No message found" error message box and random messages disappearing

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking: IMAP, defect)

Description

[JJ]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091016 Lightning/1.0pre Shredder/3.0pre

I have being searching in the Thunderbird bug list and it is possible that the issue I am reporting now is related to other bugs such as:
-	Bug 494669 - Missing messages when moving them to another folder
-	Bug 492412 - Downloaded mail disappears from inbox window arbitrarily and regularly
However, the “No message found” error message box is not reported as well as no mention to the inability to archive certain messages, so I have decided to open a brand new bug.
Description:
It happens when moving messages from one folder to another. If only one message is moved everything seems to be OK. But when another one message is moved the following error message appears: “The current command did not succeed.  The mail server responded:No message found

.”
And immediately, one o more random messages on source folder disappear.
It is particularly annoying if you use, like me, the Thunderbird archiving feature. I use a year-month partition schema and I try to empty my inbox and sent folders by dispatching incoming and outcoming messages to one of the following folders:
-	TO DO
-	TO FOLLOW UP
-	ARCHIVES (YYYY-MM)
In fact lots of errors arise while archiving:
-	“No message found” error message box; every time I type “A” to archive a message (starting from the second hit)
o	Really annoying!!!
-	Random messages disappear from the source folder
o	Really annoying!!!
-	Some messages are actually archived and others don’t. I have not been able to discover a pattern.
o	It is found out after re-index the source folder.
The only way I have found to restore folder actual contents is re-indexing. It is time-consuming and disgusting.

Reproducible: Always

Steps to Reproduce:
1. Type "A" or move a message to another folder manually.
2. Repeat step #1 more than once.
Actual Results:  
-	“No message found” error message box
-	Random messages disappear from the source folder
-	Some messages are actually archived and others don’t

Expected Results:  
Thunderbird has brilliantly solved the archiving need. Using a YEAR-MONTH partition schema is highly effective to me.
Archiving (or generally speaking, moving) a message should produce the expected results: move the selected message or thread to the archive (or generally speaking, the destination folder).

I love how TB's archiving feature. I still use it despite of that annoying bug.
After all, TB is the best email client.

I haven't loose any message, those which disappear come back after re-indexing the folder. However it is a painful situation.

Comment 1

[Ludovic Hirlimann [:Usul]]

Is there anything in Tools -> Error console when you do that ?
You are using imap right ?

Comment 2

[JJ]

Exactly, IMAP.

Following are examples of errors and warnings that arise:

ERRORS
---------------------------------------------------------------------
Error: headerEntry.enclosingRow is undefined
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 753
Error: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]"  nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame :: file:///E:/Program%20Files/Mozilla%20Thunderbird%20Shredder%203.0/components/nsLoginManager.js :: anonymous :: line 328"  data: no]
Source File: file:///E:/Program%20Files/Mozilla%20Thunderbird%20Shredder%203.0/components/nsLoginManager.js
Line: 328
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgMailNewsUrl.mimeHeaders]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://hdrtools/content/hdrtools.js :: anonymous :: line 421"  data: no]

WARNINGS:
---------------------------------------------------------------------
Warning: Unknown property 'mso-style-type'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 63
Warning: Unknown property 'mso-style-type'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 59
Warning: Unknown property 'mso-style-type'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 55
Warning: Unknown property 'mso-style-link'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 51
Warning: Unknown property 'mso-style-priority'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 50
Warning: Unknown property 'mso-style-name'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 49
Warning: Unknown property 'mso-style-name'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 49
Warning: Unknown property 'mso-style-priority'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 41
Warning: Unknown property 'mso-style-priority'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 37
Warning: Unknown property 'mso-style-priority'.  Declaration dropped.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 33
Warning: Unknown descriptor 'panose-1' in @font-face rule.  Skipped to next declaration.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 24
Warning: Unknown descriptor 'panose-1' in @font-face rule.  Skipped to next declaration.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 21
Warning: Unknown descriptor 'panose-1' in @font-face rule.  Skipped to next declaration.
Source File: imap://domain%5Cusername@host:1143/fetch%3EUID%3E/INBOX%3E362959
Line: 18

Comment 3

[Phil Ringnalda (:philor)]

Those warnings are just bad CSS in a message, but the error in chrome://hdrtools/content/hdrtools.js is probably the source of your problems. What happens when you disable whatever Header Tools extension that is?

Comment 4

[JJ]

I turned off the extension (TB Header Tools) and do repeated the test case.
Abnormal and random behavior persisted.

Error console did not show any error message.

My conclusion is that this extension produces those error messages revealed by the Error console but it affects nothing at all the way Thunderbird refreshes a folder after one or more email messages have been moved.

Comment 5

[Ludovic Hirlimann [:Usul]]

Can you generate a imap log, as decribed at https://wiki.mozilla.org/MailNews:Logging when you are reproducing the  issue ?

Comment 6

[JJ]

Of course.

Bellow is an excerpt of this log file. I think it reveals the cause of this issue: TB tries to fetch the email message just after it has been moved.
Log file is more than 10K lines long so I am going to attach it.

----------

2344[17282c0]: 3891c00:localhost:S-Sent:STREAM:CLOSE: Normal Message End Download Stream
2344[17282c0]: ReadNextLine [stream=17416a8 nb=27 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: 17 OK UID FETCH completed

2344[17282c0]: 3891c00:localhost:S-Sent:ProcessCurrentURL: entering
2344[17282c0]: 3891c00:localhost:S-Sent:ProcessCurrentURL:imap://domain%5Cnetusername@localhost:1143/onlinemove%3EUID%3E/Sent%3E112386%3E/Archives/2009:  = currentUrl
2344[17282c0]: 3891c00:localhost:S-Sent:SendData: 19 uid copy 112386 "Archives/2009"

2344[17282c0]: ReadNextLine [stream=17416a8 nb=22 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: 19 OK copy completed

2344[17282c0]: 3891c00:localhost:S-Sent:SendData: 20 uid store 112386 +FLAGS (\Deleted \Seen)

2344[17282c0]: ReadNextLine [stream=17416a8 nb=47 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: * 9 FETCH (UID 112386 FLAGS (\Seen \Deleted))

2344[17282c0]: ReadNextLine [stream=17416a8 nb=23 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: 20 OK STORE completed

0[1727140]: offline imap url succeeded :imap://domain\netusername@localhost:1143/onlinemove>UID>/Sent>112386>/Archives/2009
0[1727140]: queuing url:imap://domain\netusername@localhost:1143/select>/Sent
0[1727140]: considering playing queued url:imap://domain\netusername@localhost:1143/select>/Sent
0[1727140]: creating protocol instance to play queued url:imap://domain\netusername@localhost:1143/select>/Sent
0[1727140]: failed creating protocol instance to play queued url:imap://domain\netusername@localhost:1143/select>/Sent
0[1727140]: considering playing queued url:imap://domain\netusername@localhost:1143/select>/Sent
0[1727140]: creating protocol instance to play queued url:imap://domain\netusername@localhost:1143/select>/Sent
0[1727140]: playing queued url:imap://domain\netusername@localhost:1143/select>/Sent
2344[17282c0]: 3891c00:localhost:S-Sent:ProcessCurrentURL: entering
2344[17282c0]: 3891c00:localhost:S-Sent:ProcessCurrentURL:imap://domain%5Cnetusername@localhost:1143/select%3E/Sent:  = currentUrl
2344[17282c0]: 3891c00:localhost:S-Sent:SendData: 21 noop

2344[17282c0]: ReadNextLine [stream=17416a8 nb=13 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: * 15 EXISTS

2344[17282c0]: ReadNextLine [stream=17416a8 nb=13 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: * 15 RECENT

2344[17282c0]: ReadNextLine [stream=17416a8 nb=22 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: 21 OK noop completed

2344[17282c0]: 3891c00:localhost:S-Sent:SendData: 22 UID fetch 112396:* (FLAGS)

2344[17282c0]: ReadNextLine [stream=17416a8 nb=48 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: * 15 FETCH (UID 112396 FLAGS (\Seen \Deleted))

2344[17282c0]: ReadNextLine [stream=17416a8 nb=27 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: 22 OK UID FETCH completed

2344[17282c0]: 3891c00:localhost:S-Sent:SendData: 23 UID fetch 112386 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Bcc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type x-spam-status x-spam-flag)])

2344[17282c0]: ReadNextLine [stream=17416a8 nb=24 needmore=0]
2344[17282c0]: 3891c00:localhost:S-Sent:CreateNewLineFromSocket: 23 NO No message found

Comment 7

[JJ]

Attachment: Thunderbird IMAP log file

Thunderbird IMAP log file. Log level = 5.

It starts just before beginning test case run.

Comment 8

[JJ]

Hi,

Do you need more info?, maybe an screencast?

Thank you.

Comment 9

[Ludovic Hirlimann [:Usul]]

(In reply to comment #8)
> Hi,
> 
> Do you need more info?, maybe an screencast?

Not for the moment.

Comment 10

[Wayne Mery (:wsmwk)]

JJ 

can you reproduce this on current version ??

Comment 11

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error please respond to this bug with your reasons why.