1 = Administering imip-agent = 2 3 With imip-agent deployed, usage of the software should occur automatically. 4 However, evidence of its operation will only emerge when calendar-related 5 messages are exchanged between e-mail users. This will cause a few different 6 things to happen: 7 8 * Summary messages may be sent by the calendar system to mail recipients 9 10 * Replies to calendar-related messages may be received by the senders of 11 those messages 12 13 * Free/busy information will become available, either in responses to 14 requests sent over e-mail, or [[../FreeBusyPublishing|over the Web]] 15 16 In the background, imip-agent uses and updates information as described in the 17 [[../FilesystemUsage|filesystem usage guide]]. 18 19 == Creating User Data Stores == 20 21 The [[../MailIntegration|mail system]] mechanisms are responsible for 22 determining whether a valid recipient has been specified in any given message, 23 and imip-agent does not attempt to validate such information again. Therefore, 24 when a message is received for a calendar user for whom no data store has been 25 initialised in the [[../FilesystemUsage|filesystem]], the software will 26 automatically create one. 27 28 Consequently, users for whom such data stores have been created will experience 29 the software using the default configuration, described in the 30 [[../Preferences|preferences guide]]. It is for this reason that the default 31 values in the [[../Configuration|configuration]] should be adjusted according 32 to the policies decided for the deployment of this software. 33 34 However, it is possible to create data stores for users in advance using the 35 `tools/init_user.sh` script as in the following example: 36 37 {{{ 38 tools/init_user.sh mailto:vincent.vole@example.com 39 }}} 40 41 Here, the user identity is given as a URI since this is how iCalendar references 42 participants in scheduling operations. The result of the above command should be 43 some new directories in the [[../FilesystemUsage|filesystem area]] dedicated to 44 calendar information storage. 45 46 === Initialising Resources === 47 48 Resources belong to a class of user whose preferences should be configured in 49 advance because their policies may differ on a case-by-case basis. For example, 50 some resources may benefit from employing the `permitted_times` setting so that 51 a granularity on event times may be imposed, meaning that such resources would 52 be "handed over" at regular intervals. 53 54 The `freebusy_offers` setting, together with the `scheduling_function` setting, 55 would allow different kinds of resources to "keep open" tentatively-suggested 56 periods for different lengths of time, allowing frequently-requested resources 57 to respond to scheduling requests in a timely fashion, whilst also allowing 58 other resources to give more time to event organisers to respond to their 59 counter-proposals. 60 61 === Adjusting Preferences === 62 63 Once initialised, the user preferences can be adjusted by adding files to the 64 `preferences` directory created by the above command. For example, if a user has 65 elected to not participate in the calendar system, a file called `participating` 66 can be added as follows: 67 68 {{{ 69 echo 'no' > '/var/lib/imip-agent/preferences/mailto:vincent.vole@example.com/participating' 70 }}} 71 72 Here, the default storage location has been given in the filename. 73 74 Normally, users should visit the [[../CalendarManager|management interface]] to 75 change their preferences, but modifications done by administrators are more 76 efficiently performed by directly interacting with the filesystem. For example, 77 an administrator might initialise the common names of users by scripting changes 78 to the `CN` file for each user, obtaining such names from some kind of database. 79 80 == Excluding Users Entirely == 81 82 Since the [[../AgentPrograms|agent programs]] are installed as part of the mail 83 handling workflow, even the configuration of non-participation in the calendar 84 system for users will still result in those users' messages being passed along 85 the workflow by imip-agent, which may result in a decrease in general mail 86 delivery performance. 87 88 To exclude users entirely, the routing configuration of the 89 [[../MailIntegration|MTA]] needs to be changed so that such users identities are 90 not recognised as calendar system participants, thus preventing their messages 91 from being routed via imip-agent. This is as simple as either not listing the 92 identity in [[../MailIntegration/Simple|lists of addresses]] or by adjusting 93 [[../MailIntegration/LDAP|queries yielding calendar users]].