Multi-domain messaging
BlueMind can host several completely separate mail systems on the same infrastructure (one or more physical or virtualized servers). This principle, known as multidomain or multi-tenant, can be used in cloud infrastructures or simply to enable several messaging systems to coexist.
While technically this multi-domain infrastructure corresponds to a single installation, functionally each domain of this infrastructure must be considered as a separate mailbox, independent and isolated from the other domains.
Domains and domain aliases
A domain is identified by its primary domain name (such as mail.bluemind.net for example)).
Each domain can have one or more domain aliases: these are other domain names or subdomains (such as webmail.bluemind.net or mail.bluemind.fr)) which are then hosted on the same domain. In this case, mail services are not partitioned.
These domains can be:
- aliases: each user can exist on one or more alias domains (the user can thus receive messages on each of the domains where their address has been defined)
- different mail services, but not totally separate.
So, for example, for two companies with the same director, it's possible to have a single mail service, with only the director having an account on both domains. That way he has a single calendar which he can share with users in either domain. In this configuration, all users have an email in the main domain.
Selection criteria in multi-domain architecture
Within a single mail domain, data isn't partitioned. Individual rights can be used to hide or partition user data through the rights set by administrators and users themselves.
On partitioned domains of a multi-domain infrastructure, data is completely partitioned. The mail services are sealed off, and data cannot be exchanged (see below for examples of possible sharing).
Sharing information between mail services
Collaborative mail functionalities typically allow you to access data and information coming from other systems. BlueMind has this capability, as its sharing mechanisms can be implemented within other mail services and, obviously, within other BlueMind mail domains.
In the following examples, calendars and address books can be made visible to all or some users.
Sharing individual calendars
BlueMind's external calendar publishing features allow you to access a BlueMind calendar from another BlueMind domain (see Sharing Calendars).
Example of use: the director of two organizations on separate domains can view his calendar from the first domain on the second one by sharing its url (public or private). He can also share it with employees from either organization.
Sharing domain calendars
Domain calendars (created by an administrator) can be shared to another BlueMind domain using the same method.
Example of use: a marketing calendar shared by two subsidiaries is viewed on two separate domains. It is fed by users of either one of these domains. It can be published and viewed in the other domain by creating a new external calendar associated to a sharing url.
Sharing address books
Using APIs, you can an export address book from one BlueMind domain and insert it, still using APIs, as an address book from another BlueMind domain.
Example of use: the address book of local government officials is maintained from the city's mail domain and can be accessed through the metropolitan government's mail domain.
Domain administration
The domain administration section of the admin console gives you access to technical domain settings (server addresses, domain aliases, etc.) as well as default user settings (address books, message filters, storage quotas, archiving, etc.).
For more information, please visit Managing Domains.