[horde] problem ActiveSync Android Event with end date

[Steffen]

On Fri, 31 Jan 2014, Michael J Rubinsky wrote:

> Quoting Steffen <skhorde at smail.inf.fh-bonn-rhein-sieg.de>:
>
>> On Fri, 10 Jan 2014, Steffen wrote:

>> 12:03 one event repeated each 4th week end on 28th March
>
> ^^^ This event is NEVER sent to the server, at least not in the log you 
> posted.

OK, thanks for checking the logs.

>> Most interessting is that the time stamp gets 1 hour back ??? From 12:04
>> to 11:04. It's another PID. During that phase, no Calendar entries in
>> the log. I also had log entries another time with a line:
>> Skipping @Calendar@ because it is not PINGable.
>> 
>> Then there is a jump in the hour again with the same PID at the time
>> I remove the repeated event:
>> 2014-01-30T11:08:01+00:00 DEBUG: [1671] I       </Data>
>> 2014-01-30T11:08:01+00:00 INFO: [1671]
>> Horde_Core_ActiveSync_Driver::changeMessage(@Calendar@,  ...)
>> 2014-01-30T12:08:01+01:00 INFO: [1671] Updating state during change
>> 2014-01-30T12:08:01+01:00 DEBUG: [1671] I      </Add>
>> 
>> And with the "12" hour logs, the "Calendar" stuff appears again.
>> 
>> The log is attached
>
> I have no idea what is going on. Your synclog also seems to indicate your 
> client is issuing multiple, identical requests. Given the fact that the event 
> in question is not even sent to the server from the client, this seems like a 
> client bug.

Hmm, I will try this with other setups.

Do you have an idea, why the log time stamp warps one hour back into the 
past and back into current again? Is Horde switching to UTC maybe? The 1 
hour is the difference of the local server time to UTC.

Is it possible that the time difference break the acceptance of some 
request / response? I mean, several SYNC implementations add sanity 
checking that a SYNC message is in a defined time frame. Maybe Horde tags 
responses with a timestamp, which is one hour too old?

-- 
Steffen