-
Notifications
You must be signed in to change notification settings - Fork 1
06 Known issues
Shubhra Prakash Nandi edited this page Jul 15, 2026
·
9 revisions
Below are a list of known issues and their possible workarounds.
- 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 in 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: It is important for the user to make sure that all required values are filled and all values are in correct format while creating, updating and importing contact(s) via CardDAV clients. Users can also use native debugging tools or sync logs provided by the CardDAV client to see why the contact failed to create/update in the server.
Important: The user 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 in the server.