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 376072 - When "subscribing to other user's folder", Evolution attempts direct connection to server hosting targeted folder, instead of communicating only with server providing OWA
When "subscribing to other user's folder", Evolution attempts direct connecti...
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.26.x
Other All
: Normal enhancement
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2006-11-16 19:39 UTC by Matt Smith
Modified: 2013-07-23 14:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Snippet of evolution log at E2K_DEBUG=4 showing "subscribing to other user's folder" activity (2.42 KB, text/x-log)
2006-11-16 19:53 UTC, Matt Smith
Details
E2K_DEBUG=4 output with evolution-exchange version 2.26.0-0ubuntu3 (38.27 KB, text/plain)
2009-07-17 07:30 UTC, Lorant Nemeth
Details

Description Matt Smith 2006-11-16 19:39:49 UTC
We have a two-tier Exchange architecture, where the servers in the "front-end" tier run OWA, and the servers in the "back-end" tier host all mailboxes.  The back-end does not run OWA.  MAPI users connect directly to the back-end, but OWA users *only* connect to the front-end.

  Evolution is configured to use a front-end server (via the OWA URL).  When using "File->Subscribe to other user's folder", Evolution contacts the GAL to locate the target user's folder.  This folder is located on a back-end server. Evolution then tries to connect to this back-end server.  However, the back-end does not run OWA, and therefore a connection is impossible.  A "Generic Error" is returned.

  I am requesting a simple option that forces Evolution to only perform OWA communication through the server specified in the OWA URL, and not attempt communication directly with any other server.  In our environment, other user's folders are accessible using the format https://SERVERFQDN/exchange/USERNAME/FOLDERNAME .  I do not know if this URL format is a standard Exchange configuration, but if so, an option to allow this connection URL to be used against the front-end OWA servers to access other user's folders, instead of directly connecting to the back-end server, is desirable.
Comment 1 Matt Smith 2006-11-16 19:53:43 UTC
Created attachment 76724 [details]
Snippet of evolution log at E2K_DEBUG=4 showing "subscribing to other user's folder" activity

This file is a snippet of evolution log at E2K_DEBUG=4.  The log has been "cleaned" to remove my organization's information.  I have also reduced the log to show only the entries that were written during the "subscribing to other user's folder".  I can supply more log information, it will just take me time to clean the log data.

This log shows all GAL communication happenning correctly.  I am logged in as MYUSERNAME, attempting to view the calender of OTHERUSER.  Evolution correctly locates OTHERUSER's calendar on BACKENDSERVER, but since OWA does not run on BACKENDSERVER, Evolution cannot connect and display OTHERUSER's calendar.
Comment 2 George M. Harkin 2008-06-03 22:49:26 UTC
I have confirmed this behavior and also request an option that enabled by default.
Comment 3 Lorant Nemeth 2009-07-17 07:29:06 UTC
Problem still exist with: evolution-exchange 2.26.0-0ubuntu3
All evo components have been installed from ubuntu jaunty repo.
Attached you can find 'env E2K_DEBUG=4 evolution' output.
Scenario:
- start evolution
- switch to calendar
- select exchange calendar
- File -> Subscribe to other users calendar
- Select user nandor.galambosi from GAL
- Subscribe
- Generic Error

My user: lorant.nemeth
Searched user: nandor.galambosi


Let me know if you need any more info.
Comment 4 Lorant Nemeth 2009-07-17 07:30:59 UTC
Created attachment 138572 [details]
E2K_DEBUG=4 output with evolution-exchange version 2.26.0-0ubuntu3
Comment 5 André Klapper 2013-07-23 14:26:38 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.