got to say that its funny to see the osso mail app pull of something that modest just cant seem to get right.

i dont know why, but modest seems to have it in for one of my pop account.

it downloads full mails when told to only get headers.

mails i know i have read becomes unread the next time i open modest.

and thanks to that insistance of getting whole mails i have to manually clear the inbox.

but i guess imap (specifically gmail imap) have priority as it seems thats what most of the community uses...

YOU WILL BE ASSIMILATED TO GOOGLE. RESISTANCE IS FUTILE.

i STILL get a ssl cert. error when using gmail imap.

new modest update is available. Seems good so far...

Tried the last version and still getting internal error message on quering for new mail.

If anyone else is getting this please vote for
https://bugs.maemo.org/show_bug.cgi?id=2968

Must admit I'm getting a little bit nervous. Diablo is coming and it seems I'll end up with an email-client which only works till a new mail arrives.
I know, I know...it's beta and the developers are working on it as we speak ...but still...it's annoying

please can someone confirm, if there is a problem with imap-folder naming.
If I move mails to folders which includes characters like "." or "-" it's more likely that modest will crash with "internal error".

Since the release of W20 I have seen just a couple of Internal Error messages. Much better than the usual daily crashes.

With W22, no errors so far.

i upgraded to W22....still got the ssl cert error for gmail imap. i uninstalled modest and all libraries,wiped all traces from my system and reinstalled... and still get it. how are people getting gmail imap to work?

I too get the cert error, but I'm not sure that it's Modest's fault (completely). I also have Claws mail installed, and recalled having to do something with the cert when I first setup there, so I went to claws and looked at the saved certificate. Claws reports the same error with the gmail's cert, bad signature, but in Claws you can accept and save the certificate regardless. I haven't had the time to check it out on my PC to see if it reports the same, or if this is limited to the IT's.

W22 and still the status update doesn't seem to work correctly.

I marked an email in Inbox as "unread" (in Gmail, only configured account in modest).
Reloaded the Inbox in modest and it showed up Unread.
Read the mail thru Modest, it correctly marks it read (in modest), but not in Gmail (as expected).
Then I changed folder, but it still show Unread in the web version.
Changed back to Inbox in modest, and it still showed unread.
Even after a "reload" (even if this took quite a while to finish).

Trying to quit modest and see if it gets updated.
Yes, this time it did.

Moreover I think I found another bug I will post in bugzilla.
When I marked the mail unread thru the Gmail web interface, and hit "reload" in modest, it correctly marked the folder Inbox in bold with 1 new mail to read.
But the mail itself was still marked as read.
Thus I had the Inbox folder showing there was 1 mail to read, but no mail was actually marked as unread.
Only changing folder in modest and switching back to Inbox showed up the mail correctly marked 'unread'.

Moreover, sometimes, the Reload button takes way too much time to actually finish the process...

Uhm, I have marked another mail as unread (now I have 2 unread mails), the reload takes over a minute to finish its task, but it still shows 1 unread mail.

I am running it from Terminal (modest showui), but no error is written on console.