Hi there,

I recently switched from ownCloud to Open-Xchange. Migration of calendar and contacts was a bit tricky, but I got it working.

When I tried to connect Akonadi to the Open-Xchange server, I was glad to see there is an Open-Xchange resource. Unfortunately, the resource doesn't work: When testing the connection, the resource sends a HTTP request to the (proprietary?) API of the OX server with username and password in clear-text in the URL. The server then answers that, the "password" paramter in the URL is forbidden. I conclude this is because the Akonadi resource is for OX version 6 or older...

Fortunately OX also offers CalDAV / CardDAV connectors and so I used the Akonadi DAV resource to connect to the OX server. Basically this works good, but I have a problem with my contacts: Most of the (non empty) text fields contain an unprintable character. In the list of contacts, this character is visible as a clef at the end of the name. Opening the contact itself, the character is also selectable, e.g. in the "name" textfield. The URL field also provides a hint to the wrong character, as "%0D" is appended to the URL. The "%0D" is carriage return character. Copy-Pasting the unprintable character from another textfield to kate, saving this as an ASCII file and then displaying the hexdump also shows the carriage return character.
Logging into OX, I can't see any wrong characters in the Web-UI. Also my Android Phone with a CardDAV connector has no problem with the character. Changing a contact in KAddressbook saves the additional, wrong character to the server. This effectively corrupts my contact data and I have to manually remove the wrong carriage return from all text fields. So therefore I suspect the DAV resource to have a problem.

My guess is, that as OX is a Microsoft Exchange replacement for Microsoft Windows programs, the CardDAV resource of OX uses Windows line-endings (CRLF) and the Akonadi DAV resource can't handle this.

Does anyone know this problem? Or can someone tell me, how to change OX to use LF als line-ending or tell Akonadi to filter out the carriage return?


Thanks in advance!
Andreas

I experience the exact same problem. Saving contacts in KAddressbook leads to potentially unusable entries sometimes like john@example.comr or John Doer. Also, Data entered in KAddressbook becomes unusable in other frontends.

Example of vCard exported by KAddressbook: (Here, the data was saved outside of Kontact and is therefore usable)

Code: Select all

BEGIN:VCARD
VERSION:4.0
BDAY:1900-01-10T00:00:00
EMAIL;TYPE=INTERNET,HOME:john_doe@example.com\r
FN:John Doe\r
N:Doe\r;John;;;
PRODID:-//Open-Xchange//7.8.0-Rev20//EN\r
TEL:+1234567890123
TEL;TYPE=CELL;TYPE=PREF:+2134567890123
UID:5etd8ac4-9346-422f-be48-756595a6506b\r
END:VCARD


Same contact's vCard, exported from OX' web interface

Code: Select all

BEGIN:VCARD
VERSION:3.0
FN:John Doe
N:Doe;John;;;
EMAIL;TYPE=INTERNET,HOME:john_doe@example.com
...

KAddressbook, KMail (in the recipient form) and any pick-a-contact dialog I could find lists this contact as John Doe⌷ (here I have inserted a unicode character that looks like the 'I can't display this character'-box in kaddressbook), while the OX web interface, Android/Samsung contacts and K-9 on Android print John Doe correctly.

However, calendar data synchronised with the same OX server is not affected. The exported ics-files are the same (from KOrganizer and OX), no \r to be seen. It seems to be a specific problem with (CardDAV) contact data.

I use an OpenXchange service operated by mailbox.org and therefore do not have detailed knowledge of used versions or other technical details.
I would be happy to hear both from people with the same problem and without it, maybe there are some leads. I would also be happy to test other servers if there are any ready to just connect to via CardDAV.

Edit: Kontact version: 4:15.08.2-0ubuntu1 on Kubuntu 15.10

Please file a bug on bugs.kde.org, that's probably a bug that can be fixed.