[Tickets #10277] Re: ActiveSync Calendar and Tasks not working

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10277
------------------------------------------------------------------------------
  Ticket             | 10277
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync Calendar and Tasks not working
  Queue              | Horde Base
  Version            | 4.0.6
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2011-06-26 23:15) wrote:

> The Touchdown Client has a auto-detect feature at setup-time.  
> (Activesync Only, exchange 2003 and exchange 2007). Probably this is  
> the cause of the PING before SYNC issue.

No. Version detection for AS is done via the http headers. This is  
caused by the client getting back what is essentially garbage from the  
server when it issues the SETTINGS request. I've cleaned up the code a  
bit to make it fail a little bit cleaner, but it still fails. I'm  
working with NitroDesk, trying a number of different builds they are  
providing trying to help them narrow down the problem.


> Another possibility is: i did not check whether the other Android  
> Client (native) was still active when provisioning the Touchdown  
> client.

It was, but I can tell which request came from which client in the logs.


> The good thing (but even bad for me): i could reproduce the timezone  
> issue in Bug 10194.
> When i commented out the line in kronolith/lib/Event.php

Yes, I am having a similar issue now as well - but *only* when using  
TouchDown - not the native android app. Since this code contains  
*nothing* obtained directly from the client, I'm led to believe that  
something else earlier in the request is corrupting something in PHP  
to cause this issue.