Getting iCal Auto Complete to work

If iCal does not Auto-Complete the email addresses of invitees for events. Try following these steps to resolve the problem:

1. Remove the iCal CalDAVCalendaring extension to WebDAV that enables you to synchronize calendars. account and run the Auto-configure iCal tool. This tool can be found in your WebMail, go to Settings > Integration with Mac.
2. Go to the Directory Utility and check that the LDAPLightweight Directory Access Protocol - A protocol that enables users to access centrally managed contacts. entry for Kerio MailServer is at the top. You can find the Directory Utility in Leopard in Finder > Applications > Utilities > Directory Utility and, in Snow Leopard at OSX drive name > System > Library > CoreServices > Directory Utility.
3. Clear the local LDAP caches:

~/Library/Calendars

~/Library/Preferences

~/Library/Caches/com.apple.iCal

4. Check that the LDAP port is not blocked or being port forwarded to another machine in the network, such as the Open Directory machine.
5. Check that the SSL certificateSSL certificates are used to authenticate an identity on a server. is not out of date

If the problem still persists, please follow the next steps carefully as the problem may be with your PTR records:

1. Check that the Kerio MailServer LDAP service can be accessed from any computer by using the following command in Mac OSX Terminal:

ldapsearch –v –x –H ldap(s)://kms-server-address:LDAP port number

For example, ldapsearch –v –x –H ldaps://mail.company.com:636

If the search is successful, then you should see the following response:

# search result

Search:2

Result: 0 Success

2. If OpenLDAP answers successfully, then you need to check whether the PTR record is correct. You need to get the IP addressAn identifier assigned to devices connected to a TCP/IP network. of the MailServer hostname using nslookup:

nslookup [KMS hostname]

For example, nslookup mail.kerio.com

You should get this reponse in return:

Server: 192.168.10.10

Address: 192.168.10.10#53

Non-authoritative answer:

Name: mail.kerio.com

Address 63.197.252.130

Once you have this information, take a note of the IP address (in the example, it is 63.197.252.130). You can now perform a dig on this address to check the PTR record.

dig –x [IP Address]

For example, dig –x 63.197.252.130

You should get this reponse in return:

; <<>> DiG 9.4.1-P1 <<>> -x 63.197.252.130

;; QUESTION SECTION: ;130.252.197.63.in-addr.arpa. IN PTR

;; ANSWER SECTION: 130.252.197.63.in-addr. IN PTR 63-197-252-130.ded.pacbell.net.

;; SERVER: 192.168.10.10#53(192.168.10.10)

;; MSG SIZE rcvd: 89

You will now need to perform an nslookup on the PTR record to see if the record is pointing to a name for which there is no A record:

nslookup 63-197-252-130.ded.pacbell.net

You should get this reponse in return:

Server: 192.168.10.10
Address: 192.168.10.10#53
Non-authoritative answer:
Name: 63-197-252-130.ded.pacbell.net
Address: 195.39.55.2

You should get this reponse in return:

Server: 192.168.10.10
Address: 192.168.10.10#5
** server can't find 63-197-252-130.ded.pacbell.net.kerio.local: NXDOMAIN

If your PTR record has an incorrect response, then your local administrator will need to point the records to the correct location.

However after doing these tests (the test of the KMS LDAP Service is fine, the OpenLDAP works and the PTR records are correct) and running the Auto-Config tool still does not work, then please follow the steps below to enable logging, open a new ticket with the Kerio Technical Support Team and send us the logs in the ticket you create.

In Terminal application, type the following commands:

touch /Library/Preferences/DirectoryService/.DSLogDebugAtStart

sudo killall DirectoryService

1. Inspect Directory Service extended debug log:

/Library/Logs/DirectoryService/DirectoryService.debug.log

2. Inspect Directory Service standard debug log:

/Library/Logs/DirectoryService/DirectoryService.server.log

3. Rule out the problem from Directory Service logs and Kerio MailServer logs.
4. To disable Directory Service extended logging, run:

rm /Library/Preferences/DirectoryService/.DSLogDebugAtStart

sudo killall DirectoryService