[SOLVED] 6.0.2 is out.. CardDAV on Snow Leopard update?

[ganjo]

Just upgraded to 10.6.3 and immediately tested carddav.
Using only username (without @domain.tld, this is on the primary domain, so it works), password and server as https://domain.tld:443, Address Book accepts the settings and generates no errors at all. Still my existing contacts don't show and added contacts are not present in Zimbra. So it seems we went from an obvious error to a silent one.

Has anybody had more luck? This would be a great feature if it worked.

Strange

in fact its works: when I add a contact to adressbook, it is uploaded to zimbra server, BUT, the filename format seems different:
something like 04434c3b-1859-420a-bbc5-85f285098bda/258.vcf for zimbra
25CC1D18-C564-433E-B283-B653F0AE5575-ABSPlugin.vcf for adressbook
cause of this, they cannot see the contacts of the other

[chewitt]

I can see the same behaviour. After backing up AB.app I copied all of my contacts to Zimbra and then deleted the local 'on my mac' ones to prevent AB.app showing duplicates. In AB.app I can now see the Zimbra contacts fine, but if I look in Zimbra webmail none of them are visible. If I erase everything in Zimbra (via AB.app) and then import all my contacts into webmail using a vCard file they're visible to both apps, but in Zimbra I see extra info in the 'other' field that is unsightly (it looks like the filename examples you put above). I guess there's a few more iterations of tweaks needed on the Zimbra side, although the core functionality appears to be there now.

[dmwilliams]

I Can't get zimbra carddav working on snow leopard either.
the start of this thread was on 10-22-2009, and it is now 11-22-10
so it has been over a year and this problem has not been resolved

Has anybody been able to get zimbra carddav working with some other platform?
is it zimbra's or apple's fault?

[chewitt]

I'm not sure what issue you're having, but Apple made changes in an early 10.6.x release to solve the primary bug that stopped AB.app working against anything other than the OSX Server Address Book Server. It does work against Zimbra now, although I recall having to experiment with usernames and hostnames a little, and there are a few caveats on the Apple side still, like the non-sync'ing of AB groups, and Zimbra-side contacts not showing up in the iCal birthdays calendar or being sync'able to mobile devices via iSync.

[dmwilliams]

I'm not sure what issue you're having, but Apple made changes in an early 10.6.x release to solve the primary bug that stopped AB.app working against anything other than the OSX Server Address Book Server. It does work against Zimbra now, although I recall having to experiment with usernames and hostnames a little, and there are a few caveats on the Apple side still, like the non-sync'ing of AB groups, and Zimbra-side contacts not showing up in the iCal birthdays calendar or being sync'able to mobile devices via iSync.

I am pretty sure I have tried every permutation of usernames, domains, and ports.
I just get this "Shared Address Book configuration error" message.

[chewitt]

I am pretty sure I have tried every permutation of usernames, domains, and ports.
I just get this "Shared Address Book configuration error" message.

The username (in AB.app) needs to be the left side of your email address, e.g. for bob@somedomain.com you enter only 'bob'. Server address needs to be the FQDN associated with you email address domain, and you need to append :80 or :443 (as required) to the FQDN, e.g. mail.somedomain.com:80 else AB.app will attempt to connect on port 8800 (default for OSX Server). That works for me.

Do you have calendar access? ..I have a vague recollection that unless you have calendar (and thus CalDAV) in your COS, you don't get WebDAV access to your mailbox, and CardDAV requires it.

[dmwilliams]

The username (in AB.app) needs to be the left side of your email address, e.g. for bob@somedomain.com you enter only 'bob'. Server address needs to be the FQDN associated with you email address domain, and you need to append :80 or :443 (as required) to the FQDN, e.g. mail.somedomain.com:80 else AB.app will attempt to connect on port 8800 (default for OSX Server). That works for me.

Do you have calendar access? ..I have a vague recollection that unless you have calendar (and thus CalDAV) in your COS, you don't get WebDAV access to your mailbox, and CardDAV requires it.

I thought this might be the issue.
I was told by the provider that I have to use the whole email address.
my mail server is on a different domain mail.zimbraprovider.com
then my email address me@mydomain.com

is there any way I can get this to work?
I put an cname reccord and directed mail.mydomain.com to mail.zimbraprovider.com
then I tried using "me" as the username instead of me@mydomain.com
and I am not having luck with this either.

[dmwilliams]

I saw somebody was saying you should replace the @ sign in the username with &#64&#59;

but I have not been able to get this to work either.

[chewitt]

Adding the CNAME in DNS is only half of the job. Zimbra needs to be configured to associate the mail.yourdomain.com virtualhost with your domain else it just sees an inbound connection to the default domain of the server, and that's not where the 'me' mailbox exists. Have a look at the emails your provider sent when you bought the service. Most hosting companies auto-create virtualhosts like smtp/imap/pop/mail.domain.com etc. automatically when they provision you. If they didn't, just ask them to add it and you should be okay.

NB: iCal allows you to put the email address as the account name, but AB.app isn't as mature in figuring things out. You can use @, no need for &codes.

[StPaulie]

I am using 10.6.8 with ZCS6.0.6 and still no luck with CardDav.
Really hoping I can get this to work without having to use the Zimbra Connector