GNOME Bugzilla – Bug 348496
IMAP account gives many 'Cannot sync flags to folder' and 'Connection reset by peer' errors
Last modified: 2014-02-26 15:07:14 UTC
Please describe the problem: I have an IMAP account with blueyonder.co.uk and while Evolution is open, I periodically receive an error dialogue box saying: 'Error while Scanning folders in "IMAP server imap4.blueyonder.co.uk". IMAP4 server imap4.blueyonder.co.uk unexpectedly disconnected: Connection reset by peer' This seems to have no effect, as I still receive new mail on this account while Evolution is open. When a folder on this account is focused and I switch away from it, I quite often get an error dialogue box saying: 'Error while Refreshing folder. IMAP4 server imap4.blueyonder.co.uk unexpectedly disconnected: Connection reset by peer' or less commonly, unless I've been handling mail (I've moved all mailing lists and such away from this account due to these problems), an error dialogue declaring a failure to sync flags with folder. These errors not only have the effect of making Evolution really annoying to use with this account, but also that any mail in this account received while Evolution is open ends up unfiltered (where doing it manually sometimes works correctly, or results in the latter 'failed to sync flags' error and half-works, or doesn't work at all), and if I try to move the mail to other folders, I often end up with duplicate copies. If there is mail when Evolution is started, this mail is more likely to be filtered, but still is often missed. When using sylpheed with this account, I would receive errors saying that server-side threads weren't supported; when using Thunderbird, there are no problems with this account at all. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Sounds like a server issue to me... The server probably claims to support capabilities that actually are not.
Is there any way I can help debug this? The mail server works fine in Thunderbird and Outlook Express, if that's indicative of anything...
just sounds like your network connection is flaky to the IMAP server and the connection keeps getting dropped.
If that's the case, then Evolution's handling of flaky connections needs a *lot* of improvement - I end up with duplicated/unfiltered mails all over the place and warning dialog boxes that pop up pretty much every 10 minutes and interrupt my work flow (meaning I can't really leave Evolution open). There seems to be no problems checking the mail the first time when Evolution is opened though, which leads me to think this isn't the problem (that and Sylpheed also having problems, but Thunderbird/Outlook having none) Perhaps it could be considered to make error dialogs transient to the application window so that they don't interrupt you when the application is minimised?
I was thinking more along the lines of simply ignoring the exceptions
I've been working on the imap4 code a bit to make reconnecting seamless in the imap4-engine, to the point where the higher level imap4 implementation code (which just queues commands on the engine) doesn't ever have to know or care that the engine auto-reconnected. most of my experimentation code has been happening in libspruce, tho, and not camel itself... occasionally I sync the camel imap4 implementation w/ libspruce, so this problem may go away soon...
Many changes/fixes in IMAP4 has been committed for 2.24 cycle. Like 1) http://svn.gnome.org/viewvc/evolution-data-server?view=revision&revision=8783 2) http://svn.gnome.org/viewvc/evolution-data-server?view=revision&revision=8795
This was long ago, the IMAP backend changed in the meantime. Is it still an issue?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!