Den 01. nov. 2011 13:43, skrev Patrick Ohly:
On Tue, 2011-11-01 at 07:35 +0100, Ove Kåven wrote:
> It did not seem to quite work for me. The backend now stores EXDATEs
> that look like
> I suppose I'll need to take a look at why that happens later on.
Remember to set loglevel=4 in both sync and target config, to get full
logging on both sides.
There's some bug that causes it to bork if the EXDATE has a property
(like TZID). The calendar-backend doesn't check the property anyway; it
can go to UTC if the time itself has a "Z" suffix, but no other timezone
overrides seem possible for this field.
Would you know of another of those magic rules that would remove that