(In reply to Patrick Ohly from comment #7)
> (In reply to Sébastien Villemot from comment #6)
> > Looking at the log, it still looks that the spurious traffic comes from
> > timezone information that is repeated for every VEVENT entry.
> 
> That's worth discussing with Radicale devs. I don't know how they currently
> decide which VTIMEZONEs need to be inserted into the individual items. If
> they include *all* of them, then it's not surprising that there is
> significant overhead once a calendar contains several different time zone
> definitions.

My understanding is indeed that *all* VTIMEZONEs are inserted into all
individual items in the REPORT response.

So in the end I am not sure that the issue under discussion is actually a
problem in SyncEvolution. I leave it up to you to decide if you want to
implement a workaround for what now looks to me as a bug in Radicale.

Thanks for your feedback on this issue, it is much appreciated.