3 Replies Latest reply: May 8, 2013 4:15 AM by pairof9s
cbsmarketing Level 1 (0 points)

I am able to receive an Outlook appointment request on my iPhone. It appears as an attachment called something like "mime-attachment.ics". When I click this, details of the event pop up and I am able to add it to my calendar. Works like a charm. The problem I'm having now is, if the appointment is updated in Outlook and updates are then sent to attendees, I receive the email with an attachment again BUT instead of the details being updated, it appears exactly the same as the original event (same date, same time) instead of showing the new event information.


Does anyone know a way around this that does not involve syncing... iTunes... none of that nonsense...??!

iPhone 5
  • pairof9s Level 2 (190 points)

    So you yourself do not have an Outlook account, correct?


    If you do, it would seem the simple way to handle this would be to set up your iPhone w/ your Exchange account, even if you only want the Calendar function (not email or contacts). That way, the appointments go directly to your Calendar for accepting/denying and any updates happen directly there as well. At least, that's how it works on my iPhone & iPad (iOS 6).


    Here is an article on this:


  • cbsmarketing Level 1 (0 points)

    I don't have an Exchange account. We are in the process of changing it, as we currently have pop...


    I just don't understand why Outlook and my iPad are not communicating. The initial appointment comes through fine but any adjustments get lost in translation?!? Odd.

  • pairof9s Level 2 (190 points)

    It seems the recurring theme on these types of problems is the use of a POP email account. Something originates in corrupting or blunting the full affect of an ics event from Outlook through this method.


    I guess just thinking about it, this makes some sense in that Microsoft has probably not fully developed their ActiveSync to work properly with POP accounts, especially w/in Mac OS (if you use that). It's understandable that their motivation is towards Exchange interoperability and even further, the need to support an "old" technology like POP.


    Sorry I couldn't be more help, but perhaps you'll just have to continue to work around this until your migration to Exchange is complete.