Re: [Evolution] Yandex Caldav/Carddav

2017-02-16 Thread Patrick O'Callaghan
On Thu, 2017-02-16 at 11:00 +0300, Sergey Makeev wrote: > I was told that I hadn't been a registered member and therefore was not > authorized to post messages. [Please don't top-post on this list] Since you did post the message, a moderator must have approved it if you hadn't subscribed. And of

Re: [Evolution] Yandex Caldav/Carddav

2017-02-16 Thread Sergey Makeev
I was told that I hadn't been a registered member and therefore was not authorized##SELECTION_END## to post messages. Исходное сообщение От: Milan Crha <mc...@redhat.com> Кому: evolution-list@gnome.org Тема: Re: [Evolution] Yandex Caldav/Carddav Дата: Wed, 15 Feb 2017 19

Re: [Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Andre Klapper
On Thu, 2017-02-16 at 00:29 +0300, Sergey Makeev wrote: > Ok, ok, I will try to provide you debugging infi as descrived. > Meanwhile, why don't you register a test Yandex account and reproduce the > experiment in your home laboratory? I cannot speak for others, but my spare time is not unlimited

Re: [Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Sergey Makeev
Ok, ok, I will try to provide you debugging infi as descrived. Meanwhile, why don't you register a test Yandex account and reproduce the experiment in your home laboratory? Sergey Makeev Le noble russe Adam Tauno Williams 16 февраля 2017 г. 0:15:44 написал: > Quoting

Re: [Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Adam Tauno Williams
Quoting Sergey Makeev : Server side workes fine with Outlook Caldav Synchronizer, DavDroid, eMClient. Client side needs ti break connectiin after each request. NO, that is not how this process works. You are ***assuming*** you know the cause of the problem - and I am

Re: [Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Sergey Makeev
Server side workes fine with Outlook Caldav Synchronizer, DavDroid, eMClient. Client side needs ti break connectiin after each request. Sergey Makeev Le noble russe Adam Tauno Williams 15 февраля 2017 г. 21:41:06 написал: > Quoting Sergey Makeev :

Re: [Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Adam Tauno Williams
Quoting Sergey Makeev : Yandex have CalDAV and CardDAV servers and Evolution connects to them. One can create meetings, appointments, tasks and contacts. But when one tries to modify an entry within meeting, appointment, task or contact Evolution returns an error with code 200

Re: [Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Milan Crha
On Wed, 2017-02-15 at 19:03 +0300, Sergey Makeev wrote: > Could you please implement similar function of fix communication with > Yandex CalDAV/CardDAV servers once and for ever? Hi, you started such thread already, but it doesn't seem you follow it, because you already received responses

[Evolution] Yandex Caldav/Carddav

2017-02-15 Thread Sergey Makeev
Yandex have CalDAV and CardDAV servers and Evolution connects to them. One can create meetings, appointments, tasks and contacts. But when one tries to modify an entry within meeting, appointment, task or contact Evolution returns an error with code 200 (OK) (sic!). Thats for the first time. For

Re: [Evolution] Yandex Caldav/Carddav

2017-02-14 Thread Milan Crha
On Mon, 2017-02-13 at 23:42 +0300, Sergey Makeev wrote: > Caldav Synchronizer for MS Outlook requires to fill-in the check box > "Break connection after each request". Hi, you probably mean "Close connection after each request". That's always done with CalDAV/WebDAV calendar/book. > Whet

Re: [Evolution] Yandex Caldav/Carddav

2017-02-14 Thread Patrick O'Callaghan
On Mon, 2017-02-13 at 23:42 +0300, Sergey Makeev wrote: > Caldav Synchronizer for MS Outlook requires to fill-in the check box > "Break connection after each request". > > Whet one tries to modify an entry of a meeting, task or contact stored > by Evolution for the first time it says that there

[Evolution] Yandex Caldav/Carddav

2017-02-14 Thread Sergey Makeev
Caldav Synchronizer for MS Outlook requires to fill-in the check box "Break connection after each request". Whet one tries to modify an entry of a meeting, task or contact stored by Evolution for the first time it says that there was a mistake with event code 200 (Ok), and for the second time it