[Tickets #13874] Re: ActiveSync Returns Incorecct Status to Device during MoveItems

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13874
------------------------------------------------------------------------------
  Ticket             | 13874
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync Returns Incorecct Status to Device during
                     | MoveItems
  Queue              | Horde Framework Packages
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-02-20 15:08) wrote:

Cannot reproduce.

The logic in the code you pasted is correct. If a new UID is not  
returned for a moved message, something went wrong with moving the  
message (or an issue with the driver code, but, as I said, I can't  
reproduce this). WIthout a UID we can't report success back to the  
device, since it needs to know the new UID.

You need to find out why the old_uid -> new_uid mapping is not being  
returned in your case. The call stack looks something like this:

Horde_ActiveSync_Request_MoveItems calls  
Horde_ActiveSync_Connector_Importer::importMessageMove(), which calls  
Horde_Core_ActiveSync_Driver::moveMessage(), which calls  
Horde_ActiveSync_Imap_Adapter::moveMessage()

  I would start by looking in  
Horde_ActiveSync_Imap_Adapter::moveMessage() and see what the imap  
client is returning from the copy command. ($imap->copy).

If that is correct, next you should check the importer's  
importMessageMove method to be sure the data is handled correctly there.

What client is this? A sync log might also be helpful to weed out any  
obvious errors.