On Sun, 2016-05-22 at 22:36 +0200, Tino Mettler wrote:
On Sat, May 21, 2016 at 12:40:24 +0200, Marc Bantle wrote:
> [INFO @owncloud] CalDAV peer rejected updated because
> item is outside the sync interval
> It looks like only recent and future events
> (last 3 month) get synced properly and all
> others are being rejected.
> Does anyone know, where that message comes from
> and which component is imposing the restriction?
> How can I change it?
As Owncloud is the peer from the Syncevolution view, it looks very much
like a restriction on the Owncloud side.
Owncloud seems to have a "time range filter" fetature that sounds
related. Maybe the default is 90 days.
It's indeed not something in upstream SyncEvolution. However, the
message looks like something produced by SyncEvolution.
Is that SyncEvolution coming from Ubuntu? Renato at some point worked on
range filtering, perhaps the message comes from that code (see also
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.