Bug 469713 - Evolution-zimbra unable to access Zimbra calendars
Evolution-zimbra unable to access Zimbra calendars
Product: Fedora
Classification: Fedora
Component: evolution-zimbra (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-03 11:53 EST by Jared Smith
Modified: 2008-11-03 14:47 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-03 13:35:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jared Smith 2008-11-03 11:53:00 EST
Description of problem:

Evolution (with the evolution-zimbra package) is unable to access Zimbra calendars

Version-Release number of selected component (if applicable):


How reproducible:


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.
Comment 1 Matthew Barnes 2008-11-03 12:56:39 EST
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


with appropriate substitutions for the domain and user names.
Comment 2 Jared Smith 2008-11-03 13:35:54 EST
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.
Comment 3 Matthew Barnes 2008-11-03 14:16:39 EST
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.
Comment 4 Jared Smith 2008-11-03 14:25:34 EST
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?
Comment 5 Matthew Barnes 2008-11-03 14:47:21 EST
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.

Note You need to log in before you can comment on or make changes to this bug.