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

noreply at bugs.horde.org noreply at bugs.horde.org
Mon Jan 26 07:28:50 UTC 2015


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
  Aktualisiert 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           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
+Neue Anlage      | horde_imp_debug.log
------------------------------------------------------------------------------


christian at hailer.eu (2015-01-26 07:28) hat geschrieben:

OK, I updated PHP this morning and had a look at the IMAP debug log.  
Here are 2 examples:

C: 31 UID SEARCH RETURN (ALL COUNT) HEADER MESSAGE-ID  
<00d701d01f08$6f76a3f0$4e63ebd0$@amusing.de> UID 0:215
S: 31 BAD Error in IMAP command UID SEARCH: Invalid UID messageset
>> Command 31 took 0,0008 seconds.

and

C: 31 STATUS "INBOX.!  Astrid""" (MESSAGES UIDNEXT UIDVALIDITY HIGHESTMODSEQ)
S: 31 BAD Error in IMAP command STATUS: Invalid arguments.
>> Command 31 took 0.0012 seconds.

The second error only occurs for folders containing whitespaces.

Afterwards the IMAP errors show in the ActiveSync log:

2015-01-26T07:21:28+01:00 INFO: [936] Initializing state for  
collection: INBOX.!  Astrid, synckey:  
{54854e18-3c50-4b6c-9de1-2bfd51a9e6c4}455
...
2015-01-26T07:21:28+01:00 WARN: [936] FOLDERSYNC required, collection gone.
...
2015-01-26T07:21:28+01:00 INFO: [936] Initializing state for  
collection: INBOX.Pound, synckey:  
{54854e18-04b4-49b8-95c0-2bfd51a9e6c4}207
...
2015-01-26T07:21:28+01:00 ERR: IMAP error reported by server.
...

The first error seems to occur only for messages with a UID starting  
with "0:", because this search worked:

C: 18 UID SEARCH RETURN (ALL COUNT) HEADER MESSAGE-ID  
<urn.rtn.msg.2015012317455385c863f6a3a546d380bc665834c256d9 at 1422035154979.rte-svc-eu-1abig-i-18852b52.eu-west-1.amazon.com> UID  
6515:6680
S: * ESEARCH (TAG "18") UID COUNT 0
S: 18 OK Search completed (0.000 secs).
>> Command 18 took 0.0043 seconds.

I attached the log.

Regards, Christian



christian at hailer.eu (2015-01-26 07:28) hat hochgeladen: horde_imp_debug.log

https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=horde_imp_debug.log&ticket=13825&fn=%2Fhorde_imp_debug.log





More information about the bugs mailing list