GNOME Bugzilla – Bug 359615
Renamed folder remains under old name and cannot be deleted
Last modified: 2013-07-23 14:30:16 UTC
Please describe the problem: A folder that was renamed outside of Evolution (e.g. using Exchange webmail) remains under its old name and cannot be deleted from Evolution. An error occurs when clicking on its old name. Steps to reproduce: 1. Using Evolution connected to Exchange, create a new personal folder and place some mail in it. Note - my exchange settings have "Automatically synchronize account locally" turned on. Not sure if that is part of the cause. 2. Close Evolution. 3. Using Exchange webmail, rename the folder. 4. Open Evolution Actual results: After opening Evolution, the old folder name remains. Clicking on it results in the error "Error while opening folder exchange://<blah>/personal/<old_name>. Could not open folder". Right-clicking on the folder name and choosing "Delete" does nothing. Note that the new folder name exists and contains the email so there is no loss of data; just spurious folders remaining. Expected results: The old folder should no longer be present. Or, it should be possible to delete it. Does this happen every time? Every time. Other information: The problem is worse when you have a number of these folders. They take up space in the folder tree, but serve no purpose.
Note that this was with Exchange 2.8.1 from Ubuntu Edgy Eft - 2.8.1-0ubuntu1. The bug report form has no selection for version 2.8.x.
Would like to confirm this bug. Evolution does not seem to pick up on changes to the exchange folder tree made outside of evolution. Renaming or moving folders in Ms Outlook or the Outlook Web Access results in duplicate folders being displayed in Evolution, of which the old one cannot be opened and results in an error message. Some kind of exchange folder tree syncing seems to be needed. This bug also seems to be somewhat related: * http://bugzilla.gnome.org/show_bug.cgi?id=467585 * "Bug 467585 – Evolution should be able to sync new folders from Server without a restart (IMAP/GW/Exchange)"
I can confirm this bug. At my work (university) we also have a webmail client, which I use whenever I am on campus and do not have my laptop. I have created/renamed a few IMAP folders using the webmail client, deleted others. Evolution still thinks it sees the now-missing directories (but I get an error if I click on them) and cannot see the new directories. Evolution only sees the directories it has created. Have tried restarting the Evolution data connector, restarting the Evolution client, does not work. Client: Fedora 9 RPMs: evolution-2.22.3.1-1.fc9.i386 evolution-data-server-2.22.3-2.fc9.i386 evolution-data-server-devel-2.22.3-2.fc9.i386 evolution-data-server-doc-2.22.3-2.fc9.i386 evolution-help-2.22.3.1-1.fc9.i386 evolution-webcal-2.21.92-1.fc9.i386 Server: IMAP -jh
To clarify my comment: When I access my email using webmail, I do *not* have Evolution running on my laptop. My problem is not due to Evolution running at the same time I make a change to the IMAP folders using webmail.
Another scenario which I think relates to this bug: If you delete a folder outside of Evolution (eg, using webmail), then the folder remains in Evolution. If you try to delete the folder in evolution, nothing happens and the folder remains. Closing Evolution and restarting it did not clear the problem. The only work around I found was to create a new folder of the same name using webmail and then delete via Evolution.
Confirmed with 2.30, using IMAPX.
Correction: The remotely deleted folder was still present, and deleting it gave me an error message, but afterwards, evolution did no longer display it.
This report is **EXCHANGE specific**. If you encounter this problem with an IMAP/IMAPX account please file a separate bug against the product "Evolution".
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.