Closed Bug 133689 Opened 22 years ago Closed 15 years ago

problems loading messages after getting "Internal Syntax Error"

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Assigned: Bienvenu)

Details

Sometimes you get the "Internal Syntax Error" error. Just after this mozilla
refuses to load any messages. You are not provided with any error message,
clicking on the message just doesn't do anything.
This is properly due to the lack of a IMAP connection or something. Not really
sure what's going on just the IMAP parser hits a "Internal Syntax Error".

spin of from bug 126987
forgot to say that the failure to load only seems to affect the same folder as
where you got the "Internal Syntax Error". Loading messages from other folders
works fine. Restartuing mozilla makes it possible to load all messages again.
QA Contact: huang → gchan
I'm getting this with Mozilla 1.5 on Linux, IMAP'd to an MS Exchange 2000
server.  (I had this problem with 1.4.1, too.)

It happens randomly (as far as I can tell), maybe 1 in 20 or 30 messages has the
problem.  Once mozilla fails to read a message, I cannot get it to re-try.  It
leaves the body blank, and doesn't even update the header info when the
problematic message is selected (just leaves whatever was there previously). 
I've attached a bit of the log (the log shows that it got the header of the
message correctly, there was just a problem (no data?) when getting the body.)

Only workaround I know is to restart mozilla (just restarting mailnews is
insufficient).

Here's the server version info:
98311[8a07520]: 86c67d8:pa-exch2.mycompany.com:NA:CreateNewLineFromSocket: * OK
Microsoft Exchange 2000 IMAP4rev1 server version 6.0.6249.0
(pa-exch6.mycompany.com) ready.

Here's the log around one of the problematic messages:
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:ProcessCurrentURL: entering
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:SendData: 7 check
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: * 341 EXISTS
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: * 2 RECENT
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: 7 OK
CHECK completed.
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:SendData: 8 UID
fetch 341:* (FLAGS)
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: * 341
FETCH (FLAGS (\Recent) UID 341)
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: 8 OK
FETCH completed.
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:SendData: 9 UID
fetch 341 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Subject
Date Message-ID Priority X-Priority References Newsgroups In-Reply-To List-Id
X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason
X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason
X-Bugzilla-Reason)])
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: * 341
FETCH (UID 341 RFC822.SIZE 3682 FLAGS (\Recent) BODY[HEADER.FIELDS (From To Cc
Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To
List-Id X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason
X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason X-Bugzilla-Reason
X-Bugzilla-Reason)] {284}
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:STREAM:OPEN Size:
3682: Begin Message Download Stream
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: From:
"Sriram Sankar" <sriram@mycompany.com>
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: To:
"Fun-List" <fun-list@mycompany.com>
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: Subject:
[Fun-list] Learning to use fire extinguishers
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: Date:
Tue, 21 Oct 2003 11:51:12 -0700
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket:
Message-ID: <460A22F8DE34AA49B533BEBF24C66831032D5F@pa-exch6.mycompany.com>
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: List-Id:
<fun-list.mycompany.com>
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: 
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: )
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:STREAM:CLOSE:
Normal Message End Download Stream
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: 9 OK
FETCH completed.
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:ProcessCurrentURL: entering
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:SendData: 10 UID
fetch 341 (UID RFC822.SIZE BODY[])
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: * 341
FETCH (UID 341 RFC822.SIZE 3682 BODY[]  FLAGS (\Seen \Recent))
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:STREAM:OPEN Size:
3682: Begin Message Download Stream
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:CreateNewLineFromSocket: 10 OK
FETCH completed.
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:STREAM:CLOSE:
Normal Message End Download Stream
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:PARSER:Internal
Syntax Error: %s: 10 OK FETCH completed.
196618[8e93230]:
8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:SendData:TellThreadToDie: 11 logout
196618[8e93230]: 8f2d328:pa-exch2.mycompany.com:S-AutoFile/fun:TellThreadToDie:
close socket connection
Product: MailNews → Core
still see this problem?
Assignee: mscott → bienvenu
QA Contact: grylchan → networking.imap
Patrick writes: "I haven't seen this problem, but I stopped using mozilla for email shortly after that."

I can't say whether problem is gone.
I haven't seen that error on any platform.  Looking at the code, my not-very-informed guess would be either that the server (Exchange) passed a response that TB/Mozilla couldn't parse, or it ran out of memory.

If the error *does* happen again, the server log now includes a line indicating where the error happened, which wasn't there in 2003, so that could be more helpful.  See mailnews/imap/src/nsImapServerResponseParser.cpp.
Product: Core → MailNews Core
Let's close this WFM on the strength of comment 5
=> WFM
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.