Skip to main content

Release Notes 5.6

BlueMind 5.6 support

In accordance with our release lifecycle policy, the end of support dates for BlueMind 5.6 are:

  • patch support: undefined yet
  • security support : undefined yet

Introduction

Upgrade from BlueMind 4

For upgrades from BlueMind version 4, see BlueMind major version update.

Future news

MailApp

Old webmail

  • Total disappearance of the old webmail, which can no longer be installed.

Calendar

  • Sharing Calendars External calendar sharing is improved thanks to :
    • the addition of a new "Publish" option that generates a non-nominative share link, usable by anyone in possession of the link
    • an improved sharing window that sends an automatic message to external users when they create or modify their rights

Disappearance of old shared boxes

With version 5.6, the "old generation" shared boxes disappear: all shared boxes are now shared mailboxes complete meeting the new specifications.

Older boxes that still exist are automatically migrated when the server is upgraded from a lower version, major or minor, so there's nothing to do to perform the migration.

An important consequence of this is the disappearance of storage boxes associated with groups: it is still possible to assign an e-mail address to them in order to write to group members, but it is no longer possible to associate a mailbox with them to archive e-mails sent to this address, or to send e-mails on their behalf. To achieve this, BlueMind recommends creating a shared mailbox and positioning it as a member of the group; this way, the mailbox will receive and store all emails sent to the group, and it will be possible to write on its behalf thanks to a delegation.

Concerning the automatic migration of groups with messaging when BlueMind is updated:

  • They retain their addresses and aliases (see Edit groups > Mail).

  • A shared box is created if the box "Keep a copy of received messages" (doc v5.5) was checked:

    • it has for name _<nom-du-groupe>_mailbox and for address _<nom-du-groupe>_mailbox@domain.tld
    • it contains all the emails that were present in the original box
    • it includes the same shares as the original box
    • it is positioned as a group member (see Edit groups > Members)

    E-mails sent to the group's address are archived and can be consulted in the shared inbox, and administrators can manage this inbox as they would any other, according to their needs: they can modify the name, address, shares and delegations, or even remove it from the group.

The only constraint is that this box cannot have the same address as the group itself. To use a single address to receive and send on behalf of the group, you must :

  • configure group without mailbox
  • create a mail filter or activate message forwarding to group members (see Shared mailboxes > Automatic message forwarding)
  • give sharing rights to people (group members or not) who need access to the box
  • delegate authority to people (group members or not) who must be able to write on behalf of the box

For further information see the following pages :

Administration console

The patches

BlueMind version 5.6 includes the same level of patches as version 5.5.?. For details of fixes made to previous versions of BlueMind, please refer to the 5.5 patch release notes: