summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2012-05-18 13:16:19 (GMT)
committerJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2012-05-18 13:16:19 (GMT)
commit86f1b21a8b47234f8fe2a6e0218f6883f18e64ee (patch)
treee5d69bf82987f11c0aa47020d4f7e3dd00063aa1
parent9206c36422a127d800c5dd2f15384bc934bc773c (diff)
downloadkolab-docs-86f1b21a8b47234f8fe2a6e0218f6883f18e64ee.tar.gz
Provide Release Notes for Kolab 2.4.1
-rw-r--r--Release_Notes/en-US/Release_Notes.ent2
-rw-r--r--Release_Notes/en-US/Release_Notes.xml270
2 files changed, 248 insertions, 24 deletions
diff --git a/Release_Notes/en-US/Release_Notes.ent b/Release_Notes/en-US/Release_Notes.ent
index 056136c..8e2996d 100644
--- a/Release_Notes/en-US/Release_Notes.ent
+++ b/Release_Notes/en-US/Release_Notes.ent
@@ -1,5 +1,5 @@
<!ENTITY PRODUCT "Kolab Groupware">
-<!ENTITY PRODUCT_VERSION "2.4">
+<!ENTITY PRODUCT_VERSION "2.4.1">
<!ENTITY BOOKID "Release_Notes">
<!ENTITY YEAR "2011">
<!ENTITY HOLDER "Kolab Systems AG">
diff --git a/Release_Notes/en-US/Release_Notes.xml b/Release_Notes/en-US/Release_Notes.xml
index 2c0762a..b969ad4 100644
--- a/Release_Notes/en-US/Release_Notes.xml
+++ b/Release_Notes/en-US/Release_Notes.xml
@@ -8,12 +8,243 @@
<section id="sect-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION">
<title>Changes to Kolab &PRODUCT_VERSION;</title>
<para>
- The following changes are included with the Kolab &PRODUCT_VERSION; series:
+ The following changes are included in Kolab &PRODUCT_VERSION;:
</para>
- <formalpara id="form-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Native_Packages">
+ <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 &PRODUCT_VERSION;, native packages are provided for the following distributions;
+ As of Kolab 2.4, native packages are provided for the following distributions;
</para>
</formalpara>
@@ -21,19 +252,13 @@
<itemizedlist>
<listitem>
<para>
- Debian Lenny, see also <xref linkend="appe-Release_Notes-Version_Matrix_Debian_Lenny" />.
+ 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>
- Debian Squeeze, see also <xref linkend="appe-Release_Notes-Version_Matrix_Debian_Squeeze" />.
- </para>
-
- </listitem>
- <listitem>
- <para>
- Enterprise Linux 5, including the following distributions;
+ Enterprise Linux 6, including the following distributions;
</para>
<para>
<itemizedlist>
@@ -60,7 +285,7 @@
</para>
<para>
- For more information on packages included, see also <xref linkend="appe-Release_Notes-Version_Matrix_Enterprise_Linux_5" />.
+ For more information on packages included, see also <xref linkend="appe-Release_Notes-Version_Matrix_Enterprise_Linux_6" />.
</para>
</listitem>
@@ -68,25 +293,25 @@
</itemizedlist>
</para>
- <formalpara id="form-Release_Notes-Changes_to_Kolab_PRODUCT_VERSION-Mobile_Device_Synchronization_through_Z_Push_ActiveSync">
+ <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 &PRODUCT_VERSION;, Kolab now fully supports synchronizing Notes, Tasks, Appointments and Contacts from and to mobile devices using ActiveSync, through the Z-Push application.
+ 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_PRODUCT_VERSION">
- <title>Included in Kolab &PRODUCT_VERSION;</title>
+ <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_PRODUCT_VERSION-Horde_3.3.11">
+ <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 &PRODUCT_VERSION;, including all functionality associated with it; Calendaring, Contacts, Notes, Tasks and Free/Busy exchange capabilities.
+ 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>
@@ -99,16 +324,15 @@
</section>
- <section id="sect-Release_Notes-Upgrading_from_Kolab_2.2">
- <title>Upgrading from Kolab 2.2</title>
+ <section id="sect-Release_Notes-Upgrading_from_Kolab_2.3">
+ <title>Upgrading from Kolab 2.3</title>
<para>
- Please refer to the Appendix of our Administrator Guide for instructions on upgrading Kolab from product series 2.2 to product series 2.3.
+
</para>
</section>
- <xi:include href="Version_Matrix_Debian_Lenny.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Version_Matrix_Debian_Squeeze.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Version_Matrix_Enterprise_Linux_5.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>