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 307175 - Connector tries to use Public Folder server as Mailbox Server
Connector tries to use Public Folder server as Mailbox Server
Status: RESOLVED WONTFIX
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.12.x
Other Linux
: Normal major
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
gnome[unmaintained]
Depends on:
Blocks: 327514
 
 
Reported: 2005-06-10 16:45 UTC by RoadRunn
Modified: 2013-07-23 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
E2K_DEBUG=5 log (9.86 KB, text/plain)
2005-06-10 16:51 UTC, RoadRunn
Details
Screen shot (107.98 KB, image/png)
2005-06-10 17:03 UTC, RoadRunn
Details

Description RoadRunn 2005-06-10 16:45:10 UTC
Version details: Ximian-Connector-2.2.1
Distribution/Version: Gentoo Linux 2005.0

In my organization the mailbox OWA server is different than the Public Folder
OWA server. Durring the debug, you can see Ximian Connector connect to the
correct mailbox server, then it finds the link to Public Folders, and tries to
use that as the mailbox server. I then get a "mailbox for <username> no on this
server" and the debug says it is trying to pull it from the public folder server.
Comment 1 RoadRunn 2005-06-10 16:51:36 UTC
Created attachment 47558 [details]
E2K_DEBUG=5 log
Comment 2 RoadRunn 2005-06-10 17:03:35 UTC
Created attachment 47559 [details]
Screen shot

Screen shot of errors trying to use public folder server as mailbox server
Comment 3 Han Pilmeyer 2005-12-15 13:54:16 UTC
I had exactly the same problem. When using ximian-connector-setup-2.4 (same with
2.2), you need to enter the address of the Global Catalog replica server since
it can not find it. Someone mentioned that if you add an entry to your hosts
file that point the server which names is given on the failure message to the IP
address of the server that has your mailbox (same one as for the OWA URL), then
it will work. I tried that and indeed that worked around the problem.
Comment 4 Stefan Becker 2007-11-29 08:56:28 UTC
This bug still exists in Evolution Exchange 2.12.1.

Can you please look at this again?
Comment 5 Matthew Barnes 2008-03-11 00:50:28 UTC
Bumping version to a stable release.
Comment 6 André Klapper 2012-01-04 12:23:56 UTC
Sorry that this report has not received attention earlier.

Note that the package "evolution-exchange" is deprecated nowadays. Similar
functionality is now provided by "evolution-mapi" and "evolution-ews" packages.

This bug was reported against a version that is now not supported anymore.
Could you please check if the problem that you reported here still happens with
a recent version of Evolution (like 3.2 or 3.0) AND with either evolution-mapi
or evolution-ews? Thanks in advance!
Comment 7 André Klapper 2012-09-20 14:52:37 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 8 André Klapper 2013-07-23 14:32:52 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.