<h1>Zarafa 7.1.13-51032 Update Notes</h1>

<p>
See the <a href="http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt" target="_blank">Zarafa 7.1 Changelog</a> for more details about issues fixed in Zarafa.
</p>

<h1>Zarafa 7.1.12-49411 Update Notes</h1>

<h2>Changes</h2>

<ul>
<li>A bug in the dagent concerning umlauts has been fixed.</li>
<li>A bug in the installation/deinstallation process of the php-mapi package has been fixed.</li>
</ul>

<h1>Zarafa 7.1.12 Update Notes</h1>

<h2>Important Changes</h2>

<ul>
<li><b>The update may take a very long time, even in smaller environments</b>.</li>
<li>Because user accounts are modified during the update, the server load will increase during the update and while replicating the changes to all servers in your environment</li>
<li>Zarafa contacts are now managed by a dedicated UDM/UMC Module. Zarafa contacts thus no longer count towards the user count in the UCS domain. See below for information about migrating existing contacts</li>
<li>Zarafa shared stores and non-active users are now now managed by a dedicated UDM/UMC Module. Zarafa shared stores and non-active users thus no longer count towards the user count in the UCS domain. See below for information about migrating existing shared stores and non-active users</li>
</ul>

<h2>Migrating existing contacts, shared stores and non-active users</h2>
<p>
The migration of existing objects will be done automatically during the update by the zarafa4ucs joinscript.
To prevent the migration during joinscript execution, set the UCR variable <code>zarafa/migrateusers</code> to <code>false</code> before installing the update.
If an error is detected the joinscript will fail before any modifications are done.
Check the logfile <code>/var/log/univention/management-console-module-appcenter.log</code> or call the migration script in dry-run mode (<code>/usr/share/zarafa4ucs/zarafa4ucs-migrate-to-separate-udm-modules -d</code>) to learn more about encountered errors.
</p>

<h2>Other notable changes</h2>
<ul>
<li>Zarafa contacts and shared stores/non-active users are now managed in separate UDM/UMC modules: udm zarafa/contact and udm zarafa/non-active</li>
<li>Starting from this App version, Zarafa Webapp Version 2 is installed</li>
<li>Following the Zarafa namingscheme, shared stores are now called non-active users.</li>
<li>Zarafa contacts and shared stores/non-active users will no longer count towards the UCS license</li>
<li>If no e-mail address is configured when a user has his role changed to any zarafa role, a warning will be shown</li>
<li>The package univention-sasl will now be installed when installing Zarafa</li>
<li>The Zarafa ldap schema has been updated</li>
<li>ClamAV is explicitly restarted after installing or updating Zarafa</li>
<li>Zarafa is now installable on a UCS member server</li>
<li>The Zarafa server restart procedure during the installation has been improved</li>
</ul>

<p>
See the <a href="http://download.zarafa.com/community/final/7.1/final-changelog-7.1.txt" target="_blank">Zarafa 7.1 Changelog</a> for more details about issues fixed in Zarafa.
</p>
