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 325960 - Subscribed mail folders and public mail folders appear only after restarting Evolution
Subscribed mail folders and public mail folders appear only after restarting ...
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other Linux
: Normal normal
: 2.5
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
: 328812 (view as bug list)
Depends on:
Blocks: 327514 339777
 
 
Reported: 2006-01-06 09:23 UTC by Sushma Rai
Modified: 2013-07-23 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch (1.96 KB, patch)
2006-04-21 04:15 UTC, Sushma Rai
needs-work Details | Review

Description Sushma Rai 2006-01-06 09:23:49 UTC
After succesfully subscribing to other users folder, to see the
subscribed folder evolution, e-d-s and exchange-storage needs to be 
restarted.
Comment 1 Poornima 2006-02-17 06:31:18 UTC
This is reproducible even in evolution 2.5.9.
Comment 2 Sushma Rai 2006-03-08 12:08:00 UTC
 Opened by Poornima    (points: 20)
2006-01-27 09:15 UTC [reply]

Goto 'Folder->Subscriptions, select public mail, contact, calendar and task
folder.
Check only in mail view the subscribed public folder is not displayed.
Comment 3 Sushma Rai 2006-03-08 12:08:18 UTC
*** Bug 328812 has been marked as a duplicate of this bug. ***
Comment 4 Sushma Rai 2006-04-20 11:07:11 UTC
Now the public folders are working are accessible even without
restarting Evolution. Only subcribed folders requires restarting 
of Evolution.
Comment 5 Sushma Rai 2006-04-21 04:15:55 UTC
Created attachment 64000 [details] [review]
Patch

This patch fixes the issue of accessing subscribed non-mail folders.
With this now
Accessing first *mail* public folder and Accessing all subscribed *mail* 
folders require Evolution to be restarted, and rest of the folders 
should work fine.
Comment 6 Veerapuram Varadhan 2007-08-23 12:56:49 UTC
(In reply to comment #5)
> Created an attachment (id=64000) [edit]
> Patch
> 
> This patch fixes the issue of accessing subscribed non-mail folders.
> With this now
> Accessing first *mail* public folder and Accessing all subscribed *mail* 
> folders require Evolution to be restarted, and rest of the folders 
> should work fine.
> 

Rescanning the whole tree is a performance glitch - rather we need to see how we can rescan only the foreign hierarchy.  Marking the patch as "needs-work".
Comment 7 Matthew Barnes 2008-03-11 00:51:52 UTC
Bumping version to a stable release.
Comment 8 André Klapper 2012-09-20 14:53:12 UTC
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".
Comment 9 André Klapper 2013-07-23 14:33:30 UTC
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.