[Tickets #14874] Re: ActiveSync Protocol Error when syncing E-Mails

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14874
------------------------------------------------------------------------------
  Ticket             | 14874
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync Protocol Error when syncing E-Mails
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2018-11-16 15:09) wrote:

> Thanks for the link to the protocol specs. I had a look around but I  
> cannot match the log with the spec. The log contains XML elements  
> like "Commands" that are described in the spec (see chap. 2.2.3.32)  
> but the description of this elements implies a specific parent  
> element (Collection) that is not shown in the log as XML but as  
> "COLLECTIONS" (see 1st post). I assume this is a logging thing.

Correct. The "Folders" element represents the "COLLECTIONS" and the  
"Folder" element is a single "COLLECTION".

> According to the spec the Commands tag is optional to the Collection  
> but must contain something if present, otherwise "the server may  
> return a protocol status error". In this case the tag is present but  
> empty and a violation of the protocol like you said.
>
> The option is not to return a protocol status error. I agree that  
> this will probably not help if the client insists but I would like  
> to try and change this. It will probably take a few days until the  
> error occurs again. Until then I will try to prepare a patched  
> version.

Sorry, but we will not ignore this error. It's an outright protocol  
error. Ignoring this may lead to other unknown errors since the  
presence of the COMMANDS tag leads to certain assumptions about what  
has to happen next, server side.

The vendor needs to follow the specifications of the protocol they are  
implementing.