summaryrefslogtreecommitdiff
path: root/Release_Notes/en-US/Release_Notes.xml
blob: 759724da882a4e744ad63efd5b6522ad0d47ce0f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Release_Notes.ent">
%BOOK_ENTITIES;
]>
<article>
    <xi:include href="Article_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
    <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION">
        <title>Changes to Kolab &PRODUCT_VERSION;</title>
        <para>
            The following changes are included in Kolab &PRODUCT_VERSION;:
        </para>
        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_782_Setup_creates_wrong_virtual_alias_maps">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=782">Issue #782: Setup creates wrong virtual_alias_maps</ulink></title>
            <para>
                The Kolab Groupware setup process, <command>setup-kolab</command> set up Postfix's virtual_alias_maps lookup table configuration wrongly.
            </para>
            <para>
                System administrators that have setup Kolab before &PRODUCT_VERSION; may have noticed messages to alias recipient email addresses were not being delivered.
            </para>
            <formalpara id="form-Release_Notes-Issue_782_Setup_creates_wrong_virtual_alias_maps-Solution">
                <title>Solution</title>
                <para>
                    Replace the setting named <literal>search_filter</literal> to <literal>query_filter</literal> in <filename>/etc/postfix/ldap/virtual_alias_maps.cf</filename>.
                </para>

            </formalpara>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_772_The_MTA_daemons_are_not_configured_to_start_on_boot">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=772">Issue #772: The MTA daemons are not configured to start on boot</ulink></title>
            <para>
                Some daemons, including <application>Postfix</application>, <application>ClamAV</application> and <application>Amavis</application> were not being configured to start on boot by <command>setup-kolab</command>.
            </para>
            <formalpara id="form-Release_Notes-Issue_772_The_MTA_daemons_are_not_configured_to_start_on_boot-Solution">
                <title>Solution</title>
                <para>
                    Execute the following commands to configure the daemons to start on boot.
                </para>

            </formalpara>
            <para>

<screen># <userinput>chkconfig postfix on</userinput>
# <userinput>chkconfig clamd.amavisd on</userinput>
# <userinput>chkconfig amavisd on</userinput></screen>

            </para>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_770_No_login_to_Roundcube_possible_after_fresh_installation">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=770">Issue #770: No login to Roundcube possible after fresh installation</ulink></title>
            <para>
                An issue had been introduced, discovered and resolved with setting the DES encryption key for Roundcube.
            </para>
            <para>
                System administrators that have set up Kolab Groupware in between the time this issue was introduced and resolved may experience this issue.
            </para>
            <formalpara id="form-Release_Notes-Issue_770_No_login_to_Roundcube_possible_after_fresh_installation-Solution">
                <title>Solution</title>
                <para>
                    Set <literal>$rcmail_config['des_key']</literal> in <filename>/etc/roundcubemail/main.inc.php</filename> to a string of exactly 24 characters long.
                </para>

            </formalpara>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_761_Postfix_local_recipient_maps_filter_always_finds_group_as_recipient">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=761">Issue #761: Postfix local_recipient_maps filter always finds group as recipient</ulink></title>
            <para>
                During Kolab setup, a faulty filter has been written out to <filename>/etc/postfix/ldap/local_recipient_maps.cf</filename>.
            </para>
            <para>
                System administrators may have noticed mail to recipients that did not exist being bounced at delivery rather then denied at transmission.
            </para>
            <formalpara id="form-Release_Notes-Issue_761_Postfix_local_recipient_maps_filter_always_finds_group_as_recipient-Solution">
                <title>Solution</title>
                <para>
                    Update the <literal>query_filter</literal> setting in <filename>/etc/postfix/ldap/local_recipient_maps.cf</filename> to match the following (remove the line breaks and indentation whitespace), and restart the <application>postfix</application> service;
                </para>

            </formalpara>
            <para>

<screen>query_filter = (&amp;
    (|(mail=%s)(alias=%s))(|(objectclass=kolabinetorgperson)
    (|(objectclass=kolabgroupofuniquenames)(objectclass=kolabgroupofurls)))
)</screen>

            </para>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Login_to_web_administration_not_possible_over_SSL">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=757">Login to web administration not possible over SSL</ulink></title>
            <para>
                In a default setup, had SSL been used to connect to the Kolab Web Administration Panel, and a self-signed or otherwise invalid certificate been used, the Kolab Web Administration Panel would deny login.
            </para>
            <para>
                The underlying cause is that connections to the API of the web administration panel were 1) composed from the Request URI, and thus used HTTPS to connect to the API, and 2) were not configured to allow certificates that could not be validated.
            </para>
            <formalpara id="form-Release_Notes-Login_to_web_administration_not_possible_over_SSL-Solution">
                <title>Solution</title>
                <para>
                    Two additional settings to <filename>/etc/kolab/kolab.conf</filename> have been introduced that should be set unless certificates used can be validated. Please add these settings to <filename>/etc/kolab/kolab.conf</filename> if you are experiencing this issue.
                </para>

            </formalpara>
            <para>

<screen>[kolab_wap]
ssl_verify_peer = false
ssl_verify_host = false</screen>

            </para>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_754_Postfix_only_listens_on_the_loopback_interfaces">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=754">Issue #754: Postfix only listens on the loopback interface(s)</ulink></title>
            <para>
                The setup for Kolab Groupware did not take into account the default configuration file for Postfix makes the service listen on the loopback interface(s) only.
            </para>
            <formalpara id="form-Release_Notes-Issue_754_Postfix_only_listens_on_the_loopback_interfaces-Solution">
                <title>Solution</title>
                <para>
                    Replace or add the setting <literal>inet_interfaces</literal> in <filename>/etc/postfix/main.cf</filename> and restart the <application>postfix</application> service.
                </para>

            </formalpara>
            <para>
                Examples for valid values for the <literal>inet_interfaces</literal> setting are included in the configuration file.
            </para>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_749_No_email_addresses_for_Kolab_users">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=749">Issue #749: No email addresses for Kolab users</ulink></title>
            <para>
                Due to a missing configuration section rename in the Kolab Groupware setup process, no default recipient policy was being made available.
            </para>
            <para>
                System administrators and users alike may have experienced mailboxes for Kolab users were not being created, with symptoms ranging from failure to login to the Roundcube webmail client, to "No such mailbox" type errors.
            </para>
            <formalpara id="form-Release_Notes-Issue_749_No_email_addresses_for_Kolab_users-Solution">
                <title>Solution</title>
                <para>
                    The default configuration file contains a section named <literal>example.org</literal>. Rename this section to your local, primary domain name space.
                </para>

            </formalpara>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_725_Kolab_daemon_not_configured_to_start_on_boot">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=725">Issue #725: Kolab daemon not configured to start on boot</ulink></title>
            <para>
                The Kolab daemon may not have been configured to start on boot by the setup process.
            </para>
            <formalpara id="form-Release_Notes-Issue_725_Kolab_daemon_not_configured_to_start_on_boot-Solution">
                <title>Solution</title>
                <para>
                    Manually configure the <application>kolabd</application> service to start on boot:
                </para>

            </formalpara>
            <para>

<screen># <userinput>chkconfig kolabd on</userinput></screen>

            </para>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_722_Incorrect_ACI_controls_on_cnkolabcnconfig">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=722">Issue #722: Incorrect ACI controls on cn=kolab,cn=config</ulink></title>
            <para>
                Incorrect ACI controls may have been set on LDAP DN <literal>cn=kolab,cn=config</literal>. To detect whether the correct ACI controls have been set, please use the following command:
            </para>
            <para>

<screen># <userinput>ldapsearch -x -h localhost -b "cn=kolab,cn=config" \</userinput>
    <userinput>-D "&lt;kolab-service account dn&gt;" \</userinput>
    <userinput>-w "&lt;kolab-service account password&gt;"</userinput></screen>

            </para>
            <formalpara id="form-Release_Notes-Issue_722_Incorrect_ACI_controls_on_cnkolabcnconfig-Solution">
                <title>Solution</title>
                <para>
                    To set the correct ACI controls, give the kolab-service account read, search and compare access to <literal>cn=kolab,cn=config</literal>.
                </para>

            </formalpara>

        </section>

        <section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Issue_719_No_table_horde_cache">
            <title><ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=719">Issue #719: No table 'horde_cache</ulink></title>
            <para>
                The setup process may not have created a table named <literal>horde_cache</literal> in the roundcube database.
            </para>
            <para>
                System administrators and users alike may have noticed significant performance decrease or even disfunctional address books and/or calendars in the Roundcube webmail interface.
            </para>
            <para>
                To verify the table was created, issue the following command:
            </para>
            <para>

<screen># <userinput>mysql -u root -p roundcube -e 'show tables;'</userinput>
Password:
</screen>

            </para>
            <para>
                The list of tables should include <literal>horde_cache</literal>.
            </para>
            <formalpara id="form-Release_Notes-Issue_719_No_table_horde_cache-Solution">
                <title>Solution</title>
                <para>
                    Create the <literal>horde_cache</literal> manually, with help of the file shipped as documentation to the <literal>roundcubemail-plugins-kolab</literal> package.
                </para>

            </formalpara>
            <para>

<screen># <userinput>rpm -qld roundcubemail-plugins-kolab</userinput>
# <userinput>mysql -u root -p roundcube &lt; /path/to/horde_cache.sql</userinput></screen>

            </para>

        </section>


    </section>

    <section id="sect-Release_Notes-Changes_to_Kolab_2.4">
        <title>Changes to Kolab 2.4</title>
        <para>
            The following changes are included with the Kolab 2.4 series:
        </para>
        <formalpara id="form-Release_Notes-Changes_to_Kolab_2.4-Native_Packages">
            <title>Native Packages</title>
            <para>
                As of Kolab 2.4, native packages are provided for the following distributions;
            </para>

        </formalpara>
        <para>
            <itemizedlist>
                <listitem>
                    <para>
                        Debian Squeeze, Wheezy and Sid packages are being worked on, see also <ulink url="https://bugzilla.kolabsys.com/show_bug.cgi?id=728" />.
                    </para>

                </listitem>
                <listitem>
                    <para>
                        Enterprise Linux 6, including the following distributions;
                    </para>
                    <para>
                        <itemizedlist>
                            <listitem>
                                <para>
                                    CentOS
                                </para>

                            </listitem>
                            <listitem>
                                <para>
                                    Red Hat Enterprise Linux
                                </para>

                            </listitem>
                            <listitem>
                                <para>
                                    Scientific Linux
                                </para>

                            </listitem>

                        </itemizedlist>

                    </para>
                    <para>
                        For more information on packages included, see also <xref linkend="appe-Release_Notes-Version_Matrix_Enterprise_Linux_6" />.
                    </para>

                </listitem>

            </itemizedlist>

        </para>
        <formalpara id="form-Release_Notes-Changes_to_Kolab_2.4-Mobile_Device_Synchronization_through_Z_Push_ActiveSync">
            <title>Mobile Device Synchronization through Z-Push ActiveSync</title>
            <para>
                As of version 2.4, Kolab now fully supports synchronizing Notes, Tasks, Appointments and Contacts from and to mobile devices using ActiveSync, through the Z-Push application.
            </para>

        </formalpara>

    </section>

    <section id="sect-Release_Notes-Included_in_Kolab_2.4">
        <title>Included in Kolab 2.4</title>
        <para>
            <itemizedlist>
                <listitem>
                    <formalpara id="form-Release_Notes-Included_in_Kolab_2.4-Horde_3.3.11">
                        <title>Horde 3.3.11</title>
                        <para>
                            Horde Webmail 3.3.11 is included with Kolab 2.4, including all functionality associated with it; Calendaring, Contacts, Notes, Tasks and Free/Busy exchange capabilities.
                        </para>

                    </formalpara>

                </listitem>

            </itemizedlist>

        </para>

    </section>

    <section id="sect-Release_Notes-Upgrading_from_Kolab_2.3">
        <title>Upgrading from Kolab 2.3</title>
        <para>

        </para>

    </section>

    <xi:include href="Version_Matrix_Debian_Squeeze.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
    <xi:include href="Version_Matrix_Enterprise_Linux_6.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</article>