From 862a848043d3c78dbd84f125e3cc362f19429287 Mon Sep 17 00:00:00 2001 From: Klaus Leithoff Date: Tue, 15 Dec 2015 13:39:10 +0000 Subject: [PATCH] ActiveSync/Mail/MeetingRequests: HandlingMeetingRequests on MobileDevice has serious issues within our/zpush2 implementation. thus we overwrite the globalobjId from calendar object, as: if you delete the mail, that is the meeting-request its using the globalobjid as reference and deletes both: mail AND meeting. we dont want this. since accepting meeting requests with the mobile does nothing we see no further drawbacks with that. TODO: Look into MeetingRequestHandling --- mail/inc/class.mail_zpush.inc.php | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mail/inc/class.mail_zpush.inc.php b/mail/inc/class.mail_zpush.inc.php index 75734d6034..ec35d9ac52 100644 --- a/mail/inc/class.mail_zpush.inc.php +++ b/mail/inc/class.mail_zpush.inc.php @@ -1062,6 +1062,10 @@ class mail_zpush implements activesync_plugin_write, activesync_plugin_sendmail, ($attachment = $this->mail->getAttachment($id, $attach['partID'],0,false,false,$_folderName)) && ($output->meetingrequest = calendar_zpush::meetingRequest($attachment['attachment']))) { + //overwrite the globalobjId from calendar object, as: if you delete the mail, that is + //the meeting-request its using the globalobjid as reference and deletes both: + //mail AND meeting. we dont want this. accepting meeting requests with the mobile does nothing + $output->meetingrequest->globalobjid = activesync_backend::uid2globalObjId($id); $output->messageclass = "IPM.Schedule.Meeting.Request"; unset($attachment); continue; // do NOT add attachment as attachment