[horde] ActiveSync/IMP error with latest GIT

[Michael M Slusarz]

Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting Joerg Pulz <Joerg.Pulz at frm2.tum.de>:
>
>> On Wed, 26 Feb 2014, Joerg Pulz wrote:
>>>
>>> Now, when the client attempts to sync messages i get the following errors:
>>>
>>> 2014-02-26T10:31:54+01:00 INFO: [16619]
>>> Horde_Core_ActiveSync_Driver::getMessage(INBOX, 407672)
>>> 2014-02-26T10:31:54+01:00 ERR: [16619] Message gone or error  
>>> reading message
>>> from server: Not Found
>>> 2014-02-26T10:31:54+01:00 INFO: [16619] Updating state during change
>>> 2014-02-26T10:31:54+01:00 INFO: [16619]
>>> Horde_Core_ActiveSync_Driver::getMessage(INBOX, 407673)
>>> 2014-02-26T10:31:54+01:00 ERR: [16619] Message gone or error  
>>> reading message
>>> from server: Not Found
>>> 2014-02-26T10:31:54+01:00 INFO: [16619] Updating state during change
>>> 2014-02-26T10:31:54+01:00 INFO: [16619]
>>> Horde_Core_ActiveSync_Driver::getMessage(INBOX, 407674)
>>> 2014-02-26T10:31:54+01:00 ERR: [16619] Message gone or error  
>>> reading message
>>> from server: Not Found
>>> 2014-02-26T10:31:54+01:00 INFO: [16619] Updating state during change
>>> ..... and so on
>>
>> Just found this which seems to be related to the error above:
>> WARN: HORDE PHP ERROR: Invalid argument supplied for foreach() [pid  
>> 16103 on line 2582 of "/.../horde/libs/Horde/Imap/Client/Socket.php"]
>>
>> Looks like as this gets logged for every message that should be synced by
>> ActiveSync but results in the "Message gone error" instead.
>>
>> Maybe that helps to fix this issue.
>
> I believe there was a fix for that issue just committed to Git  
> within the last few days. Not sure if it hit the stable release in  
> Horde_Imap_Client yet though.

Don't think this has anything to do with any recent fixes in  
Horde_Imap_Client.  There was a recent patch to fix BODYPARTSIZE  
behavior, but this doesn't appear to be related.

michael
-- 

___________________________________
Michael Slusarz [slusarz at horde.org]