While there's an Evolution 2.2 ebuild in ~arch, there is no matching Ximian connector ebuild and as Evolution requires the same version Ximian Connector in order for Exchange functionality to be available this poses a problbem for Evolution users wanting to test the new version and utilizing Exchange features. I created an updated ebuild but had to remove a patch for Exchange Authorization which I couldn't really find any documentation on. Reproducible: Always Steps to Reproduce: 1. Upgrade Evolution to anything greater than 2.0 2. Try to access Exchange server after upgrade 3. Actual Results: Account with Exchange server type is unavailabe in account lists. Expected Results: When matching Ximian Connector version is installed, Exchange support is available.
Sorry, but it does not work anywhere, this is not a Gentoo issue. You should complain to Novell. It
Sorry, but it does not work anywhere, this is not a Gentoo issue. You should complain to Novell. It´s FUBAR in every other Evolution release. :-( It is *said* to work again in 2.2.2 which is available now, I did not try yet. http://ftp.gnome.org/pub/GNOME/desktop/2.10/2.10.1/sources/
Hmm.. I'm not sure of that. I installed Ximian Connector 2.2.0 using a modified Ximian ebuild and Exchange support works correctly. It uses Ximian Connector 2.2.0 which is download from http://ftp.gnome.org/pub/GNOME/desktop/2.10/2.10.0/sources/. It just seems as though you have to have the matching versions of the Ximian Connector and Evolution. Regards,
Well, I tried 2.2.1 with Ubuntu and FC3 and _never_ got it working, with a lot of luck I was able to use it _once_ to connect to Exchange and on next start of Evolution it is totally screwed, unuseable... :/
i have a machine with FC4 beta installed. Evolution 2.2.1.1 and connector 2.2.1.1 work like charm.
Yeah I need the updated ximian-connector >= 2.2 as well for the new evolution.
Copying 2.0.2-r1 ebuild and deleting pkg_setup() function works for me.
I used the ebuilds from <a href="http://bugs.gentoo.org/show_bug.cgi?id=84971">this</a> bug report. Doesn't work. First thing evolution does is tell me the evolution-data-storage task quit unexpectedly.
Sorry, that should have been the first thing evolution does is tell me the evolution-exchange-storage task quit unexpectedly. No idea how to debug this further.
Created attachment 59728 [details] Upgrade to latest stable connector on Evolution site. This mail-client/ximian-connector ebuild depends on and will build with Evolution 2.2.1.1. It isn't in portage yet, so create a portage overlay if you don't have one, and do an "ebuild <filename> digest" on it. Then it should emerge.
(In reply to comment #8) > Sorry, that should have been the first thing evolution does is tell me the evolution-exchange-storage task quit unexpectedly. No idea how to debug this further. The evolution-exchange-storage process appears to be socket oriented, and it stays up when Evolution closes. Perhaps you could use "ps -efwww" to find out its command line, kill it with "evolution --force-shutdown", and run it under gdb with the same command line. Then, when it "quits unexpectedly", you can go see what gdb is showing. Maybe it's a segfault that needs to be reported to the developers.
(In reply to comment #0) >I created an updated ebuild but had to remove a patch for Exchange Authorization which I couldn't really find any documentation on. I needed that patch back when Evolution 2.0.2 as having user authentication problems. It was mishandling the domain extended user name. The patch does not appear to be needed any longer, since a user name can be specified with the domain name in front, as in "domain\username" in the user preferences. This causes the correct behavior during authentication. I've attached an ebuild to this bug which allows Evolution 2.2.1.1 to connect to Exchange servers. I haven't tested it with Evolution 2.2.2, but there is no reason the ebuild should not work. That is, unless a later ximian-connector isn't needed for Evolution 2.2.2. Let me know if there is such a requirement, and I'll put out another ebuild for it.
(In reply to comment #6) > Copying 2.0.2-r1 ebuild and deleting pkg_setup() function works for me. You need to change RDEPEND too, so ">=mail-client/evolution-2.0.2" becomes ">=mail-client/evolution-2.2.1". Otherwise the config phase of the connector compile will fail when it finds the old versions of the "developer libraries" which Evolution 2.0.2 has.
added ximian-connector 2.2.3 , fixed up deps (those listed in the ebuilds here were not quite correct). I cannot test this, so it's really up to you guys.
gnome-extra/evolution-data-server-1.2.1 mail-client/evolution-2.2.1.1 mail-client/ximian-connector-2.2.3 I'm getting the 'No mailbox for user xxxx' on what was a working setup under Evo 2.0.4/connector-2.0.2.
(In reply to comment #14) > gnome-extra/evolution-data-server-1.2.1 > mail-client/evolution-2.2.1.1 > mail-client/ximian-connector-2.2.3 > > I'm getting the 'No mailbox for user xxxx' on what was a working setup under Evo > 2.0.4/connector-2.0.2. > Can you login to your exchange account from another location such as webmail or Outlook? Last time I received that error, it was because my password expired.
