[Tickets #11754] ActiveSync won't push new emails to mobile device

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/11754
------------------------------------------------------------------------------
  Ticket           | 11754
  Erstellt Von     | jmozdzen at nde.ag
  Zusammenfassung  | ActiveSync won't push new emails to mobile device
  Warteschlange    | Synchronization
  Version          | Git master
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


jmozdzen at nde.ag (2012-11-25 18:16) hat geschrieben:

I'm running a WebOS Pre3 against Horde5, ActiveSync. I've tried  
various settings and scenarios now, but always get to a point where  
the Pre3 will not receive new emails.

My test workflow:
- delete account from mobile device
- delete ActiveSync device in Horde
- reboot mobile device
- add account to mobile device (and select "email" only, to avoid  
mixed polls in the logs)
   * I see all current email on the device, no errors detected
- let it run for some time
- send new email to my email address
   * new emails show up in Horde5 web interface, but not on mobile device

I've tried with protocol 2.5 and 12.1, to the same effect. As I'm  
running ActiveSync with "custom logging", I have a device-specific log  
file to analyze.

Something that caught my eye in that log file - I have various "ERR:"  
entries, usually a pointer to trouble:

2012-11-25T14:22:39+00:00 ERR: Unmatched content:
2012-11-25T14:22:39+00:00 ERR: Array

2012-11-25T14:22:44+00:00 ERR: Changes detected in sync_cache during  
wait interval, exiting without updating cache.

2012-11-25T14:43:26+00:00 ERR: Incrementing counter, we saw this  
synckey before.

2012-11-25T14:53:39+00:00 ERR: [5199] State gone, PING terminating and  
forcing a SYNC:

2012-11-25T15:08:28+00:00 ERR: [5323] PING terminating: Empty synckey  
for INBOX

Most of these appear several times, but not necessarily in a specific pattern.

Since I started my latest test run, I have not been struck by "Base  
lambda function for closure not found in" bail-outs, which I earlier  
suspected as the root cause of these problems.

Can anyone shed some light on this and please give me a helping hand  
with debugging this issue?