Comment # 3 on bug 944768 from Michal Bruncko

hi again.
seems I finally found working configuration. My assumption with IPv6 is
probably correct, but this wasn���t enough to have CalDAV calendars and tasklists
working. I have to:
- completely delete both existing CalDAV Calendar and CalDAV Tasklist from
Evolution
- and completely recreate each CalDAV source with using IPv4 address used
instead of DNS name. 

Now I have working configuration which lives even after restarting Evolution
client and I can successfully read and update both Calendar events and Tasks. 

also I can see "sync" icon (two arrows) near CalDAV Calendar to confirm that
calendar is in sync. 

in summary this is bug for me. Evolution should recognize that IPv6 cant be
used (due whatever limitation) and IPv4 has to be used instead (as an failover
option).