@rfc2822 said in Assigning pictures to Yandex contacts:

Before introducing complicated workarounds, I’d ask Yandex first.

A single boolean flag with “don’t exchange pictures/ignore server-supplied picture” semantics hardly qualifies as a “complicated workaround”. (Basically, “don’t use PHOTO field”.)

As for asking Yandex… I have. And all I got from them so far is a pair of links: one to their official CardDAV/CalDAV setup page, another - to 4pda.ru forum. Not exactly useful.

On the subject of complicated workarounds… A complicated workaround would be to store the encoded picture in the NOTE field of the contact card (with some additional markup, of course) and send it to Yandex that way. I tried and it appears that Yandex servers accept it, store it and then serve it back in its unspoiled form. So, that would actually work around Yandex refusal to store PHOTO… until they get wise to it, probably 🙂

@hexado @hexado said in Posteo X-JABBER:

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:j@j.com 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.

@rfc2822 Hi, thanks a lot for the prompt and comprehensive reply! I’ll follow the https://github.com/nextcloud/deck/issues/15 for updates.

@rfc2822 Thank you, this helps a lot, it is a subscription of a shared calendar of an openXchange suite. Seems this error has always been there, but ICSX5 has begun to fail just with the pre-former release. I will contact the server software provider…

I can confirm that 3.3.5 from F-Droid no longer has this issue. Thanks for the quick turnaround!

@mbiebl Yes, this has been fixed with Google Contacts 3.39. We’ll keep the page a bit for users who don’t update often, and then remove it.

@mikescandy Great that you found it anyway 🙂

As I understand it, it’s an eM Client problem, because it treats LABEL as a separate address. Please follow up here: https://forum.emclient.com/t/contacts-wont-display-address-in-column-when-vcard-uses-lower-case-type/45285/7

So, the Nokia support replies and said that this is an App issue of DAVx5 but I have to wait for future Updates of the Phone too 😵 The support isn´t good and the 7.2 is a buggy phone with a lot of problems. All updates and patches bringing new problems. I decided to send it back and buy another phone. I hope this will help.

I have added it to “Known problems” here, too: https://www.davx5.com/tested-with/icloud

Until this is fixed in the server, we have added a workaround which is shipped with DAVx5 3.1-rc1 (latest beta on Google Play). Does it work for you with 3.1-rc1 again?

Sorry I didn’t have time to try it during the weekend but I tested it now and it seems to be working.
Thank you for the quick fix!

Hi @rfc2822

thanks for the swift response - this is what I feared. Anyway, your very helpful FAQ page pointed me to a very nice alternative app (Etar) so I can even ditch Google Calendar completely - huray! 🙂

Keep up the great work you are doing on DavX5, I am a very happy long-time user.

All the best,
Simon

@rfc2822 Thanks for taking a look. 20191121T035347Z is exactly 90 days prior to when the request was made. Davx5 is configured to begin searching for events 90 days prior. I assumed CAL:time-range start=“20191121T035347Z indicated the start point for that range. Is that not the case? Nevermind, I misread your reply. I’ll look for broken events in that range and see what I can find. Thanks for your help.

Hello,

After DAVx⁵ has uploaded a task, the server replied with 204 No Content, which means that the task has been created correctly and there’s no further information about that.

A 204 response is terminated by the first empty line after the header fields because it cannot contain a message body.

In your case, the server has sent additional information (20 bytes) together with the status “there is no further information”, so this doesn’t make sense and can’t be processed.

It’s probably some misconfiguration of the server or the (reverse) proxy; please contact your admin for more information.

@cogliano Thanks for the update!

@schiri thank you for digging into this and reporting the outcome here. very appreciated! Glad that there is no issue on our side 😄 Recurring tasks and sub-tasks are supported in acalendar+ tasks and can be synced via DAVx5.

@martin-grotzke said in UID of imported invitation/event overwritten:

Then the issue is only, that for the first sync the ics that DAVx sends to SOGo does not contain METHOD:REPLY (and in consequence on organizer side the attendee status is not updated). But this METHOD:REPLY is set when I accept/decline the invitation after the initial sync was done.
Would it make sense to set METHOD:REPLY for the initial sync already if the organizer is not the attendee for that the invitation was accepted/declined?

DAVx⁵ never sets METHOD, because this is CalDAV Scheduling, which is not supported by DAVx⁵. The Android calendar provider doesn’t have the possibility to store the required fields for that.

But this METHOD:REPLY is set when I accept/decline the invitation after the initial sync was done.

I don’t understand that. Do you think DAVx⁵ sets METHOD:REPLY? It’s only possible that it keeps it as an “unknown property” when it has received it from the server.

Thanks for the whole file, I’ll have a look.

Yes this helped, thank you 🙂