stlpaul | # 41 | 2013-06-12, 00:35 | Report

Same also started happening to me today...

Might it be useful if someone whose gmail is still working properly can produce the same kind of log, so we can compare a "good" session to a "bad" session?

xvan | # 42 | 2013-06-12, 00:51 | Report

Does deleting that particular mail recover the session?
I have that bug, but don't know which mail triggered it.

Ilmanowar | # 43 | 2013-06-12, 01:16 | Report

It is a gmail only problem.
It seems that gmail introduced an automatic folder division for messages.
This system similarly to the spam filter gives a label organization to mails.
This new feature is being introduced to all accounts and it makes non-standard the IMAP transactions.
Even the service is disable (default) can't be removed.
I contacted days ago google, to confirm my supposion: any reply yet.
I think that we need ask a solution to gmail. Modest works properly.
In the other hand it is possible to make modest compatible with the buggy gmail protocol.

Copernicus | # 44 | 2013-06-12, 01:18 | Report

Doesn't seem to. I deleted the mail, then deleted and recreated the Gmail account, but still having problems -- the inbox doesn't even appear now.

It looks like whatever bug this is, it well and truly messes up Modest.

Copernicus | # 45 | 2013-06-12, 01:24 | Report

I can't agree. If there were truly a serious Gmail issue, millions of people across the globe would be up in arms immediately. It would probably be headline news!

My Thunderbird client is having no problem with Gmail, even when reading the e-mail that triggered the issue in my Modest client. Moreover, my other Modest client, in which I haven't yet downloaded the message of interest, is having no problem using Gmail today.

Honestly, something in this particular message is causing Modest to go ga-ga...

EmmaGx | # 46 | 2013-06-12, 02:08 | Report

Just adding a Me too!

Can't read anything that's come in since 5.30pm BST 11 the June ...

... old messages (even ones I've not read before) open just fine ... it's just new messages sent after that time that are causing the problem ... seems like gmail have definitely changed something!

Hoping someone can find a solution! x

Estel | # 47 | 2013-06-12, 03:23 | Report

It's possible, that gmail changed something to non-standard, yet, supported by most mainstream mail clients. So called "corporate spoiling" of standards, i.e. enforcing adapting to your shitte, just because you're popular. I'm not sure if it's the case here, but it is very suspicious, that problems started to appear in sync with google adding a new "feature" (no matter if you want it or not).

OTOH, it is possible, that modest "gmail" automatic configuration was already "spoiled" by bending to some non-standards things, that were changed, lately. In this case, not only setting gmail to work via pop3 (we already confirmed it's working), but also *manually* (avoiding automatic setup for gmail!) adding imap account for gmail, typing ports by the hand etc, should help. I haven't tried it yet, it's just a theory.

BTW, I got hit by that bug, too. Strangely, in my case, it happened with old mail that was already opened in the past - one with attachement. Other old mails, without attachements, are working fine (for nowj.

It would reinforce point about fault geing on gmail's side, due to some changes they introduce. (or, modest *was* bugged after all, but gmail change just triggered that bug). In any case, google sux

/Estel

Copernicus | # 48 | 2013-06-12, 06:13 | Report

I just can't believe it, personally. Sure, things happen that are advantageous to mainstream mail clients from time to time; but, there are just so many non-mainstream mail clients out there (and the mail system is so well entrenched by this point anyway), that a change that has this drastic of an effect on clients would have people at Google's doors with pitchforks in mere moments. (Heck, you can already see the fire in people's eyes just from the folks here using Modest.) Honestly, if Google ever did cause something this significant, they'd be backing it out of their system in mere hours.

I'm fairly certain now that the first message Marmistrz sent me triggered the bug, even though I was able to download and read it. Every message after that one, from him or anyone else, generates the error message.

From the log messages, it appears that Modest has gone wonky about IMAP UID numbers. Essentially, it can still download mail from Gmail (or whoever), but some check at the end determines that the UID was wrong and gives up, even though it is apparent that both Modest and Google agreed on the UID up to that point. This really has to be a bug on Modest's part somewhere...

freemangordon | # 49 | 2013-06-12, 07:06 | Report

I agree with Copernicus that it seems to be a bug in modest

EDIT:

More precisely - not in modest, but in tinymail-camel

xvan | # 50 | 2013-06-12, 07:37 | Report

Just to confirm that its a modest bug, I use offline imap + mutt without any issue.