1 = Incoming Messages = 2 3 When messages are received by the MTA for a recipient, imip-agent employs message rules in the MTA to provide handlers to inspect any calendar-related content and to update its records. Different handlers are provided to process incoming messages depending on the nature of the eventual recipient: 4 5 People:: Handled by the person handler 6 Resources:: Handled by the resource handler 7 8 The different processing is described below. 9 10 == Events == 11 12 For people, the operation of the person handler is as follows: 13 14 {{{#!table 15 <rowspan="2"> '''Method''' || 16 <rowspan="2"> '''Effect on Objects''' || 17 <colspan="2"> '''Effect on Free/Busy''' || 18 <rowspan="2"> '''Effect on Request Queue''' 19 == 20 ''for recipient's own record'' || ''for recipient's record of others'' 21 == 22 `CANCEL` || 23 Set the state of the cancelled event, retaining it for future reference || 24 Remove record if the event is cancelled for the attendee (even if the event is not completely cancelled) || 25 <rowspan="3"> Update the recipient's free/busy record for the organiser || 26 Remove any queue entry 27 == 28 `PUBLISH` || 29 <rowspan="2"> Add or update object, removing specific recurrences of recurring events || 30 <rowspan="3"> || 31 No modification to the queue 32 == 33 `REQUEST` || 34 Add a queue entry for the event 35 == 36 `REPLY` || 37 Merge attendee participation information || 38 Update the recipient's free/busy record for each of the attendees || 39 No modification to the queue 40 }}} 41 42 The effect of the person handler is to ensure that the user's record of the free/busy status for ''other participants'' reflects the consequences of those participants' stated attendance of events, and for the object records to reflect the most recent state of each event. 43 44 Note that the free/busy information for a recipient of an event is not generally changed when receiving a message. Such information is only definitively changed by recipients themselves when responding to incoming messages, and the [[../OutgoingMessages|outgoing messages]] processing is concerned with updating that information as such responses are sent. 45 46 For resources, the operation of the resource handler is as follows: 47 48 {{{#!table 49 <rowspan="2"> '''Method''' || 50 <rowspan="2"> '''Effect on Objects''' || 51 <colspan="2"> '''Effect on Free/Busy''' || 52 <rowspan="2"> '''Effect on Request Queue''' 53 == 54 ''for recipient's own record'' || ''for recipient's record of others'' 55 == 56 `CANCEL` || 57 Set the state of the cancelled event, retaining it for future reference || 58 Remove record if the event is cancelled for the attendee (even if the event is not completely cancelled) || 59 <rowspan="4"> No records of other participants are employed by the resource handler || 60 <rowspan="4"> No queue is employed by the resource handler 61 == 62 `PUBLISH` || 63 <colspan="2"> Ignored by the resource handler 64 == 65 `REQUEST` || 66 Add or update object, removing specific recurrences of recurring events || 67 Attempt to schedule the event, creating or updating records for the recipient 68 == 69 `REPLY` || 70 <colspan="2"> Ignored by the resource handler 71 }}} 72 73 == Other Object Types == 74 75 Other object types are not handled.