- 1 General CALDAV Issues
- 2 Apple/Mac Issues
- 2.1 iCal Issues
- 2.1.1 Not seeing Calendar's
- 2.1.2 Entourage Use for Calendars - Leopard/10.5 users
- 2.1.3 Calendar events are displaying the wrong time
- 2.1.4 Attendee Lookups for iCALv3/MacOS10.5
- 2.1.5 Attendee Lookup for iCal/Mac 10.4
- 2.1.6 iCal calendar color changing modifies calendar name and/or doesn't retain color
- 2.1.7 New Calendars don't sync unless you select "all". Mac 10.4/Z-isync
- 2.1.8 Directory Access configuration on Macs
- 2.1.9 Mac clients cause spamming of invitation events when they adjust calendar events
- 2.1.10 Calendar Invites can't be imported into iCal
- 2.1.11 iTunes & iPhone configuration for CALDAV
- 2.1.12 Clearing iCal cache
- 2.2 Sync To Do/Tasks Items in Leopard
- 2.1 iCal Issues
- 3 What's my time and timezone?
- 4 Hostname resolution issues and testing commands
General CALDAV Issues
Lightning & Thunderbird
Lightning does not support Caldav + Free/Busy
Free/Busy support is only available for the Sun Cal Server.
Maybe we could "fake" this out within our Ldap configuration. Like RFE for Apple OD:
Address/username lookup doesn't occur within a new appointment
Unfortunately, I've not figured a way around this at this time.
Not seeing Calendar's
DO NOT USE SPACES
Entourage Use for Calendars - Leopard/10.5 users
Because of some core issues with Apple's SyncServices, we recommend that Entourage users use iCALv3 (Mac 10.5) configured for CALDAV. Please use the Zimbra Connector instructions to setup iCal for CALDAV. This recommedation also stems from the fact that Microsoft decided to use WebDAV rather than CALDAV for Entourage. If MS decides later to include CALDAV support for Entourage, we'll have another option.
Please see bug for details:
Calendar events are displaying the wrong time
Apple expects the year of 1971 for the DTSTART variable within an ICS file. There is no standard that dictates this.
Zimbra (prior to version 5.0.5) was using 1601, this is in /opt/zimbra/conf/timezones.ics .
Please see bug for more details (resolved 5.0.5):
Attendee Lookups for iCALv3/MacOS10.5
iCal3 [webdav] needs to use the Apple Directory Access utility for attendees (It's on 10.5). It will only work against Apple OD/CAL servers.
RFE filed to include necessary LDAP attributes to provide ical oattendee lookups
See bug [scheduled for 5.0.7]:
Attendee Lookup for iCal/Mac 10.4
iCal.app on Mac 10.4 only uses local entries in Apples Addressbook for address/username lookup for new appointments.
Addressbook+LDAP configuration requires a copy of an "all/*" search in ldap into the local addressbook. Sync doesn't seem to work.
Please see this bug comment and the 10.4 section for more details:
Free/Busy Lookup not working as expected
The Free/Busy lookup requires auto-attendee lookup to be working, this requires bug 26619 to be resolved.
iCal calendar color changing modifies calendar name and/or doesn't retain color
Fixed in 5.0.5 . See bugs for details:
New Calendars don't sync unless you select "all". Mac 10.4/Z-isync
Please see bug for details:
Directory Access configuration on Macs
File that configures [system wide] for Address Book resolution
Mac clients cause spamming of invitation events when they adjust calendar events
This, at it's root, is caused by other bugs listed here. Usually this will get resolved with the proper upgrades that the bugs require (ZCS 5.0.5+)
There is a RFE/Bug though that will also resolve this, by allowing the "action" of an appointment to be set.
Please see bug for details [scheduled for 5.0.7]:
Calendar Invites can't be imported into iCal
If you look at the ics file, you might see an extra return character at the end.
You'll see this if an Outlook client send an invite to a user using a Mac with a thick client [Mail.app/Entourage].
This was resolved in the 5.0.5 release. Please see bug for more details:
iTunes & iPhone configuration for CALDAV
Please see main wiki page on iPhone http://wiki.zimbra.com/index.php?title=IPhone
If you follow the instructions about configuring the Zimbra iSync Connector for CALDAV use, there should be no issues about sync'ing with your iPhone.
At this time, new events created on a iPhone/CALDAV setup will write the event to a local calendar in iCal.app . There's no way around this yet. It's a limitation at this time with Apple's software. You can change the events calendar assignment though later via iCal.app.
Please see Screenshot of iTunes & iPhone
Clearing iCal cache
Make and run script:
#!/bin/sh rm -rf '~/Library/Application Support/SyncServices/Local/clientdata/com.apple.iCal' rm -rf ~/Library/Calendars rm -rf ~/Library/Preferences/com.apple.iCal.plist rm -rf ~/Library/Caches/com.apple.iCal rm -rf ~/Library/Preferences/IcalExternalSync.plist rm -rf ~/Library/Preferences/ByHost/com.apple.iCal.helper.*
Sync To Do/Tasks Items in Leopard
RFE filed, please see http://bugzilla.zimbra.com/show_bug.cgi?id=12917
No target date, please vote for this RFE.
What's my time and timezone?
I wrote up the steps to make sure the ZCS server is using the correct time and timezone here:
Hostname resolution issues and testing commands
Allot of failed installs are because administrators are skipping the steps to make sure resolution is working.
Check your /etc/hosts file. You should have the localhost entry exactly as below. Your ZCS server name should be replaced with the zimbra.test.com and zimbra fields. The IP address should be the IP address bound to the network interface [ip addr or ifconfig -a to confirm].
127.0.0.1 localhost.localdomain localhost 192.168.0.1 zimbra.test.com zimbra
If your ZCS server is behind a firewall or is being NAT'd. Make sure that resolution for the hostname on the ZCS server returns the internal IP information rather than the external IP. To test:
hostname -f zimbra.test.com
domainname -f zimbra.test.com
As long as one of the above returns the full hostname, use the command for the following. The MX lookups depend on how you are doing your mail domain and server hostname.
host `hostname -f` zimbra.test.com has address 192.168.0.1 host -t MX `domainname -f` zimbra.test.com mail is handled by 10 zimbra.test.com. host -t MX `domainname -d` test.com mail is handled by 10 zimbra.test.com.
You should also have reverse records (PTR) as well. Replace 192.168.0.1 using your internal ip address, it should return something like:
host 192.168.0.1 188.8.131.52.in-addr.arpa domain name pointer zimbra.test.com
Please review wiki page on split-DNS :
and also the variable use of lmtp_host_lookup .