maemo.org - Talk - [solved] Problems with Modest and Gmail

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - [solved] Problems with Modest and Gmail (https://talk.maemo.org/showthread.php?t=90399)

Re: Problems with Modest and Gmail

I also use gmail, but combined with offlineimap and dovecot, so that both modest and alpine only ever talk to dovecot.

So far I have never noticed any problem such as the one reported here.

Note that the "Message (title) not available on the server" as reported on the first post happens (AFAIK) when you are too quickly notified of a new message (e.g. with Nokia Messaging, which I used for a long time in the past) and *then* Google applies whatever filter it makes it move to another folder. When modest then tries to fetch the message, it's not there anymore.

Re: Problems with Modest and Gmail

no problem here. checked few emails on my gmail account and i haven't faced any problem.

Re: Problems with Modest and Gmail

Quote:

Originally Posted by independent (Post 1351013)

Every single email! It's completely unusable for me.

Can you post your log? You can get it by

Code:

export CAMEL_DEBUG="all"

maemo-summoner /usr/bin/modest -s

We need to find, what's common for all the ppl with the problem.

Any modest devs here? Maybe they'd know anything...

Re: Problems with Modest and Gmail

Quote:

Originally Posted by marmistrz (Post 1351211)

.
.
.
We need to find, what's common for all the ppl with the problem.

Any modest devs here? Maybe they'd know anything...

Once there is any clue what happens, I guess we'll find developers to fix the bug. If it is in modest.

Re: Problems with Modest and Gmail

Quote:

Originally Posted by freemangordon (Post 1351214)

Once there is any clue what happens, I guess we'll find developers to fix the bug. If it is in modest.

But, we know more or less what happens. The message is fetched and right then an error. The problem is: is it gmail's or modest's problem. Anyway, google won't give a damn to fix it for N900, so the maemo devs will have to fix it nevertheless :P

Re: Problems with Modest and Gmail

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...

Re: Problems with Modest and Gmail

Quote:

Originally Posted by marmistrz (Post 1351217)

May I have a message from you too? :)

ivo.g.dimitrov.75 at gmail.com

Re: Problems with Modest and Gmail

@freemangordon.
I've sent you a forward of an email which gives me the message "message 'subject' not available on server. I also sent and email to myself with just the word test in the subject field which did the same thing as have all mails since 8th of June.
Hope you can help.

Re: Problems with Modest and Gmail

Quote:

Originally Posted by king Ralphred (Post 1351247)

Thanks, now the problem is reproducible, I'll look into it when I have some spare time.

Re: Problems with Modest and Gmail

Quote:

Originally Posted by mekenig (Post 1350807)

Thankfully, Nokia Messaging is working fine for me sync'ing with my GMail account so I won't have to ditch my N900 because I can't read incoming gmail.com emails.

Little off-topic, but if gmail would change something, to the point of making standards compliant e-mail client unable to read incoming e-mails, I would ditch gmail in a heartbeat, not my device.

Just like tons of people are doing with shitty google talk, which became uncompatible with other jabber networks.