After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 721915 - New messages are not detected as they arrive on IMAPX account
New messages are not detected as they arrive on IMAPX account
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-01-10 08:41 UTC by Milan Bouchet-Valat
Modified: 2015-03-06 20:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Bouchet-Valat 2014-01-10 08:41:46 UTC
Since I've upgraded to Evo 3.10.3, the mails I receive on one of my IMAPX accounts are no longer detected. I need to switch to another folder, and back to the inbox, for Evo to notice there are new messages. There's the same problem when returning from suspend/offline mode. Even clicking on Send/Receive does not work (or not all the time).

With another IMAPX account I have, everything is working fine.

I think I can provide you with a test account on that IMAP server if you want to debug this.
Comment 1 Matthew Barnes 2014-01-10 13:29:24 UTC
Depends on several factors, like whether your IMAP server supports IDLE and how quickly it times out idle client connections.  Evolution 3.12 will indicate your connection status in the folder tree, so you can more easily see when you lose a socket connection.
Comment 2 Milan Bouchet-Valat 2014-01-10 13:34:45 UTC
Yeah, but it used to work for all releases of Evo over the last 5 years, up to 3.10. Also, I have set "check for new messages every 1 minute", so it should definitely do something (or in the worst case show an error message).
Comment 3 Milan Bouchet-Valat 2014-01-14 09:01:48 UTC
Is there anything I can do to help fixing this (testing...)? Or would you be interested in an account on that server to check by yourself?
Comment 4 Matthew Barnes 2014-01-14 12:53:23 UTC
A test account may be useful, but first run Evolution from a terminal window and check for any warning messages that may give clues.
Comment 5 Milan Bouchet-Valat 2014-01-14 20:37:46 UTC
Not sure. On startup I get this:
(evolution:16919): camel-WARNING **: Unable to load store summary: Expected version (1), got (0)

(evolution:16919): camel-WARNING **: Cannot load summary file: Success

(process:16986): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed


But actually I've discovered that fetching mails can work fine for a few hours, and even across a suspend/resume. The bug only reappeared after the second suspend/resume cycle (affecting both accounts which are mentioned in the log below):
(evolution:17099): camel-WARNING **: network_service_can_reach_cb: Error resolving "imap.sfr.fr" : Temporary name resolving failure [approx translation]

(evolution:17099): camel-WARNING **: network_service_can_reach_cb: Error resolving "imap.sciences-po.fr" : Temporary name resolving failure [approx translation]

(evolution:17099): camel-WARNING **: network_service_can_reach_cb: Error resolving "imap.gmail.com" : Temporary name resolving failure [approx translation]

[repeat many times - these were also printed after the first suspend/resume, when it still worked]

(evolution:17099): camel-WARNING **: network_service_can_reach_cb: Error resolving "smtp.gmail.com" : Temporary name resolving failure [approx translation]
evolution-shell-Message: Connection established.  Going online.

(evolution:17099): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL)

(evolution:17099): evolution-mail-WARNING **: receive_update_got_folderinfo: Cannot connect to "imap.sfr.fr:143": Could not resolve "imap.gmail.com". Check that you have correctly typed the hostname [approx translation]

(evolution:17099): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL)

(evolution:17099): evolution-mail-WARNING **: receive_update_got_folderinfo: Cannot connect to "imap.gmail.com:993": Could not resolve "imap.gmail.com". Check that you have correctly typed the hostname [approx translation]
Comment 6 Milan Bouchet-Valat 2014-01-22 13:30:08 UTC
Are the messages above of any use? Do you need something else?
Comment 7 Matthew Barnes 2014-01-22 14:06:43 UTC
Looks like you're having name resolution problems after resuming.
Comment 8 Milan Bouchet-Valat 2014-01-29 15:44:33 UTC
Yeah, but everything works fine if I restart Evolution. So it looks like the socket gets corrupt or something. Indeed, it seems to happen only when I'm on WiFi, not with the Ethernet connection. So it may be a problem with the driver.

But don't you connect to NetworkManager to be warned when the connection is reinitiated?  Evo does not seem to be able to recover automatically from this everywhere: the automatic mail fetching fails, while other operations still work.
Comment 9 Milan Bouchet-Valat 2014-02-06 18:19:03 UTC
I've also noticed that when this happens, everytime I click on a message to read it, in the task bar I can see that a ping on my IMAPX server is done. Definitely looks like the connection handler isn't stored correctly once it has failed.
Comment 10 Milan Crha 2014-02-10 16:23:49 UTC
I would try with 3.10.4 (released only today), maybe you see a side-effect of bug #702709.
Comment 11 Milan Bouchet-Valat 2014-02-13 10:57:27 UTC
Indeed, it fixes the problem! Thanks for the pointers.

*** This bug has been marked as a duplicate of bug 702709 ***
Comment 12 Milan Bouchet-Valat 2014-02-21 22:05:53 UTC
I spoke too soon. It worked for a few suspend/resume cycle, and then broke again. There must be something fishy going on (maybe the WiFi driver?).
Comment 13 Milan Crha 2014-05-20 05:16:32 UTC
I'm sorry for the often "try the latest version", but Matthew managed to write a code for better detection when the server is reachable or not, which depends on a GNetworkMonitor. This is available in 3.12.x only. I also made many changes in IMAPx code, some are surely good, which are part of the current 3.12.2. I hope it makes it work for you.
Comment 14 Milan Bouchet-Valat 2014-05-20 08:33:53 UTC
Requiring the new version is not a problem; what worries me is that very often the new version introduces one fix and another equally annoying bug, which means Evo offers a poor usability in all releases for me. :-/

I'll try 3.12.2.
Comment 15 Milan Crha 2015-03-05 21:18:28 UTC
We've got much further meanwhile, many maybe related fixes landed to the stable branch, which made the current 3.12.11 stable version. Not that much different from 3.12.9 (the difference are mostly crash fixes).

Please try with it or any newer version and report back. Thanks in advance.
Comment 16 Milan Bouchet-Valat 2015-03-06 20:11:08 UTC
Ah, sorry, forgot to report back. This started working again (likely when Fedora 21 was released). I'm now using 3.12.11 and I must say this is one of the most stable Evo releases in a few years. Keep it that way! :-)