Description of problem: Changes in the underlying network configuration, e.g. the route to a mail server, are not handled very well by Evolution. For example, it usually gets stuck when trying to check for new messages on an IMAP server that's now serviced by a different route (such as over a VPN), forcing me to kill it in order to not waste any more time. (Is Evolution keeping connections open when they're not being used for anything productive? More aggressive timeout, perhaps? Or have Evolution tear down all connections as soon as the network configuration changes?) Version-Release number of selected component (if applicable): evolution-3.0.3-1.fc15.x86_64 evolution-3.2.2-1.fc16.i686 How reproducible: Always. Steps to Reproduce: 0. Have VPN on hand to connect to a IMAP server. 1. Start Evolution, check e-mail. 2. Start VPN that becomes the route for that server. 3. Click "Send / Receive" and watch as there's no progress on that server. I've waited minutes for Evolution to give up and reconnect. Most cases I got fed up with waiting and killed and restarted Evolution. Actual results: Wait forever for Evolution to not reconnect to IMAP server. Expected results: I have to wait no more than 20 seconds for Evolution to give up and try reconnecting.
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. [1] https://bugzilla.gnome.org/show_bug.cgi?id=659873