[Tickets #13825] Remi PHP update to 5.5.21-1 results in constant resyncing

[noreply at bugs.horde.org]

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

Ticket-URL: https://bugs.horde.org/ticket/13825
------------------------------------------------------------------------------
  Ticket           | 13825
  Erstellt Von     | christian at hailer.eu
  Zusammenfassung  | Remi PHP update to 5.5.21-1 results in constant resyncing
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


christian at hailer.eu (2015-01-23 13:28) hat geschrieben:

Hello,

I'm not quite sure it's a bug, but I'll describe what happened today  
after updating the Remi PHP packages from version 5.5.20-2 to 5.5.21-1  
(http://php.net/ChangeLog-5.php#5.5.21 and  
http://blog.famillecollet.com/post/2015/01/23/PHP-version-5.4.37-5.5.21-and-5.6.5).

Server: CentOS 6.6 i686

Among others, the php-imap package was updated this morning. Several  
friends contacted me some hours later to tell me their ActiveSync  
devices are syncing constantly, emptying the folders and resyncing  
again. It affected all device types, Outlook 2013, Android and iPhone.
I had a look at the Horde ActiveSync device logs and saw a lot of  
errors like this these:

2015-01-23T13:45:21+01:00 ERR: IMAP error reported by server.
2015-01-23T13:45:21+01:00 ERR: IMAP error reported by server.
2015-01-23T13:45:36+01:00 ERR: IMAP error reported by server.
2015-01-23T13:45:36+01:00 ERR: IMAP error reported by server.
2015-01-23T13:45:36+01:00 ERR: IMAP error reported by server.
2015-01-23T13:45:36+01:00 ERR: IMAP error reported by server.
2015-01-23T13:45:36+01:00 ERR: IMAP error reported by server.

So I had a look at dovecot which I use as the IMAP backend. No  
problems/errors in the logs.

Then I realized I updated PHP and that the php-imap package was among  
the updates. I downgraded all PHP packages to the old version and  
everything works like a charm now.

The reason why I'm filing this bug is: I think Horde should handle the  
above error message and tell the ActiveSync client to try again later.  
I suspect that Horde reported back to the client that no message at  
all is left in the folder it tried to sync when the error occurs, and  
with the next ping it is able to connect again and resyncs all the  
messages.

Could that be the reason for the above behaviour?

Best regards, Christian