1.1 --- a/README.txt Sun Oct 25 23:41:59 2015 +0100
1.2 +++ b/README.txt Mon Oct 26 13:31:55 2015 +0100
1.3 @@ -89,6 +89,10 @@
1.4 If already installed, the /etc/imip-agent/config.sh script should be edited
1.5 instead.
1.6
1.7 +With local SMTP delivery, the mail system will need to be configured to route
1.8 +messages for local recipients. See the description of mail configuration for
1.9 +more information.
1.10 +
1.11 Configuring Other Software
1.12 ==========================
1.13
1.14 @@ -103,7 +107,7 @@
1.15 Either Exim or Postfix can be chosen as a mail system supporting the agent.
1.16
1.17 Configuring Mail Systems for the Agent
1.18 ---------------------------------------
1.19 +======================================
1.20
1.21 The essential aspect of mail system configuration involves mail transports and
1.22 the integration of agent programs into the mail processing pipeline. Thus, the
1.23 @@ -127,20 +131,28 @@
1.24
1.25 If local SMTP delivery is being used, the 30_exim4-config_people file (in
1.26 conf/exim) or the master.cf.items file (in conf/postfix) will need adjusting.
1.27 -Where LMTP_SOCKET is employed, a suitable filesystem path is required; where
1.28 -the lmtp system group is employed, it may be replaced with a different group.
1.29 -See below for a discussion of LMTP and mail delivery.
1.30 +
1.31 +If LMTP is being used, instances of LMTP_SOCKET in the example configuration
1.32 +files will need to be replaced with a suitable filesystem path. Where the lmtp
1.33 +system group is employed, it may be replaced with a different group. See
1.34 +below for a discussion of LMTP and mail delivery.
1.35
1.36 Configuring Mail Systems for Mail Recipients
1.37 ---------------------------------------------
1.38 +============================================
1.39
1.40 The software should operate independently of the way mail recipients are
1.41 identified in any given mail system, and thus does not dictate things such as
1.42 routing or account querying. However, example configuration files are provided
1.43 -that demonstrate the use of LDAP to identify mail recipients:
1.44 +that demonstrate the use of various techniques to identify mail recipients.
1.45
1.46 +Naturally, these recipient identification configuration examples can be
1.47 +disregarded in favour of other ways of defining mail recipients, subject to
1.48 +the needs of any given environment.
1.49
1.50 -For Exim with LDAP (in conf/exim/ldap)...
1.51 +Using LDAP with Exim
1.52 +--------------------
1.53 +
1.54 +For Exim (in conf/exim/ldap)...
1.55
1.56 010_exim4-config_ldap_people_outgoing Defines recipients and outgoing
1.57 mail routing
1.58 @@ -148,8 +160,10 @@
1.59 020_exim4-config_ldap_resources ...
1.60 020_exim4-config_ldap_people_outgoing_recipients
1.61
1.62 +Using LDAP with Postfix
1.63 +-----------------------
1.64
1.65 -For Postfix with LDAP (in conf/postfix/ldap)...
1.66 +For Postfix (in conf/postfix/ldap)...
1.67
1.68 main.cf.example Defines recipients and outgoing
1.69 mail routing (for inclusion in
1.70 @@ -159,6 +173,8 @@
1.71 virtual_alias_maps_people_outgoing.cf mail routing
1.72 virtual_alias_maps_resources.cf ...
1.73
1.74 +Using Lists of Identities
1.75 +-------------------------
1.76
1.77 Since the use of LDAP can be somewhat challenging and also excessive in some
1.78 situations, examples of maintaining recipient information using a simpler
1.79 @@ -168,8 +184,10 @@
1.80 virtual identity files, but this permits a very transparent way of
1.81 administering the system.
1.82
1.83 +Using Lists with Exim
1.84 +---------------------
1.85
1.86 -For Exim without LDAP (in conf/exim/simple)...
1.87 +For Exim (in conf/exim/simple)...
1.88
1.89 010_exim4-config_people_outgoing Defines recipients and outgoing
1.90 mail routing
1.91 @@ -193,8 +211,10 @@
1.92
1.93 aliases.example Routes calendar to root
1.94
1.95 +Using Lists with Postfix
1.96 +------------------------
1.97
1.98 -For Postfix without LDAP (in conf/postfix/simple)...
1.99 +For Postfix (in conf/postfix/simple)...
1.100
1.101 main.cf.example Defines recipients and outgoing
1.102 mail routing (for inclusion in
1.103 @@ -208,11 +228,6 @@
1.104
1.105 virtual_alias_maps_local Defines recipients and local users
1.106
1.107 -
1.108 -Naturally, the above recipient identification configuration examples can be
1.109 -disregarded in favour of other ways of defining mail recipients, subject to
1.110 -the needs of any given environment.
1.111 -
1.112 LDAP Representations for Mail Recipients
1.113 ----------------------------------------
1.114
1.115 @@ -244,7 +259,7 @@
1.116 mailRecipient object class is employed by resources in Kolab.
1.117
1.118 Configuring Mail Systems for Mail Delivery
1.119 -------------------------------------------
1.120 +==========================================
1.121
1.122 The agent software assumes that delivery of mail to recipients may be
1.123 performed either using local SMTP or by using LMTP to a suitable mailbox
1.124 @@ -282,7 +297,7 @@
1.125 cyrus lmtp 750 /var/run/cyrus/socket
1.126
1.127 Configuring Cron for Free/Busy Updates
1.128 ---------------------------------------
1.129 +======================================
1.130
1.131 The periods occupied by recurring events are not expanded beyond a certain
1.132 window of time by imip-agent. As a consequence, free/busy collections need to
1.133 @@ -299,7 +314,7 @@
1.134 crontab entry of the appropriate format is required instead.
1.135
1.136 Configuring Web Servers for Free/Busy Publishing
1.137 -------------------------------------------------
1.138 +================================================
1.139
1.140 Each user may request the publishing of their free/busy information by
1.141 configuring certain settings. The conf/apache/imip-agent.conf file provides a
1.142 @@ -315,7 +330,7 @@
1.143 network-specific access constraints.
1.144
1.145 Configuring Web Servers for the Calendar Management Interface
1.146 --------------------------------------------------------------
1.147 +=============================================================
1.148
1.149 A calendar management interface is provided to allow users to view and
1.150 interact with their calendars through the Web. The