CalDav Issue with Leopard

[CdtDelta]

Hey all,
I'm thinking this might be a firewall issue, but I'm trying to get my CalDav integration working with Leopard based off the blog post today.
When I try to set up the connection, I get the following error:

Unexpected secure name resolution error (code -9813). The server name <zimbra server> may be incorrect.

Now I can connect to my Zimbra server just fine over https to use webmail. I'm assuming that CalDav uses the same port for that? I looked up the error in the forums and didn't see it.

Thanks ahead of time,
CdtDelta

[jholder]

hi CDT
Are you using any sort of proxying? CalDav is on what ever your http port is, so if you're using https be sure to put https in the box..

Anything in the /opt/zimbra/log/zmmailboxd.out file?

[CdtDelta]

Nope, just a firewall. I am using https only actually with the server. If I use http I'll get a port blocked error (or something like that).

There's nothing in the log file (and I mean there's nothing in the log file).

Is there an easy way to check the Zimbra version I'm running? I'm wondering if I ever upgraded to 5.0.2.

[danielfarrelly]

iCal on Leopard works great with Zimbra v5. In iCal, setup the account url like this:

https://yourmailserverhostname/princ...sers/cdtdelta/

Make sure the hostname is a FQDN.

[CdtDelta]

Ok well I updated to 5.0.2 and tried it again, still no joy. I am using the Open Source version if that makes a difference.
Is there something I need to enable on the Zimbra server in order to use CalDav? Or is it enabled by default?

Just looked at the logs on my Mac, and it's showing this when I try to connect:

Mar 18 13:20:16 Slave-1 iCal[597]: [DAVRequest _readStreamEvent]: SecTrustEvaluate failed. Failing with error: Error Domain=NSStreamSocketSSLErrorDomain Code=-9813 "Operation could not be completed. (NSStreamSocketSSLErrorDomain error -9813.)"
Mar 18 13:20:18 Slave-1 iCal[597]: *** -[NSLock dealloc]: lock (<NSLock: 0x16a19e00> '(null)') deallocated while still in use
Mar 18 13:20:18 Slave-1 iCal[597]: *** Break on _NSLockError() to debug.

[danielfarrelly]

Originally Posted by CdtDelta

Ok well I updated to 5.0.2 and tried it again, still no joy. I am using the Open Source version if that makes a difference.
Is there something I need to enable on the Zimbra server in order to use CalDav? Or is it enabled by default?

Just looked at the logs on my Mac, and it's showing this when I try to connect:

Mar 18 13:20:16 Slave-1 iCal[597]: [DAVRequest _readStreamEvent]: SecTrustEvaluate failed. Failing with error: Error Domain=NSStreamSocketSSLErrorDomain Code=-9813 "Operation could not be completed. (NSStreamSocketSSLErrorDomain error -9813.)"
Mar 18 13:20:18 Slave-1 iCal[597]: *** -[NSLock dealloc]: lock (<NSLock: 0x16a19e00> '(null)') deallocated while still in use
Mar 18 13:20:18 Slave-1 iCal[597]: *** Break on _NSLockError() to debug.

are your certificates okay? did you attempt to install a commercial cert and/or move a commercial cert from one server to another? if so, try reinstalling the certs manually. did you set zmtlsctl to redirect?

on another note, try Sunbird and see if you get the same errors. use both http & https.

[CdtDelta]

Originally Posted by danielfarrelly

are your certificates okay? did you attempt to install a commercial cert and/or move a commercial cert from one server to another? if so, try reinstalling the certs manually. did you set zmtlsctl to redirect?

on another note, try Sunbird and see if you get the same errors. use both http & https.

Nope, didn't touch certificates at all. I only have one server, this is for my personal mail (so there are only like three accounts on it).
No I did not set zmtlsctl to redirect. My server is set up for https only, and that's what I'm typing in the settings for iCal. I get a "connection refused" if I use http only.

[danielfarrelly]

we can maybe try some basic stuff. nmap and see what ports are open. what version of OS X are you running? amount of ram, processor, etc. do you have a fqdn and mx record pointing directly to an IP, or are you using a proxy of some sort. have you created any calendars other than the default "calendar"?

[jholder]

Are you able to use iCal against the hosted demo?

[Oinos]

I'd like to chime in and state that I'm having this very same issue, sans firewall. I'm on my local network with nothing between and getting the same error if I try to connect via https. If I try connecting via http, I can connect, but get a different error that warrants a thread of its own.

The particulars:

Release 5.0.4_GA_2101.RHEL5_64_20080321154100 CentOS5_64 FOSS edition

Mac OS X 10.5.2 - iCal 3.0.2