Sorry for the multiple replies, but actually I was wrong on a couple things in my last post. It looks like the stock Android Contacts app exports as X-JABBER
Yes, the Android Contacts app exports vCard 2.0 (CardDAV requires vCard 3 or 4), and even a very “special” flavor of it. As I see it, these exported files can only be used for importing into Android Contacts again. I recommend to not use these exported files for anything else than for importing with the same app.
but the OS in general uses a different DB format and Conversations does work with DAVx5 / IMPP.
Works here, too. I use Conversations and XMPP addresses for contacts myself.
I continue to have to have the problem of phone numbers edited Android-side disappearing in Posteo on sync back. Edited emails don’t have this problem. Also, this occurs when using IMPP:xmpp:firstname.lastname@example.org as suggested
I have checked this and found:TYPE=MOBILE is not defined, neither in vCard 3 nor 4. So for DAVx⁵, this is a custom label, so it saves the phone number with “type: custom” and custom label: “Mobile”. When you edit the phone number on Android without changing the type, DAVx⁵ sends the phone number as: group1.TEL;TYPE=x-mobile:34243451343 group1.X-ABLabel:Mobile
using the X-ABLabel to retain the label.However, it seems the Posteo Web UI doesn’t understand vCard-compliant grouping and simply doesn’t show the phone number. If you then change the type to “Mobile” (not Custom: mobile) on Android and then sync, DAVx⁵ will upload TEL;TYPE=cell:.. and the phone number will be shown in Posteo as expected.
So:Can you please report the missing grouping support to Posteo? Please fix your vCards so they use TYPE=cell instead of TYPE=mobile, or you risk that things like this happen.