[Tickets #13739] Invitation emails from Office 365 not decoded properly.

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13739
------------------------------------------------------------------------------
  Ticket             | 13739
  Created By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Invitation emails from Office 365 not decoded properly.
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-12-05 14:56) wrote:

 From SImon:

I have 3 accounts in Nine. One is a normal Microsoft Exchange account,  
one is a full native Office 365 account, one is a Horde account.

On the Office 365 system I receive internal invites fine. These work  
in Nine as expected. Same with native Exchange system invites.

On the Horde system I received a meeting invite from someone who is on  
Office 365. This arrived as a base64 encoded email and synced to Nine  
as an email with an unreadable attachment, no indication that it is a  
meeting at all.

The same invite displays in native Horde Webmail as an invitation.

If I forward the invite to my native Exchange account it then syncs to  
my device in that account with an ics file, which I assume is the  
decoded base64 attachment that was not decoded in the sync from Horde.

So what I think is happening is that the invite is sent to me as a  
base64 encoded ics because I'm not on his Office365 system. Horde  
syncing with Nine does not decode this, so I have no way of doing  
anything with it.

Not sure if it's a Horde sync issue or a Nine issue. The fact that  
sending it through  native Exchange decodes it to Nine Ok as an ics  
(even though Nine can't handle the ics..... yet)  leads me to think  
this may be a Horde sync issue.

I have cced Mike Rubinsky at Horde.

Thanks
Simon