195645 - When trying to read a forwarded HTML message sometime mozilla enters endless wait

Status: RESOLVED FIXED

(MailNews Core :: Networking: IMAP, defect)

Description

[bicatu]

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

Sometimes I click in a message to read it s content and mozilla keeps reading it
without displaying anything nor finishing the load.

If I press stop and view the source the message is already there.  When this
happens I need to exit all mozilla windows and log in again to check the other
messages.  

The trouble message causes this error everytime I click on it.

So far it seems that it is a problem when someone forwards HTML/Attached email
originally sent by Outlook but I am not sure.

The navigator and other components continue to work with no problems.

I found this with either windows/linux builds and cyrus/wu IMAP servers.

Reproducible: Always

Steps to Reproduce:
1. log in
2. click on the message
3. hang



Expected Results:  
show the message :)

Comment 1

[Michael Nacey]

I have also seen this error on both Mozilla 1.5 and the Thunderbird 0.4a
(20031110)on both Linux and Windows(XP). This happens to me semi-frequently with
HTML messages (usually with embedded signatures). IMAP server is iMail 8.03. The
apps do not crash, but will never load the message and will lock any other
reading in the same IMAP account. Here is my last log (aborted after a long hang):

0[294310]: 21ed930:mail1.teletracking.com:NA:SetupWithUrl: clearing
IMAP_CONNECTION_IS_OPEN
4060[2620b20]: 21ed930:mail1.teletracking.com:NA:ProcessCurrentURL: entering
4060[2620b20]:
21ed930:mail1.teletracking.com:NA:ProcessCurrentURL:imap://[e-mail]:143/select%3E/INBOX:
 = currentUrl
4060[2620b20]: 21ed930:mail1.teletracking.com:NA:CreateNewLineFromSocket: * OK
IMAP4 Server (IMail 8.03)

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:SendData: 1 capability

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:CreateNewLineFromSocket: *
CAPABILITY IMAP4 IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN AUTH=LOGIN

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:CreateNewLineFromSocket: 1 OK
CAPABILITY completed

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:SendData: 2 authenticate CRAM-MD5

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:CreateNewLineFromSocket: +
PDMzNi4tNzk5MTU2NDY4QE1BSUwxPg==

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:SendData:
bW5hY2V5IDgzYTI3MjAwOGUyOTM1MGQ5ZDQxNzZlZjllNWJlMTA5

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:CreateNewLineFromSocket: 2 NO
AUTHENTICATE Unsupported authentication mechanism, credentials rejected

4060[2620b20]: 21ed930:mail1.teletracking.com:NA:SendData: Logging suppressed
for this command (it probably contained authentication information)
4060[2620b20]: 21ed930:mail1.teletracking.com:NA:CreateNewLineFromSocket: 3 OK
LOGIN completed

4060[2620b20]: 21ed930:mail1.teletracking.com:A:SendData: 4 lsub "" "*"

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Pam

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Tri-L

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Saved

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Orders

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Templates

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Drafts

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Sent

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Unmarked) "/" INBOX

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Trash

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" spam

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Citrix

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LSUB
(\Marked) "/" Build

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: 4 OK
LSUB completed

4060[2620b20]: 21ed930:mail1.teletracking.com:A:SendData: 5 list "" "INBOX"

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LIST
(\Unmarked) "/" INBOX

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * LIST
(\Unmarked) "/" INBOX

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: 5 OK
LIST completed

4060[2620b20]: 21ed930:mail1.teletracking.com:A:SendData: 6 select "INBOX"

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * FLAGS
(\Answered \Flagged \Deleted \Seen \Draft)

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * 16 EXISTS

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * 0 RECENT

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * OK
[UNSEEN 16] 1 Messages unseen

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: * OK
[UIDVALIDITY 1068142371] UIDs valid

4060[2620b20]: 21ed930:mail1.teletracking.com:A:CreateNewLineFromSocket: 6 OK
[READ-WRITE] SELECT completed

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:SendData: 7 UID fetch 1:*
(FLAGS)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
1 FETCH (FLAGS (\SEEN) UID 367460703)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
2 FETCH (FLAGS (\ANSWERED \SEEN) UID 368142518)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
3 FETCH (FLAGS (\SEEN) UID 368142537)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
4 FETCH (FLAGS (\ANSWERED \SEEN) UID 368142543)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
5 FETCH (FLAGS (\SEEN) UID 368142642)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
6 FETCH (FLAGS (\SEEN) UID 368142657)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
7 FETCH (FLAGS (\ANSWERED \SEEN) UID 368142688)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
8 FETCH (FLAGS (\SEEN) UID 368142695)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
9 FETCH (FLAGS (\SEEN) UID 368142759)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
10 FETCH (FLAGS (\ANSWERED \DELETED \SEEN) UID 368142768)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
11 FETCH (FLAGS (\DELETED \SEEN) UID 368142771)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
12 FETCH (FLAGS (\DELETED \SEEN) UID 368142781)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
13 FETCH (FLAGS (\ANSWERED \SEEN) UID 368142782)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
14 FETCH (FLAGS (\DELETED \SEEN) UID 368142783)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
15 FETCH (FLAGS (\DELETED \SEEN) UID 368142787)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
16 FETCH (FLAGS () UID 368142788)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: 7
OK UID Completed

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:ProcessCurrentURL: entering
4060[2620b20]:
21ed930:mail1.teletracking.com:S-INBOX:ProcessCurrentURL:imap://[e-mail]:143/fetch%3EUID%3E/INBOX%3E368142759:
 = currentUrl
4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:SendData: 8 UID fetch
368142759 (BODYSTRUCTURE)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: *
9 FETCH (BODYSTRUCTURE (("text" "html" ("charset" "us-ascii") NIL NIL "7bit"
6844 155 NIL NIL NIL)("image" "jpeg" ("name" "C:\\TeleLogoSignature.jpg")
"<[e-mail]>" NIL "base64" 29092 NIL
("inline" ("filename" "C:\\TeleLogoSignature.jpg")) NIL) "related" ("boundary"
"------------000003050400010407040109") NIL NIL) UID 368142759)

4060[2620b20]: 21ed930:mail1.teletracking.com:S-INBOX:CreateNewLineFromSocket: 8
OK UID Completed

0[294310]: 21ed930:mail1.teletracking.com:S-INBOX:TellThreadToDie: close socket
connection
0[294310]: 21ed930:mail1.teletracking.com:S-INBOX:TellThreadToDie: close socket
connection

Comment 2

[David :Bienvenu]

the server is dropping the connection when we fetch the body structure. But we
shouldn't lock out operations on that folder after that. Would it be possible to
get access to a test account on that server? And for the test account to have a
message that causes the problem?

Comment 3

[David :Bienvenu]

Actually, I've got iMail 8.01 - if you could send me a message that causes the
problem, I could try it on my server...though there's no guarantee that it would
cause the problem on my server.

Comment 4

[Michael Nacey]

I actually stopped it after it had hung for a few minutes (so the Close Socket
events are my doing). Interestingly enough, when I turn off the message pane and
go to forward the message, it shows the body of the message just fine in the
forwarded message. Perhaps it is an issue with the message pane?. I will try to
forward it to you without changing the headers directly from the iMail server so
don't be alarmed if you get a strange message.

Also, this particular message was not sent by Outlook, but by Thunderbird.

Comment 5

[David :Bienvenu]

well, the second close socket is probably yours, but I'm not sure about the
first one. After we fetch body structure, we'll fetch the message immediately,
and I don't see that in the log. Perhaps we have some problem parsing the body
structure response, but we usually put an entry in the log when the parser gets
an error...

Comment 6

[Michael Nacey]

Verfied that this still happens in both Mozilla 1.6b and Thunderbird 0.4

Comment 7

[David :Bienvenu]

thanks to Michael, I have a test account with this message in it, and I see the
behaviour he describes. It's either a problem with the server response to the
body structure request, or a problem with our parsing of the body structure, in
particular, with one of the quoted strings. Hmm, maybe it's our handling of '\'
characters in quoted strings...

Comment 8

[David :Bienvenu]

Attachment: proposed fix

we need to account for the escape chars cut when calculating the next starting
pos. This fixes this bug for me, and probably a lot of dups.

Comment 9

[(not reading, please use [e-mail] instead)]

Comment on attachment 137252 [details] [diff] [review]
proposed fix

nice!  r/a=sspitzer

maybe a candidate for 1.4.2?

Comment 10

[David :Bienvenu]

request 1.4.2 permission...I think there are a fair number of dups of this bug.

Comment 11

[David :Bienvenu]

Fix checked in; thx so much for the test account, Michael.

Comment 12

[Michael Nacey]

Glad to help. When can I check it out?

Comment 13

[David :Bienvenu]

tomorrow's 1.6b nightly/daily build will have the fix.  

Comment 14

[Michael Nacey]

Nightly build 2003121209 fixes this for me.

Comment 15

[Mike Cowperthwaite]

*** Bug 218278 has been marked as a duplicate of this bug. ***

Comment 16

[Simon Paquet [:sipaq]]

Comment on attachment 137252 [details] [diff] [review]
proposed fix

I guess David Bienvenu also wanted to ask for approval and not only for
blocking status. This patch has been fixed on the trunk and the 1.6-branch for
over a month, so it should be pretty safe to put it into 1.4.2

Comment 17

[bicatu]

I was wondering if this is solved in the latest thunderbird builds ?

Comment 18

[David :Bienvenu]

if the thunderbird build is from after 12/11/03, it will have this fix.

Comment 19

[Mike Kaply [:mkaply]]

Comment on attachment 137252 [details] [diff] [review]
proposed fix

please get this in fast and put the keyword fixed1.4.2 when it is in