06 Known issues

Below are a list of known issues and their possible workarounds.

Contacts fail to create/update

1. When using a graphical user interface (GUI) based CardDAV client like Mozilla Thunderbird's native CardDAV address book, the client may fail to inform the user when a contact fails to create/update on the server. This may happen due to factors such as the contact may be missing data for a mandatory LDAP attribute (based on the field map of the address book in the conf file) or the contact may not have compatible data for a LDAP attribute like the telephone number. The user may never come to know of such a failure as the client may not show any sync status information against the contact and the associated reason for failure in the GUI.
   
   Workaround: Server administrators should inform the users about the fields which must be be filled in the GUI along with the format of data in the fields (as required by the LDAP attribute based on the field map of the address book in the conf file) while creating, updating and importing contact(s) via CardDAV clients. Users can use native debugging tools or sync logs provided by the CardDAV client to see why the contact failed to create/update on the server and report it to the server administrator.
   
   Important: Server administrator should inform the users that they should not discard any contact file (exported from another address book) used for importing contacts to the server before making sure that all the contacts in the file are present on the server.