paul@933 | 1 | = Outgoing Messages = |
paul@933 | 2 | |
paul@934 | 3 | When messages are sent by a mail client, imip-agent employs an outgoing |
paul@934 | 4 | message rule in the MTA to provide a handler to inspect any calendar-related |
paul@934 | 5 | content and to update its records. |
paul@933 | 6 | |
paul@934 | 7 | The management interface does not use this outgoing message rule because it |
paul@934 | 8 | sends messages from the general calendar address (for example, |
paul@934 | 9 | `calendar@example.com`), and there is no trivial way of deducing the identity |
paul@934 | 10 | of the real sender. Instead, the manager explicitly sends suitably-modified |
paul@934 | 11 | messages to the address of the user operating the interface to achieve the |
paul@934 | 12 | same effect as the outgoing message rule, as well as to notify any mail |
paul@934 | 13 | clients that would normally be managing calendar events on behalf of the user. |
paul@933 | 14 | |
paul@933 | 15 | == Events == |
paul@933 | 16 | |
paul@933 | 17 | {{{#!table |
paul@934 | 18 | '''Method''' || '''Effect on Objects''' || '''Effect on Free/Busy''' |
paul@934 | 19 | || '''Effect on Request Queue''' |
paul@933 | 20 | == |
paul@934 | 21 | `CANCEL` |
paul@934 | 22 | || Remove selected attendees or an entire event |
paul@934 | 23 | || Remove record if entire event is cancelled |
paul@934 | 24 | ||<rowspan="4"> Remove any queue entry |
paul@933 | 25 | == |
paul@934 | 26 | `PUBLISH` |
paul@934 | 27 | ||<rowspan="2"> Add or update object, removing specific recurrences of |
paul@934 | 28 | .. recurring events |
paul@934 | 29 | ||<rowspan="2"> Add record for the event, removing records for specific |
paul@934 | 30 | .. recurrences of an event |
paul@933 | 31 | == |
paul@933 | 32 | `REQUEST` |
paul@933 | 33 | == |
paul@934 | 34 | `REPLY` |
paul@934 | 35 | || Merge attendee participation information |
paul@934 | 36 | || Update records for the event, preserving specific recurrence records when |
paul@934 | 37 | .. changing a recurring event |
paul@933 | 38 | }}} |
paul@933 | 39 | |
paul@934 | 40 | The effect of the outgoing handler is to ensure that the user's free/busy |
paul@934 | 41 | status reflects the consequences of their stated attendance of events, and for |
paul@934 | 42 | the object records to reflect the most recent state of each event. |
paul@933 | 43 | |
paul@933 | 44 | == Other Object Types == |
paul@933 | 45 | |
paul@934 | 46 | Other object types are not handled. Free/busy information, if exchanged, is |
paul@934 | 47 | not obtained by the handler to replace its own records. |