Red Hat Bugzilla – Bug 469713
Evolution-zimbra unable to access Zimbra calendars
Last modified: 2008-11-03 14:47:21 EST
Description of problem: Evolution (with the evolution-zimbra package) is unable to access Zimbra calendars Version-Release number of selected component (if applicable): evolution-help-2.24.1-2.fc10.x86_64 evolution-webcal-2.23.91-1.fc10.x86_64 evolution-bogofilter-2.24.1-2.fc10.x86_64 evolution-data-server-doc-2.24.1-2.fc10.x86_64 evolution-zimbra-0.1.1-3.fc10.x86_64 evolution-sharp-devel-0.18.0-1.fc10.x86_64 evolution-brutus-1.2.27-2.fc10.x86_64 evolution-data-server-2.24.1-2.fc10.x86_64 evolution-data-server-devel-2.24.1-2.fc10.x86_64 evolution-conduits-2.24.1-2.fc10.x86_64 evolution-spamassassin-2.24.1-2.fc10.x86_64 evolution-sharp-0.18.0-1.fc10.x86_64 evolution-2.24.1-2.fc10.x86_64 evolution-rspam-0.0.6-4.fc10.x86_64 How reproducible: Always Steps to Reproduce: 1. Open Evolution 2. Create a new account of type "Zimbra" 3. Open the Calendar 4. Notice that appointments on the Zimbra calendar aren't displayed 5. Try to add an appointment to a Zimbra calendar Actual results: A dialog box appears that says "Unable to open the calendar 'Calendar'." Expected results: I expect to be able to see existing appointments on the calendar, and to add new appointments to the calendar. Additional info: If I run evolution from within a terminal window, I see the following: (evolution:17367): e-utils-WARNING **: Cannot resolve symbol 'com_zimbra_new_calendar_setup' in plugin '/usr/lib64/evolution/2.24/plugins/libcom-zimbra-account-setup.so' (not exported?) I'm not 100% sure it's related, but it sure sounds like it might be related to me.
If you're accessing a Zimbra 5 server, Evolution's CalDAV support is greatly improved in version 2.24. I'd recommend that over evolution-zimbra. The URL for the CalDAV calendar should look something like caldav://zimbra.server.hostname/dav/USERNAME/Calendar with appropriate substitutions for the domain and user names.
Thanks Matthew... that did the trick. I just had to know the magic path (replacing "home" with "dav" in the URI) to make Zimbra happy. Now, let me play Captain Obvious here and ask a silly question. If someone is using the Zimbra connector and it realizes it's talking to a Zimbra 5 server, shouldn't it at least fail gracefully and say "Hey buddy, you may wanna try CalDAV instead!" Or is that just me being overly optimistic? In any case, I'll go ahead and close this ticket, as I've obviously found a workaround.
Ideally, I'd agree. The Zimbra connector was incomplete to begin with and it's no longer under active development, so my long-term goal for the thing is to drop support for older Zimbra versions and turn it into an Evolution extension that automates the configuration process as much as possible -- setting up an IMAP account, LDAP address book, and CalDAV calendar for you. Kinda like what Evolution-Exchange does.
OK, that sounds like a plan. The one thing that CalDAV doesn't seem to be doing (that the Zimbra connector does) is automatically update an appointment when I receive an email informing me of a change to said appointment. With CalDAV, it seems I'm forced to log into the web interface of Zimbra, accept the change, and then it shows up in my CalDAV calendar. Is there an easy work-around for that currently? (And I'm sorry... I realize that this ticket probably isn't the best support forum. I'm just happy to have found an avenue to talk to someone with a clue about how this all works.) Also, do you know the magic incantation to get the Zimbra GAL to work in Evolution?
Not sure. Mind filing a new bug about the CalDAV update issue? Unfortunately I don't have access to a Zimbra server running LDAP at the moment, but the Zimbra forums might hold some clues. Sorry I couldn't be of more help there; I'm kind of researching this at the moment myself.