paul@102 | 1 | imip-agent
|
paul@102 | 2 | ==========
|
paul@102 | 3 |
|
paul@102 | 4 | This software implements an agent that can interpret e-mail messages
|
paul@102 | 5 | containing calendar information, maintain availability records for scheduling
|
paul@102 | 6 | participants, act on behalf of resources and other entities that need to
|
paul@102 | 7 | participate in scheduling, and support user interfaces for end-users whose
|
paul@102 | 8 | e-mail programs do not understand calendar data.
|
paul@102 | 9 |
|
paul@102 | 10 | Getting Started
|
paul@102 | 11 | ===============
|
paul@102 | 12 |
|
paul@102 | 13 | Eventually, this information should be incorporated into packages for various
|
paul@955 | 14 | operating system distributions, and the accompanying instructions should be
|
paul@955 | 15 | largely superfluous for most users.
|
paul@731 | 16 |
|
paul@955 | 17 | See: docs/wiki/GettingStarted
|
paul@891 | 18 |
|
paul@143 | 19 | Configuring Mail Systems for Mail Recipients
|
paul@932 | 20 | ============================================
|
paul@143 | 21 |
|
paul@143 | 22 | The software should operate independently of the way mail recipients are
|
paul@143 | 23 | identified in any given mail system, and thus does not dictate things such as
|
paul@143 | 24 | routing or account querying. However, example configuration files are provided
|
paul@932 | 25 | that demonstrate the use of various techniques to identify mail recipients.
|
paul@143 | 26 |
|
paul@932 | 27 | Naturally, these recipient identification configuration examples can be
|
paul@932 | 28 | disregarded in favour of other ways of defining mail recipients, subject to
|
paul@932 | 29 | the needs of any given environment.
|
paul@900 | 30 |
|
paul@955 | 31 | See: docs/wiki/MailIntegration
|
paul@955 | 32 | See: docs/wiki/MailIntegration--LDAP
|
paul@955 | 33 | See: docs/wiki/MailIntegration--Simple
|
paul@144 | 34 |
|
paul@143 | 35 | Configuring Mail Systems for Mail Delivery
|
paul@932 | 36 | ==========================================
|
paul@143 | 37 |
|
paul@143 | 38 | The agent software assumes that delivery of mail to recipients may be
|
paul@900 | 39 | performed either using local SMTP or by using LMTP to a suitable mailbox
|
paul@900 | 40 | provider.
|
paul@900 | 41 |
|
paul@955 | 42 | See: docs/wiki/MailIntegration
|
paul@955 | 43 | See: docs/wiki/MailIntegration--LMTP
|
paul@955 | 44 | See: docs/wiki/MailIntegration--LocalSMTP
|
paul@670 | 45 |
|
paul@748 | 46 | Configuring Web Servers for Free/Busy Publishing
|
paul@932 | 47 | ================================================
|
paul@748 | 48 |
|
paul@748 | 49 | Each user may request the publishing of their free/busy information by
|
paul@748 | 50 | configuring certain settings. The conf/apache/imip-agent.conf file provides a
|
paul@748 | 51 | configuration file for deployment with the Apache Web server software that
|
paul@748 | 52 | exposes a directory for Web publishing containing the published free/busy
|
paul@748 | 53 | information.
|
paul@748 | 54 |
|
paul@748 | 55 | Access to free/busy information may not be moderated, but Web server
|
paul@748 | 56 | directives can be introduced to impose access controls. Mail programs that
|
paul@748 | 57 | wish to consult the free/busy information may have problems in dealing with
|
paul@748 | 58 | authentication mechanisms, however, and it may be regarded as acceptable in
|
paul@748 | 59 | certain environments to expose such information publicly or with
|
paul@748 | 60 | network-specific access constraints.
|
paul@748 | 61 |
|
paul@748 | 62 | Configuring Web Servers for the Calendar Management Interface
|
paul@932 | 63 | =============================================================
|
paul@748 | 64 |
|
paul@748 | 65 | A calendar management interface is provided to allow users to view and
|
paul@748 | 66 | interact with their calendars through the Web. The
|
paul@748 | 67 | conf/apache/imip-manager.conf file provides a configuration file for
|
paul@748 | 68 | deployment with the Apache Web server software that enables this interface.
|
paul@748 | 69 |
|
paul@905 | 70 | The management interface is deployed as a CGI program, meaning that a suitable
|
paul@905 | 71 | module must be enabled in the Apache configuration. On Debian, this is done as
|
paul@905 | 72 | follows:
|
paul@905 | 73 |
|
paul@905 | 74 | a2enmod cgi
|
paul@905 | 75 |
|
paul@748 | 76 | Since such access to calendars should only be performed by identified
|
paul@905 | 77 | users, access controls are suggested in the configuration file. Modules
|
paul@905 | 78 | providing additional authentication support may need to be enabled. For
|
paul@905 | 79 | example, on Debian, the LDAP authentication/authorisation support is enabled
|
paul@905 | 80 | as follows:
|
paul@905 | 81 |
|
paul@905 | 82 | a2enmod authnz_ldap
|