Zarafa Caldav Calendar not found

When trying to access my Zarafa calendar using CalDAV, I get an error message telling me no calendars were found.

I only have one default calendar on the Zarafa server. Unfortunately it’s an SSL server, so I can not provide a TCP dump. Is there any way to log the communication from within Rainlendar, so I can provide some more useful information?

You can enable the debugging in Rainlendar and check from the debug log what exactly the server sends to Rainlendar.

Ah thank you, it looks like Rainlendar can not find the calendar resource.

When using Zarafa the calendar URL is:

<server>/caldav/<user>/<calendar-name>

Using a browser, I can download my default calender as one ICS file with this URL:

<server>/caldav/amn/Calendar

When connecting to the URL using a WebDAV client, I can actually see all the ics files for each calender event.

Here is a stripped down version of the logfile I got when trying to add the caldav calendar resource. I replaced the server name and my personal information.

Maybe you can see what’s wrong here. I’m not much into the CalDAV protcol and I didn’t check the RFC yet.

21:39:06: [0:00:51.137] Dummy: Checking options: <server>/caldav/amn/Calendar
21:39:06: [0:00:51.346] Dummy: CURLINFO_TEXT: Server auth using Basic with user \'amn\'
21:39:06: [0:00:51.346] Dummy: CURLINFO_HEADER_OUT: OPTIONS /caldav/amn/Calendar HTTP/1.1
Authorization:<REMOVED FROM LOG>
User-Agent: Rainlendar-CalDAVPlugin/1.0
Host: <server>
Accept: */*
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: HTTP/1.1 200 OK
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: Allow: OPTIONS, GET, POST, PUT, DELETE, MOVE
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: Allow: PROPFIND, PROPPATCH, REPORT, MKCALENDAR
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: Content-Length: 0
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: Server: Zarafa
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: Date: Wed, 05 Feb 2014 20:38:53 GMT
21:39:06: [0:00:51.416] Dummy: CURLINFO_HEADER_IN: Connection: close
21:39:06: [0:00:51.416] Dummy: CURLINFO_TEXT: Closing connection #0

21:39:06: [0:00:51.419] Dummy: Making request: <server>/caldav/amn/Calendar
21:39:06: [0:00:51.613] Dummy: CURLINFO_TEXT: Server auth using Basic with user \'amn\'
21:39:06: [0:00:51.613] Dummy: CURLINFO_HEADER_OUT: PROPFIND /caldav/amn/Calendar HTTP/1.1
Authorization:<REMOVED FROM LOG>
User-Agent: Rainlendar-CalDAVPlugin/1.0
Host: <server>
Accept: */*
Content-Type: application/xml; charset=\"utf-8\"
DEPTH:0
Content-Length: 204
Expect: 100-continue
21:39:07: [0:00:52.615] Dummy: CURLINFO_TEXT: Done waiting for 100-continue
21:39:07: [0:00:52.615] Dummy: CURLINFO_DATA_OUT: <?xml version=\"1.0\" encoding=\"utf-8\" ?>
<D:propfind xmlns:D=\"DAV:\" xmlns:C=\"urn:ietf:params:xml:ns:caldav\"><D:prop><D:current-user-principal/><D:principal-URL/><C:calendar-home-set/></D:prop></D:propfind>
21:39:07: [0:00:52.615] Dummy: CURLINFO_TEXT: We are completely uploaded and fine
21:39:07: [0:00:52.787] Dummy: CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status
21:39:07: [0:00:52.787] Dummy: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
21:39:07: [0:00:52.788] Dummy: CURLINFO_HEADER_IN: Content-Type: application/xml; charset=\"utf-8\"
21:39:07: [0:00:52.788] Dummy: CURLINFO_HEADER_IN: Content-Length: 558
21:39:07: [0:00:52.788] Dummy: CURLINFO_HEADER_IN: Server: Zarafa
21:39:07: [0:00:52.788] Dummy: CURLINFO_HEADER_IN: Date: Wed, 05 Feb 2014 20:38:55 GMT
21:39:07: [0:00:52.788] Dummy: CURLINFO_HEADER_IN: Connection: close
21:39:07: [0:00:52.788] Dummy: CURLINFO_HEADER_IN:
21:39:07: [0:00:52.789] Dummy: CURLINFO_DATA_IN: <?xml version=\"1.0\" encoding=\"UTF-8\"?>
<C:multistatus xmlns:D=\"urn:ietf:params:xml:ns:caldav\" xmlns:C=\"DAV:\">
 <C:response>
  <C:href>/caldav/amn/Calendar</C:href>
  <C:propstat>
   <C:prop>
    <C:current-user-principal>
     <C:href>/caldav/amn/</C:href>
    </C:current-user-principal>
    <C:principal-URL>
     <C:href>/caldav/amn/</C:href>
    </C:principal-URL>
    <D:calendar-home-set>
     <C:href>/caldav/amn/</C:href>
    </D:calendar-home-set>
   </C:prop>
   <C:status>HTTP/1.1 200 OK</C:status>
  </C:propstat>
 </C:response>
</C:multistatus>
21:39:07: [0:00:52.789] Dummy: CURLINFO_TEXT: Closing connection #0

21:39:07: [0:00:52.793] Dummy: Making request: <server>/caldav/amn/
21:39:08: [0:00:52.992] Dummy: CURLINFO_TEXT: Server auth using Basic with user \'amn\'
21:39:08: [0:00:52.992] Dummy: CURLINFO_HEADER_OUT: PROPFIND /caldav/amn/ HTTP/1.1
Authorization:<REMOVED FROM LOG>
User-Agent: Rainlendar-CalDAVPlugin/1.0
Host: <server>
Accept: */*
Content-Type: application/xml; charset=\"utf-8\"
DEPTH:1
Content-Length: 170
Expect: 100-continue
21:39:09: [0:00:53.993] Dummy: CURLINFO_TEXT: Done waiting for 100-continue
21:39:09: [0:00:53.994] Dummy: CURLINFO_DATA_OUT: <?xml version=\"1.0\" encoding=\"utf-8\" ?>
<D:propfind xmlns:D=\"DAV:\" xmlns:C=\"urn:ietf:params:xml:ns:caldav\"><D:prop><D:displayname/><D:resourcetype/></D:prop></D:propfind>
21:39:09: [0:00:53.994] Dummy: CURLINFO_TEXT: We are completely uploaded and fine
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: Content-Type: application/xml; charset=\"utf-8\"
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: Content-Length: 369
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: Server: Zarafa
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: Date: Wed, 05 Feb 2014 20:38:56 GMT
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN: Connection: close
21:39:09: [0:00:54.115] Dummy: CURLINFO_HEADER_IN:
21:39:09: [0:00:54.116] Dummy: CURLINFO_DATA_IN: <?xml version=\"1.0\" encoding=\"UTF-8\"?>
<C:multistatus xmlns:C=\"DAV:\">
 <C:response>
  <C:href>/caldav/amn/</C:href>
  <C:propstat>
   <C:prop>
    <C:displayname>John Doe</C:displayname>
    <C:resourcetype>
     <C:collection/>
    </C:resourcetype>
   </C:prop>
   <C:status>HTTP/1.1 200 OK</C:status>
  </C:propstat>
 </C:response>
</C:multistatus>
21:39:09: [0:00:54.116] Dummy: CURLINFO_TEXT: Closing connection #0

21:39:09: [0:00:54.120] DEBUG: Dummy: John Doe was ignored since its resource type is not calendar

The server doesn’t return the calendar resource so Rainlendar cannot get the list of calendars. You could try to go through the new calendar wizard in Rainlendar even though it cannot find the calendars. Then set the url to the calendar’s properties directly and see if you can download the events that way.

Temar, did you solve the problem at the time? The same is now in Kopano (formerly Zarafa).

And i can’t find the url for my calender…

Thx
Frank

Hello everybody,

is the problem solved right now? Unfortunatley I can either connect to the kopano ical calendar in a sort of read-mode or I can connect to it with the possibility of writing appointments but not reading them :blink:

I’ll explain what I did:
To get the kopano-calendar to be shown by rainlendar I added a network-calendar and used the URL /<URLofKopanoServer:8443>/caldav/<UsernameOfKopanoUser>

I added the options ‘write-only’ and ‘use local copy’

This worked fine. Here the main parts of the debug:

[code]16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: HTTP/1.1 200 OK
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Etag: 1571226657
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Content-Type: text/calendar; charset=“utf-8”
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Content-Disposition: attachment; filename=“Calendar.ics”
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Content-Length: 1309571
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Server: Kopano
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Date: Wed, 16 Oct 2019 14:50:52 GMT
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN: Connection: close
16:50:52: [0:00:22.558] Kalender Marco: CURLINFO_HEADER_IN:
16:50:52: [0:00:22.573] Kalender Marco: CURLINFO_DATA_IN: BEGIN:VCALENDAR

VERSION:2.0

PRODID:-//Kopano//8.7.81//EN
[/code]

With this way of configuration I am not able to alter or ad new appointments. When removing the option ‘calendar write protected’ and trying to do so I get the following error:

Network error calendar ...
Error while uploading data to:
URL...
answer of server: 404 Not Found

On the other hand - when adding a CalDAV calendar in Rainlendar by using the format /<URLofKopanoServer:8443/caldav/<NameOfKopanoUser>/calendar
the actual calendar is not downloaded - the debug says:

17:33:03: [0:00:07.512] Calendar: CURLINFO_TEXT: Done waiting for 100-continue
17:33:03: [0:00:07.512] Calendar: CURLINFO_DATA_OUT: <?xml version=\"1.0\" encoding=\"utf-8\" ?>
<D:propfind xmlns:D=\"DAV:\" xmlns:C=\"urn:ietf:params:xml:ns:caldav\"><D:prop><D:current-user-principal/><D:principal-URL/><C:calendar-home-set/></D:prop></D:propfind>
17:33:03: [0:00:07.512] Calendar: CURLINFO_TEXT: We are completely uploaded and fine
17:33:03: [0:00:07.604] Calendar: CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status
17:33:03: [0:00:07.604] Calendar: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
17:33:03: [0:00:07.604] Calendar: CURLINFO_HEADER_IN: Content-Type: application/xml; charset=\"utf-8\"
17:33:03: [0:00:07.604] Calendar: CURLINFO_HEADER_IN: Content-Length: 602
17:33:03: [0:00:07.605] Calendar: CURLINFO_HEADER_IN: Server: Kopano
17:33:03: [0:00:07.605] Calendar: CURLINFO_HEADER_IN: Date: Wed, 16 Oct 2019 15:33:03 GMT
17:33:03: [0:00:07.605] Calendar: CURLINFO_HEADER_IN: Connection: close
17:33:03: [0:00:07.605] Calendar: CURLINFO_HEADER_IN:
17:33:03: [0:00:07.618] Calendar: CURLINFO_DATA_IN: <?xml version=\"1.0\" encoding=\"UTF-8\"?>
<C:multistatus xmlns:D=\"urn:ietf:params:xml:ns:caldav\" xmlns:C=\"DAV:\">
 <C:response>
  <C:href>/caldav/marco.hoffmann/Kalender</C:href>
  <C:propstat>
   <C:prop>
    <C:current-user-principal>
     <C:href>/caldav/marco.hoffmann/</C:href>
    </C:current-user-principal>
    <C:principal-URL>
     <C:href>/caldav/marco.hoffmann/</C:href>
    </C:principal-URL>
    <D:calendar-home-set>
     <C:href>/caldav/marco.hoffmann/</C:href>
    </D:calendar-home-set>
   </C:prop>
   <C:status>HTTP/1.1 200 OK</C:status>
  </C:propstat>
 </C:response>
</C:multistatus>
17:33:03: [0:00:07.618] Calendar: CURLINFO_TEXT: Closing connection 0
17:33:03: [0:00:07.618] Calendar: CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):
17:33:03: [0:00:07.618] Calendar: 
17:33:03: [0:00:07.618] Calendar: Result: (0) 207 Multi-Status.
17:33:03: [0:00:07.619] DEBUG: Calendar: The CalDAV Url: URLofKopano>:8443/caldav/marco.hoffmann/
17:33:03: [0:00:07.619] Calendar: CURLINFO_TEXT: Hostname was NOT found in DNS cache
17:33:03: [0:00:07.632] Calendar: CURLINFO_TEXT:   Trying 89.X...
17:33:03: [0:00:07.652] Calendar: CURLINFO_TEXT: Connected to URLofKopano> port 8443 (#0)
17:33:03: [0:00:07.652] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Client hello (1):
17:33:03: [0:00:07.652] Calendar: 
17:33:03: [0:00:07.699] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server hello (2):
17:33:03: [0:00:07.699] Calendar: 
17:33:03: [0:00:07.699] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, CERT (11):
17:33:03: [0:00:07.700] Calendar: 
17:33:03: [0:00:07.700] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server key exchange (12):
17:33:03: [0:00:07.700] Calendar: 
17:33:03: [0:00:07.702] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server finished (14):
17:33:03: [0:00:07.702] Calendar: 
17:33:03: [0:00:07.715] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Client key exchange (16):
17:33:03: [0:00:07.715] Calendar: 
17:33:03: [0:00:07.715] Calendar: CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):
17:33:03: [0:00:07.715] Calendar: 
17:33:03: [0:00:07.716] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):
17:33:03: [0:00:07.716] Calendar: 
17:33:03: [0:00:07.725] Calendar: CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):
17:33:03: [0:00:07.725] Calendar: 
17:33:03: [0:00:07.725] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):
17:33:03: [0:00:07.725] Calendar: 
17:33:03: [0:00:07.725] Calendar: CURLINFO_TEXT: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
17:33:03: [0:00:07.725] Calendar: CURLINFO_TEXT: Server certificate:
17:33:03: [0:00:07.725] Calendar: CURLINFO_TEXT: 	 subject: C=DE; ST=Baden-Wuerttemberg; L=Freiburg im Breisgau; O=amabeja; CN=<URLofKopano>; emailAddress=
17:33:03: [0:00:07.725] Calendar: CURLINFO_TEXT: 	 start date: 2019-06-10 12:36:39 GMT
17:33:03: [0:00:07.726] Calendar: CURLINFO_TEXT: 	 expire date: 2022-06-09 12:36:39 GMT
17:33:03: [0:00:07.726] Calendar: CURLINFO_TEXT: 	 issuer: C=DE; ST=Baden-Wuerttemberg; L=Freiburg im Breisgau; O=amabeja; CN=<URLofKopano>; emailAddress=
17:33:03: [0:00:07.726] Calendar: CURLINFO_TEXT: 	 SSL certificate verify result: self signed certificate (18), continuing anyway.
17:33:03: [0:00:07.726] Calendar: CURLINFO_TEXT: Server auth using Basic with user \'marco.hoffmann\'
17:33:03: [0:00:07.726] Calendar: CURLINFO_HEADER_OUT: PROPFIND /caldav/marco.hoffmann/ HTTP/1.1

Authorization:<REMOVED FROM LOG>
User-Agent: Rainlendar-CalDAVPlugin/1.0

Host: <URLofKopano>:8443

Accept: */*

Content-Type: application/xml; charset=\"utf-8\"

DEPTH:1

Content-Length: 261

Expect: 100-continue
17:33:04: [0:00:08.724] Calendar: CURLINFO_TEXT: Done waiting for 100-continue
17:33:04: [0:00:08.724] Calendar: CURLINFO_DATA_OUT: <?xml version=\"1.0\" encoding=\"utf-8\" ?>
<D:propfind xmlns:D=\"DAV:\" xmlns:C=\"urn:ietf:params:xml:ns:caldav\" xmlns:CS=\"/calendarserver.org/ns/\"><D:prop><D:displayname/><D:resourcetype/><C:supported-calendar-component-set/><CS:getctag/></D:prop></D:propfind>
17:33:04: [0:00:08.724] Calendar: CURLINFO_TEXT: We are completely uploaded and fine
17:33:04: [0:00:08.805] Calendar: CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status
17:33:04: [0:00:08.805] Calendar: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
17:33:04: [0:00:08.805] Calendar: CURLINFO_HEADER_IN: Content-Type: application/xml; charset=\"utf-8\"
17:33:04: [0:00:08.805] Calendar: CURLINFO_HEADER_IN: Content-Length: 593
17:33:04: [0:00:08.805] Calendar: CURLINFO_HEADER_IN: Server: Kopano
17:33:04: [0:00:08.805] Calendar: CURLINFO_HEADER_IN: Date: Wed, 16 Oct 2019 15:33:05 GMT
17:33:04: [0:00:08.806] Calendar: CURLINFO_HEADER_IN: Connection: close
17:33:04: [0:00:08.806] Calendar: CURLINFO_HEADER_IN:
17:33:04: [0:00:08.817] Calendar: CURLINFO_DATA_IN: <?xml version=\"1.0\" encoding=\"UTF-8\"?>
<C:multistatus xmlns:D=\"/calendarserver.org/ns/\" xmlns:E=\"urn:ietf:params:xml:ns:caldav\" xmlns:C=\"DAV:\">
 <C:response>
  <C:href>/caldav/marco.hoffmann/</C:href>
  <C:propstat>
   <C:prop>
    <C:displayname>Marco Hoffmann</C:displayname>
    <C:resourcetype>
     <C:collection/>
    </C:resourcetype>
    <E:supported-calendar-component-set>
     <E:comp name=\"VTIMEZONE\"/>
    </E:supported-calendar-component-set>
    <D:getctag>0</D:getctag>
   </C:prop>
   <C:status>HTTP/1.1 200 OK</C:status>
  </C:propstat>
 </C:response>
</C:multistatus>
17:33:04: [0:00:08.817] Calendar: CURLINFO_TEXT: Closing connection 0
17:33:04: [0:00:08.818] Calendar: CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):
17:33:04: [0:00:08.818] Calendar: 
17:33:04: [0:00:08.818] Calendar: Result: (0) 207 Multi-Status.
17:33:04: [0:00:08.819] DEBUG: Calendar: Marco Hoffmann was ignored since its resource type is not calendar
17:33:04: [0:00:08.819] WARNING: Calendar: Unable to find the calendars from the given url. Trying to get the events from the url instead.
17:33:04: [0:00:08.819] Calendar: Making request: /<URLofKopano>:8443/caldav/marco.hoffmann/Kalender
17:33:04: [0:00:08.820] Calendar: CURLINFO_TEXT: Hostname was NOT found in DNS cache
17:33:04: [0:00:08.825] Calendar: CURLINFO_TEXT:   Trying 89.X...
17:33:04: [0:00:08.829] Calendar: CURLINFO_TEXT: Connected to <URLofKopano> port 8443 (#0)
17:33:04: [0:00:08.830] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Client hello (1):
17:33:04: [0:00:08.830] Calendar: 
17:33:04: [0:00:08.883] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server hello (2):
17:33:04: [0:00:08.884] Calendar: 
17:33:04: [0:00:08.884] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, CERT (11):
17:33:04: [0:00:08.884] Calendar: 
17:33:04: [0:00:08.885] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server key exchange (12):
17:33:04: [0:00:08.885] Calendar: 
17:33:04: [0:00:08.886] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server finished (14):
17:33:04: [0:00:08.887] Calendar: 
17:33:04: [0:00:08.898] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Client key exchange (16):
17:33:04: [0:00:08.898] Calendar: 
17:33:04: [0:00:08.899] Calendar: CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):
17:33:04: [0:00:08.899] Calendar: 
17:33:04: [0:00:08.899] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):
17:33:04: [0:00:08.899] Calendar: 
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):
17:33:04: [0:00:08.907] Calendar: 
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):
17:33:04: [0:00:08.907] Calendar: 
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: Server certificate:
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: 	 subject: C=DE; ST=Baden-Wuerttemberg; L=Freiburg im Breisgau; O=amabeja; CN=<URLofKopano>; emailAddress=
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: 	 start date: 2019-06-10 12:36:39 GMT
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: 	 expire date: 2022-06-09 12:36:39 GMT
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: 	 issuer: C=DE; ST=Baden-Wuerttemberg; L=Freiburg im Breisgau; O=amabeja; CN=<URLofKopano>; emailAddress=
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: 	 SSL certificate verify result: self signed certificate (18), continuing anyway.
17:33:04: [0:00:08.907] Calendar: CURLINFO_TEXT: Server auth using Basic with user \'marco.hoffmann\'
17:33:04: [0:00:08.907] Calendar: CURLINFO_HEADER_OUT: PROPFIND /caldav/marco.hoffmann/Kalender HTTP/1.1

Authorization:<REMOVED FROM LOG>
User-Agent: Rainlendar-CalDAVPlugin/1.0

Host: <URLofKopano>:8443

Accept: */*

Content-Type: application/xml; charset=\"utf-8\"

DEPTH:1

Content-Length: 167

Expect: 100-continue
17:33:05: [0:00:09.906] Calendar: CURLINFO_TEXT: Done waiting for 100-continue
17:33:05: [0:00:09.906] Calendar: CURLINFO_DATA_OUT: <?xml version=\"1.0\" encoding=\"utf-8\" ?>
<D:propfind xmlns:D=\"DAV:\" xmlns:C=\"urn:ietf:params:xml:ns:caldav\"><D:prop><D:getetag/><C:calendar-data/></D:prop></D:propfind>
17:33:05: [0:00:09.906] Calendar: CURLINFO_TEXT: We are completely uploaded and fine
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: Content-Type: application/xml; charset=\"utf-8\"
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: Content-Length: 381
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: Server: Kopano
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: Date: Wed, 16 Oct 2019 15:33:06 GMT
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN: Connection: close
17:33:06: [0:00:09.994] Calendar: CURLINFO_HEADER_IN:
17:33:06: [0:00:10.006] Calendar: CURLINFO_DATA_IN: <?xml version=\"1.0\" encoding=\"UTF-8\"?>
<C:multistatus xmlns:D=\"urn:ietf:params:xml:ns:caldav\" xmlns:C=\"DAV:\">
 <C:response>
  <C:href>/caldav/marco.hoffmann/Kalender</C:href>
  <C:propstat>
   <C:prop>
    <C:getetag>1560500852</C:getetag>
    <D:calendar-data></D:calendar-data>
   </C:prop>
   <C:status>HTTP/1.1 200 OK</C:status>
  </C:propstat>
 </C:response>
</C:multistatus>
17:33:06: [0:00:10.006] Calendar: CURLINFO_TEXT: Closing connection 0
17:33:06: [0:00:10.007] Calendar: CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):
17:33:06: [0:00:10.007] Calendar: 
17:33:06: [0:00:10.007] Calendar: Result: (0) 207 Multi-Status.
17:33:06: [0:00:10.007] WARNING: Calendar: Found some events but the server didn\'t send any content for them. Let\'s try with calendar-multiget instead.
17:33:06: [0:00:10.007] Calendar: Making request: /<URLofKopano>:8443/caldav/marco.hoffmann/Kalender
17:33:06: [0:00:10.007] Calendar: CURLINFO_TEXT: Hostname was NOT found in DNS cache
17:33:06: [0:00:10.013] Calendar: CURLINFO_TEXT:   Trying 89.X.X.X
17:33:06: [0:00:10.016] Calendar: CURLINFO_TEXT: Connected to <URLofKopano> port 8443 (#0)
17:33:06: [0:00:10.017] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Client hello (1):
17:33:06: [0:00:10.017] Calendar: 
17:33:06: [0:00:10.071] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server hello (2):
17:33:06: [0:00:10.072] Calendar: 
17:33:06: [0:00:10.072] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, CERT (11):
17:33:06: [0:00:10.072] Calendar: 
17:33:06: [0:00:10.072] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server key exchange (12):
17:33:06: [0:00:10.072] Calendar: 
17:33:06: [0:00:10.073] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Server finished (14):
17:33:06: [0:00:10.073] Calendar: 
17:33:06: [0:00:10.081] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Client key exchange (16):
17:33:06: [0:00:10.081] Calendar: 
17:33:06: [0:00:10.081] Calendar: CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):
17:33:06: [0:00:10.081] Calendar: 
17:33:06: [0:00:10.081] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):
17:33:06: [0:00:10.081] Calendar: 
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):
17:33:06: [0:00:10.089] Calendar: 
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):
17:33:06: [0:00:10.089] Calendar: 
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: Server certificate:
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: 	 subject: C=DE; ST=Baden-Wuerttemberg; L=Freiburg im Breisgau; O=amabeja; CN=<URLofKopano>; emailAddress=
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: 	 start date: 2019-06-10 12:36:39 GMT
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: 	 expire date: 2022-06-09 12:36:39 GMT
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: 	 issuer: C=DE; ST=Baden-Wuerttemberg; L=Freiburg im Breisgau; O=amabeja; CN=<URLofKopano>; emailAddress=
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: 	 SSL certificate verify result: self signed certificate (18), continuing anyway.
17:33:06: [0:00:10.089] Calendar: CURLINFO_TEXT: Server auth using Basic with user \'marco.hoffmann\'
17:33:06: [0:00:10.090] Calendar: CURLINFO_HEADER_OUT: REPORT /caldav/marco.hoffmann/Kalender HTTP/1.1

Authorization:<REMOVED FROM LOG>
User-Agent: Rainlendar-CalDAVPlugin/1.0

Host: <URLofKopano>:8443

Accept: */*

Content-Type: application/xml; charset=\"utf-8\"

DEPTH:1

Content-Length: 233

Expect: 100-continue
17:33:07: [0:00:11.103] Calendar: CURLINFO_TEXT: Done waiting for 100-continue
17:33:07: [0:00:11.103] Calendar: CURLINFO_DATA_OUT: <?xml version=\"1.0\" encoding=\"utf-8\" ?>
<C:calendar-multiget xmlns:D=\"DAV:\" xmlns:C=\"urn:ietf:params:xml:ns:caldav\"><D:prop><D:getetag/><C:calendar-data/></D:prop><D:href>/caldav/marco.hoffmann/Kalender</D:href></C:calendar-multiget>
17:33:07: [0:00:11.103] Calendar: CURLINFO_TEXT: We are completely uploaded and fine
17:33:07: [0:00:11.207] Calendar: CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status
17:33:07: [0:00:11.207] Calendar: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
17:33:07: [0:00:11.207] Calendar: CURLINFO_HEADER_IN: Content-Type: application/xml; charset=\"utf-8\"
17:33:07: [0:00:11.207] Calendar: CURLINFO_HEADER_IN: Content-Length: 262
17:33:07: [0:00:11.207] Calendar: CURLINFO_HEADER_IN: Server: Kopano
17:33:07: [0:00:11.207] Calendar: CURLINFO_HEADER_IN: Date: Wed, 16 Oct 2019 15:33:07 GMT
17:33:07: [0:00:11.208] Calendar: CURLINFO_HEADER_IN: Connection: close
17:33:07: [0:00:11.208] Calendar: CURLINFO_HEADER_IN:
17:33:07: [0:00:11.221] Calendar: CURLINFO_DATA_IN: <?xml version=\"1.0\" encoding=\"UTF-8\"?>
<C:multistatus xmlns:D=\"urn:ietf:params:xml:ns:caldav\" xmlns:C=\"DAV:\">
 <C:response>
  <C:href>/caldav/marco.hoffmann/Kalender/Kale.ics</C:href>
  <C:status>HTTP/1.1 404 Not Found</C:status>
 </C:response>
</C:multistatus>
17:33:07: [0:00:11.221] Calendar: CURLINFO_TEXT: Closing connection 0
17:33:07: [0:00:11.221] Calendar: CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):
17:33:07: [0:00:11.221] Calendar: 
17:33:07: [0:00:11.222] Calendar: Result: (0) 207 Multi-Status.
17:33:07: [0:00:11.222] Calendar: Read 0 items from url \"/<URLofKopano>:8443/caldav/marco.hoffmann/Kalender\"

Whilst adding new events works fine within Rainlendar when the calendar is added via CalDAV. The appointment is shown in Kopano and the debug says:

[code]
17:44:35: [0:11:39.098] Calendar: CURLINFO_HEADER_OUT: PUT /caldav/marco.hoffmann/Kalender/2133727e-70fb-de4e-8a83-f198f7832f35.ics HTTP/1.1

Authorization:
User-Agent: Rainlendar-CalDAVPlugin/1.0

Host: :8443

Accept: /

Content-Type: text/calendar

If-None-Match: *

Content-Length: 323

Expect: 100-continue
17:44:36: [0:11:40.095] Calendar: CURLINFO_TEXT: Done waiting for 100-continue
17:44:36: [0:11:40.095] Calendar: CURLINFO_DATA_OUT: BEGIN:VCALENDAR

PRODID:-//Rainlendar/CalDAVPlugin V1.4//EN

VERSION:2.0

BEGIN:VEVENT

UID:2133727e-70fb-de4e-8a83-f198f7832f35

SUMMARY:neuer Termin

CLASS:PRIVATE

DTSTAMP:20191016T154433Z

LAST-MODIFIED:20191016T154433Z

DTSTART;VALUE=DATE:20191016

DTEND;VALUE=DATE:20191017

TRANSP:OPAQUE

END:VEVENT

END:VCALENDAR
17:44:36: [0:11:40.095] Calendar: CURLINFO_TEXT: We are completely uploaded and fine
17:44:36: [0:11:40.417] Calendar: CURLINFO_HEADER_IN: HTTP/1.1 201 Created
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN: DAV: 1, access-control, calendar-access, calendar-schedule, calendarserver-principal-property-search
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN: Etag: 1571240676
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN: Content-Length: 0
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN: Server: Kopano
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN: Date: Wed, 16 Oct 2019 15:44:36 GMT
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN: Connection: close
17:44:36: [0:11:40.418] Calendar: CURLINFO_HEADER_IN:
17:44:36: [0:11:40.418] Calendar: CURLINFO_TEXT: Closing connection 0
17:44:36: [0:11:40.418] Calendar: CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):
17:44:36: [0:11:40.418] Calendar:
17:44:36: [0:11:40.419] DEBUG: AddComponent: “neuer Term”
17:44:36: [0:11:40.419] AddComponent: Start: Date: 16-10-2019 | Time: -1:-1:-1 | DST: No | UTC: No | Zone: null
17:44:36: [0:11:40.419] AddComponent: End: Date: 17-10-2019 | Time: -1:-1:-1 | DST: No | UTC: No | Zone: null
17:44:36: [0:11:40.419] Calendar: Result: (0) 201 Created.
17:44:36: [0:11:40.419] CalDAV Calendar-Calendar-Offline: Writing offline file “C:\Users\Marco\.rainlendar2\backups\CalDAV Calendar-Calendar-Offline.ics”
17:44:37: [0:11:41.045] DEBUG: Merging component 2133727e-70fb-de4e-8a83-f198f7832f35 “neuer Term”[/code]

I don’t get the problem. Reading and writing appointments with the Android caldav-synchronizer ‘DAVx^5’ works fine. Sync is no problem in both ways.

The certificate does not cause the problem - and it is valid by the way. But the log clearly shows, that the certificate is accepted.

The calendar is also downloadable directly via the URL via browser however it takes about 50s to get ready for download.

Please help. I have a pro-subscription and I’d really would like to be able to alter and ad appointments within Rainlendar too.

Kind regards,

Marco

Rainlendar tries to get the events from the server two different ways but is unsuccessful since the server doesn’t support either methods. I would need to get access to the server to be able to try myself and see how to get the events from it.

If you contact me via PM or via my registered email I could create a new Zarafa/Kopano account on my server and send you the credentials you need to login on the web interface and to synchronize via caldav too.

Is that ok?

Kind regards,

M. Hoffmann

That would be great. Sent you an email.