GNOME Bugzilla – Bug 350684
Subscribe to Folders causes the Connector backend to spin
Last modified: 2013-07-23 14:29:19 UTC
So, I finally got my exchange connector working correctly again today, so I went in to Folder->Subscriptions and selected my exchange account. I was watching the connector with E2K_DEBUG set to 2. When I opened the dialog, the connector started scanning the Exchange server. And when it finished, it started to scan again and again and again. When I hit close on the dialog, I got a lost connection to Exchange Backend and the window with the connector running continue to spin one last time. I was trying to use this to subscribe to some public folders. This seems to be a bug one way or another, but maybe this is the wrong place to subscribe to public folders, but I don't think so. Versions: evolution-2.7.91-1 evolution-connector-2.7.91-2 evolution-data-server-1.7.91-1 This is Fedora Rawhide.
Ryan, It is the correct place to subscribe to public folders. So, when you selected the exchange account in that dialog, you didn't get any public folders listed? can you paste the E2K_DEBUG traces and also the console log messages here?
The list actually comes up just fine, but the progress thing keeps moving (even though everything is listed there) and the connector keeps looping. The debug isn't going to show you much more than I said, it basically just loops through the folders over and over again.
Created attachment 70659 [details] bzipped Exchange output, showing loop If you look a bit down, you will see things like: SEARCH /public/Demo Calendars/ HTTP/1.1 Over and over again. This is what happened when I went in to the folder subscription dialog.
Another bug related to this is #347811.
Bumping version to a stable release.
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.