Thread: [solved] Problems with Modest and Gmail
View Single Post
Copernicus's Avatar
Copernicus is offline Copernicus
2013-06-11 , 18:15
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#36
Aha!!! I've just received a message from Marmistrz that exhibits the problem in my copy of Modest. I'm personally betting that the problem lies in the truly enormous ID string being used for the message:

Message-ID: <CANaCrST0DBGwq7i5iP--aek15eqrRpY-YQ8a0eawo2XVBTzdwA@mail.gmail.com>

I think there's something like 66 characters all told in that ID, if I counted right.

EDIT: Drat, I've got another message with the same size ID, and that one has no problems, so it can't be the raw size. That one doesn't have any dashes in the ID, though... I'll check the rest of the header for anything suspicious.

EDIT 2: I've just noticed that a message from maemo.org earlier this morning also triggers the error. Checking the log, I just see a message like Marmistrz had on the first page of this thread...

EDIT 3: From the log, I'm getting the following sequence:

Code:
sending : C00000 CAPABILITY
received: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH AUTH=XOAUTH2
received: C00000 OK Thats all she wrote! m8if529565ibg.26
sending : C00001 LOGIN xxx xxx
received: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH
received: C00001 OK jpietrzak8@gmail.com John Pietrzak authenticated (Success)
sending : C00002 CAPABILITY
received: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH
received: C00002 OK Success
sending : C00003 ENABLE CONDSTORE
received: * ENABLED CONDSTORE
received: C00003 OK Success
sending : C00004 NAMESPACE
received: * NAMESPACE (("" "/")) NIL NIL
received: C00004 OK Success
sending : C00005 SELECT INBOX (CONDSTORE)
received: * FLAGS (\Answered \Flagged \Draft \Deleted \Seen Junk NonJunk $Forwarded $MDNSent)
received: * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen Junk NonJunk $Forwarded $MDNSent \*)] Flags permitted.
received: * OK [UIDVALIDITY 3] UIDs valid.
received: * 287 EXISTS
received: * 0 RECENT
received: * OK [UIDNEXT 353] Predicted next UID.
received: * OK [HIGHESTMODSEQ 277626]
received: C00005 OK [READ-WRITE] INBOX selected. (Success)
sending : C00006 NOOP
received: C00006 OK Success
sending : C00007 UID FETCH 352 BODY.PEEK[]
After which the full body of message 352 comes down. But, after that, comes this log item:

Code:
received: C00007 OK Success
CamelException.setv(0x43f9ad48, 109, 'Message with UID 352 does not exists')
So, not sure what is going on here...

EDIT 4: Ok, here we go. As of about noon today, my copy of Modest on my main N900 began exhibiting the bad behavior after receiving a particular message from Marmistrz. Since then, every message that had not been previously stored on my N900 comes up with the error message "does not exists". In short, my Gmail connection in Modest has been hosed.

However, if I use Modest on my second N900 (and carefully avoid loading any of Marmistrz' messages), everything works fine; I can download new messages off of Gmail with no problem.

Thus, I'd have to say that something buggy is going on in Modest itself, something to do with parsing a particular message...
Last edited by Copernicus; 2013-06-11 at 20:11. Reason: Log info
 

The Following 9 Users Say Thank You to Copernicus For This Useful Post: