Closed
Bug 363666
Opened 18 years ago
Closed 18 years ago
No messages show up in IMAP folder listings due to QUOTAROOT parsing problem
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: chris, Assigned: mscott)
References
Details
(Keywords: fixed1.8.1.2, regression)
Attachments
(2 files)
20.57 KB,
text/plain
|
Details | |
1.16 KB,
patch
|
Bienvenu
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418.9 (KHTML, like Gecko) Safari/419.3 Build Identifier: 2.0b1 Downloaded 2.0 beta 1. Ran it with same profile from 1.5.08. When it logs into my main IMAP account, after it reads the folder, All the messages in the list for that folder disappear - I am left with an empty folder. If I switch back to 1.5.0.8, everything works fine and all the messages show up. This happens for all folders. For folders other than the in box, I can actually see it opening the folder and displaying the initial list of messages, and then all the messages just disappearing - poof. Reproducible: Always
Reporter | ||
Updated•18 years ago
|
Version: unspecified → 2.0
Comment 1•18 years ago
|
||
View > Messages is set to all?
Reporter | ||
Comment 2•18 years ago
|
||
Yes, it is set to all by default. I have tried changing to other things, and then back to all but it does not fix the problem. I also tried deleting my entire contents folder of IMAP folder listing cache files (the folder in my profile folder called ImapMail), and that did not help either.
Reporter | ||
Comment 3•18 years ago
|
||
I just downloaded 2.0b2 and I am having the same problem. I went through the formal process (option-double-click start) of creating a new profile and added 1 IMAP account. logged in, and see an empty inbox which I know has 40+ messages in it. If i log in with 1.5.x, I see everything fine. The cursos seems to stick at the BW watch in thunderbird, although I can do things no problem. Error messages from the error console: Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIIOService2.manageOfflineStatus]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///Users/chris/Desktop/Thunderbird.app/Contents/MacOS/components/offlineStartup.js :: anonymous :: line 95" data: no] Source File: file:///Users/chris/Desktop/Thunderbird.app/Contents/MacOS/components/offlineStartup.js Line: 95 Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgAccountManager.defaultAccount]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/msgMail3PaneWindow.js :: MigrateJunkMailSettings :: line 1748" data: no] I am running against a Merak Icewarp IMAP server.
Comment 4•18 years ago
|
||
I think those js errors are unrelated. Are you sure the messages are downloaded? What you saw "initially" wasn't cache of the messages you already downloaded? An imap protocol log may be helpful <http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap>
Reporter | ||
Comment 5•18 years ago
|
||
imap protocol log noticed this error: 37691392[5e03fb0]: 22fec00:mail.grope.com:S-INBOX:SendData: 11 getquotaroot "INBOX" 37691392[5e03fb0]: ReadNextLine [stream=5e04698 nb=67 needmore=0] 37691392[5e03fb0]: 22fec00:mail.grope.com:S-INBOX:CreateNewLineFromSocket: * QUOTAROOT C:\Program Files\Merak\mail\grope.com\chris\inbox\ "" 37691392[5e03fb0]: 22fec00:mail.grope.com:S-INBOX:PARSER:Internal Syntax Error: %s:: no atom characters found 37691392[5e03fb0]: 22fec00:mail.grope.com:S-INBOX:PARSER:Internal Syntax Error on line: %s: * QUOTAROOT C:\Program Files\Merak\mail\grope.com\chris\inbox\ "" 37691392[5e03fb0]: 22fec00:mail.grope.com:S-INBOX:SendData: 12 UID fetch 1:* (FLAGS)
Reporter | ||
Comment 6•18 years ago
|
||
The previous error with the QUOTAROOT response is causing TBird to logout before the server sends back the message listing: 37691392[5e03fb0]: 22fec00:mail.grope.com:NA:SendData: 13 logout dunno if the response is valid or not. Will have to look it up.
Comment 7•18 years ago
|
||
Did this work with 1.5.0.8? We might have tightened up the parsing of the quota response in 2.0
Reporter | ||
Comment 8•18 years ago
|
||
Yes, no problems pre-2.0. * QUOTAROOT C:\Program Files\Merak\mail\grope.com\chris\inbox\ "" Seems like this is valid response to a getquotaroot request per RFC2087 (I'm way sketchy on BNF form though).
Comment 9•18 years ago
|
||
looks to me like this code has gone back and forth and back and forth: https://bugzilla.mozilla.org/show_bug.cgi?id=274546 and this checkin http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=nsImapServerResponseParser.cpp&branch=&root=/cvsroot&subdir=mozilla/mailnews/imap/src&command=DIFF_FRAMESET&rev1=1.136&rev2=1.137 I need to look at the rfc - it looks to me like we're just eating all the tokens...
Comment 10•18 years ago
|
||
cc'ing our parser expert - on the 2.0 branch, we're still doing what I did in https://bugzilla.mozilla.org/show_bug.cgi?id=274546 - I don't think we can skip to crlf like we are doing on the trunk, because of bug 274546
Comment 11•18 years ago
|
||
or does perhaps skip to crlf do the right thing with string literals now?
Comment 12•18 years ago
|
||
David, as you have found out in Comment 9, http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=nsImapServerResponseParser.cpp&branch=&root=/cvsroot&subdir=mozilla/mailnews/imap/src&command=DIFF_FRAMESET&rev1=1.136&rev2=1.137 the old code for QUOTAROOT has sneaked back in... The blame is on me: in Bug 327754 I first submitted a reasonable patch (id=212417) and then somehow fell back to the old version (id=212418). Anyway, |skip_to_CRLF()| does not do the right thing there---so Bug 274546 appears again. I extracted the part of the "good" patch (id=212417) and have attached it (but have not tested it again).
Updated•18 years ago
|
Attachment #252997 -
Flags: review?(bienvenu)
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Mac OS X → All
Hardware: Macintosh → All
Summary: No messages show up in IMAP folder listings → No messages show up in IMAP folder listings due to QUOTAROOT parsing problem
Comment 13•18 years ago
|
||
Comment on attachment 252997 [details] [diff] [review] Properly skip QUOTAROOT response ah, thx so much! That looks like the right thing to do. I'll try it out today.
Attachment #252997 -
Flags: review?(bienvenu) → review+
Comment 14•18 years ago
|
||
I've landed this on the trunk and branch, to get feedback as quickly as we can. It worked with the four imap servers I have access to, that support quota ...Chris, can you try out a nightly 2.0 build - the fix will be in tomorrow's build.
Reporter | ||
Comment 15•18 years ago
|
||
version 2 beta 2 (20070128) from nightly/latest-mozilla1.8/ - still having the same problem. Same error messages in the imap protocol log. I built a trunk version last night and had the same problem, and verified it had the patch in it. I'm now wondering if the parser is having trouble with the windows path? The backslashes are not atoms and are confusing it - (they should be escaped/double-backslashes)? Could be that this is pushing bug 322863 & patch beyond it's limits? http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=nsIMAPGenericParser.cpp&branch=&root=/cvsroot&subdir=mozilla/mailnews/imap/src&command=DIFF_FRAMESET&rev1=1.50&rev2=1.51
Comment 16•18 years ago
|
||
right, the \ need to be escaped: atom ::= 1*ATOM_CHAR ATOM_CHAR ::= <any CHAR except atom_specials> atom_specials ::= "(" / ")" / "{" / SPACE / CTL / list_wildcards / quoted_specials quoted_specials ::= <"> / "\"
Resolution: FIXED → INVALID
Comment 17•18 years ago
|
||
any chance of contacting the Merak Icewarp IMAP server folks? I think they're returning invalid protocol...
Reporter | ||
Comment 18•18 years ago
|
||
I've contacted them. They're pretty responsive...
Reporter | ||
Comment 19•18 years ago
|
||
It's a problem in the 8.5.x versions of their server, which we are running. They've apparently fixed it in the latest 8.9.x versions. So I guess this would be their problem. Unfortunately we now have to either shell out for the upgrade or ... :-(
You need to log in
before you can comment on or make changes to this bug.
Description
•