The Calendar Server then consumes the invitation from the iSchedule URL just as it would have done if an external calendar server had posted an invitation to one of its users. Posting the invitation request to a calendar iSchedule URL Injecting the corresponding iTIP message into the regular calendar server workflowĪdding meta-data (email X- headers) to the iMIP email before delivering it to its recipients Intercepting incoming emails containing an iMIP message An iMIP message has an iCalendar attachment of type 'text/calendar' with a method= option in the 'Content-Type:' header.
Message Server iMIP Configuration OverviewĪ Messaging Server MTA channel (an "iSchedule" channel) handles automatic processing of external calendar invites by: Finally, because of the addition of meta data to the email message, the Convergence (web-based) client is able to display a scheduling-specific form to users that enables them to accept, decline, or indicate a "maybe" to meeting invitations directly from their email without having to switch to the calendar client. As the response is sent directly by Calendar Server, it does not matter how the user accepted the invitation (whether from a calendar client on a mobile device, desktop, or from an email client).
That status change also enables Calendar Server to send a response to the organizer indicating the disposition of the meeting request.
Thus, based upon the user accepting or rejecting the request, the calendar client merely has to update the attendee status in the invitation. Because the invitation is already in the user's calendar, invitation replies and cancel are also merged automatically. That is, CalDAV clients now receive iMIP messages in their scheduling-inbox, and are able to process them just like regular CalDAV-based invitations and replies. Users can either accept the "external" meeting invite directly from their calendar client (either desktop or mobile iOS CalDAV clients) or they can still accept it from their email client.
Once you have configured your deployment accordingly, users have a choice on how to process invitations.
As a consequence, external event invitations automatically appear in the user's calendar without the need for a manual intervention, even when using a "non-calendar" aware client. You configure the Messaging Server MTA to process the calendar invite email (which is an iMIP message), extract the pertinent calendar information, then use the iSchedule protocol to add the invite to the attendee's calendar database. This capability involves an intermediary in the form of Messaging Server. To users, handling an external invite then appears just like an internal invite. You can configure your Calendar Server deployment to automatically process invitations coming from external calendar systems. Automatically Accepting External Invitations