Major changes
- grommunio: Production availability of Debian 11 via repository
- grommunio: Availability of grommunio mobile apps via the App Store and Playstore
- grommunio: Support for stretched cluster installations
- grommunio: Preliminary support for OpenID Connect via Keycloak
- grommunio Web: Major upgrade including over 230 fixes, updated WYSIWYG editor, design and performance improvements
- grommunio Groupware: Enhanced Out-of-Office autoresponder implementation
- grommunio Groupware: Enhanced support for OP_MOVE rules processing
- grommunio Groupware: Enhanced vCard processing
- grommunio Groupware: Full multilingual mailbox support for 91 languages
- grommunio Groupware: Full support for mailbox owner mode
- grommunio Groupware: Full support for shared mailboxes
- grommunio Groupware: Import into public stores
- grommunio Groupware: Support for public folder access via EAS (Exchange ActiveSync)
- grommunio Groupware: Synchronization resiliency for offline mode with broken objects (named properties)
- grommunio Admin: Enhanced Active Directory Alias Support (Exchange compatible)
- grommunio Admin: Inline help for better understanding and easier administration
- grommunio Admin: Integration of remote wipe for Administrators via Admin UI/CLI
- grommunio Admin: License manager integration within Admin UI
- grommunio Admin: Reorganization of Admin UI for better usability
- grommunio Chat: Major upgrade to 6.1.1 with many fixes, style adoptions and seamless upgrade procedure
- grommunio Setup: Support for special characters under special circumstances with grommunio Meet and grommunio Files
The Documentation covers the necessary steps for the update procedure.
Post-update tasks
If you are using the grommunio appliance, some packages may require customization, depending on your configuration:
The list of known files that may require customization is due to configuration file extensions:
/etc/grommunio-antispam/local.d/redis.conf.rpm*/etc/grommunio-web/config.php.rpm*/etc/grommunio-chat/config.json.rpm*/etc/prosody/prosody.cfg.lua.rpm*
If the configuration file has been replaced by a package update, the minimal procedure is to copy the original configuration file back into place. It is recommended to create a backup beforehand and restart the corresponding service either via Admin UI/CLI or System Console/ssh:
.. code-block: bash
cp /etc/prosody/prosody.cfg.lua /etc/prosody/prosody.cfg.lua.rpmnew cp /etc/prosody/prosody.cfg.lua.rpmsave /etc/prosody/prosody.cfg.lua systemctl restart prosody