[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-13 14:33) hat geschrieben:

>> 1) What version Horde_ActiveSync are you using?
>> 2) What ActiveSync client is this?
>>
>> The best way for me to see what's going on is a wireshark dump of the
>> conversation, but if i can get access to the same client you are
>> using I can try to reproduce without one.
>
> Nevermind. Your client is broken. It is sending an empty "COMMANDS" element:
>
> [25543][2018-11-13T09:23:11+01:00] I:    <Commands />
>
> This is a violation of the EAS specification:
>
> MS-ASCMD Section 2.2.3.22 COMMANDS:
>
> [...]
>
> This element is optional. If it is present, it MUST include at least  
> one operation. It is a child of the Collection element.
>

Thanks for the info. Got the sync working again for this user:

- disabled sync on the client
- reset status on the server
- enabled sync for contacts and calendar
- enabled sync for E-Mail

Maybe this approach changed the client status in a way that the empty  
"command" was not sent again.



-- 
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.