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

[email protected]
Newsgroups gmane.comp.horde.bugs
Message-ID <[email protected]>
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14874
------------------------------------------------------------------------------
  Ticket           | 14874
  Aktualisiert Von | [email protected]
  Zusammenfassung  | ActiveSync Protocol Error when syncing E-Mails
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Not A Bug
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


[email protected] (2018-11-14 17:50) hat geschrieben:

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.

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.



-- 
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.