evo-exchange doesn't work (error loading libcamelexchange.so)

Bug #17170 reported by Piers Cornwell
12
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Evolution-exchange no longer works. Following message is printed to the console
on startup (mailbox and URLs removed):

(evolution:10295): evolution-mail-WARNING **: couldn't get service
exchange://*;ad_server=*;owa_url=https://*;mailbox=*;owa_path=/Exchange: Could
not load /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so:
/usr/lib/evolution/2.2/libexchange.so.0: undefined symbol: ldap_ntlm_bind

Revision history for this message
Joe Barnett (thejoe) wrote :

I'm seeing the same thing with a slightly different error message

(evolution:14114): evolution-mail-WARNING **: couldn't get service
exchange://*/;filter;owa_path=exchange;mailbox=*;owa_url=*;ad_server=*: Could
not load /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so:
/usr/lib/libexchange-storage-1.2.so.0: undefined symbol: remove_folder_esource

Revision history for this message
Richard Ayotte (rich-casinoniagara) wrote :
Revision history for this message
Andrew Waldram (andrew-waldram) wrote :

Hi,

This has been fixed in HEAD since 15/7/2005 ,

There does not seem to be any work going on within Breezy to fix this(an update
of this bug would help), This error means NO MAIL for anyone who's using the
exchange-data-server to connect to an exchange server.

Though I agree this is probably only a small proportion of users the very fact
that a mail client cannot recieve mail is quite catastrophic.

I think the priority should be raised to P1 as I believe lower priority bugs are
being addressed ahead of this one.

Don't mean to sound condecending or non appreciative of the work done by Breezy
developer but this bug is annoying especialy when it has been fixed upstream 2
weeks ago.

Revision history for this message
Andrew Waldram (andrew-waldram) wrote :

Now thats what I call service

Fixed with latest update cheers

Revision history for this message
Jeff Bailey (jbailey) wrote :

Bug claims that it's fixed, closing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.