BlueMind 4.0-beta

The BlueMind team is proud to introduce the first beta release of our
future 4.0 version, which can be downloaded here!

A word of caution

BlueMind beta releases are exclusively available for a fresh install:
upgrades from a previous release is not supported yet. Future upgrades
from a beta to final v4.0 may not be supported either: our beta
releases should only be used for evaluation purposes.

Native Outlook support

New feature #1 without a doubt is native Outlook support. However this
is brought by the BlueMind subscription: you’ll need an evaluation
subscription (ask
here]( to be able to
install the required bm-mapi package. We provide step-by-step
here. Keep
in mind that there are still some rough edges, but we’re working on
them! You’ll find details on theses limitations in our

Native Outlook support is not supported on RedHat yet, but it will
definitely be part of the final release, and hopefully even sooner.


BlueMind 4.0 enables administrators to dispatch user information (not
only email) on multiple dedicated servers, which can improve data
consistency and performance.

Mail archiving is now fully automatic: your users won’t notice a
difference between regular and archived mail.

New e-mail entry points in the REST API

BlueMind 4.0 is adding entry points for e-mail management, you will
find them in our new REST API doc

We now provide an API comparison tool that will help you to maintain
your add-ons and scripts between BlueMind releases by showing

We wish you a pleasant evaluation!

Changelog 4.0-beta2

  • BM-14080 Feat: RHEL7 MAPI support
  • Fix: bm-cli addressbookuid in contact deduplicate command
  • BM-13675 BM-14097 Feat: prepare some caching of our service topology
  • BM-14115 MAPI Fix: don’t consider archived users as active delegates
  • BM-14115 MAPI Fix: crash on unauthorized freebusy request
  • COAX-546 Fix: service URL incorrect as seen from Outlook
  • COAX-547 Fix: crash on Outlook calendar sharing
  • MAPI Fix: when deleting props, merge with previously unset values
  • BM-14165 Replication Fix: file descriptor leak sucking all system memory with deleted files in /dev/shm
  • BM-14119 Signature Feat: support for fax.home and variables
  • BM-14104 Imp: support Thunderbird >= 65

Changelog 4.0-beta3

  • COAX-549 Imp: Outlook online mode features and performance
  • Feat: Add --match option to filter using a regexp in bm-cli
  • BM-14244 Feat: add server API for unreadItems (we need to apply overlay on mailshares) and use that to deal with MAPI unread filter
  • BM-14245 Fix: schedule in at least 2ms to prevent vertx error
  • FACTORFX-142 Impr: domino archive migration in a specific folder
  • Feat: ElasticSearch 6.4.3 upgrade
  • Feat: postgresql 11 upgrade
  • FEATWEBML-209 Imp: add part content disposition for MailboxItem
  • BM-13375 Fix: re-reset the OAB every hour
  • BM-13785 Fix: don’t give whole mailbox ACLs when the folder is not inbox
  • BM-14004 Fix: don’t null pointer on tables without columns when creating a notification
  • BM-14170 Feat: limit number of results for domain addressbook search
  • BM-14182 Fix: mail search in outlook online mode
  • BM-14185 Fix: return NotEnoughMemory for props with values
  • BM-14243 Fix: Outlook contact search
  • BM-14244 Feat: fast path for well known searches
  • BM-14244 Feat: Quick (ES-based) full text search in mailshare folders
  • BM-14246 Fix: sent email is empty
  • BM-14267 Feat: send-on-behalf sets the right from & sender header
  • BM-14268 Fix: set content-id on parts when the corresponding mapi prop is set
  • BM-14275 Fix: incorrect session expiration
  • Fix: check & repair are inverted for mapi.folders op
  • Fix: throttle hollow serialization (mapi cache)
  • BM-14120 Feat: make monitoring TICK stack mandatory
  • BM-14120 Fix: handle milter hprofs with tick self-healing
  • FEATBL-307 Feat: auto-configure postgresql local memory
  • BM-14264 Fix: vulnerability reported by Synacktiv in contact app (CVE-2019-9563)
  • Fix: Thunderbird addon initialized twice causing sync issues
  • BM-13553 Fix: nginx configuration consistency on multi-server install