Tickets :: Comment on [#13739] iTips not decoded properly in EAS.

* Your Email Address
* Spam protection	Enter the letters below: .__ __. __ ._.\ / \| \(__ / ` \| >< \|__/.__)\__._\|_/ \
Comment	> 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
Attachment
Watch this ticket