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

* Your Email Address
* Spam protection	Enter the letters below: .. .. ..__..__ \|\|\/\|\ /[__][__) \__\|\| \| \/ \| \|\|
Comment	> Thanks for your very fast answer. > Yes i am current in analyse and try to find at which procedure the > newid will not returned. > In my mind, i think the IMAP-Backend Server is the problem. > I use DBMail 3.1.8 current. I think the UIDPLUS Feature is needed for > ActiveSync for this. The Horde IMP comes out without this. This > feature is after my researches implemented, possible disabled or not > in the List of the Features of the Server and the Client does not use > then this. > > My ActiveSync Client is a iOS Device and in the ActiveSync-Debug the > Response XML returns no MSGID and the Status 1 (Invalid Srouce). > The Server Moves the Message correctly but my Deivce means it's not > moved, but the message is removed from the current folder on device > and is to finde in the new folder. The Working is absolut correct but > the Status will not right returned. If i have new information after > my analyses, i will report this. > > > >> 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. >
Attachment
Watch this ticket

Saved Queries