Research In Motion™ have just released an important security patch for the BlackBerry Enterprise Server platforms that could potentially affect MDaemon Messaging Server. This patch addresses a vulnerability in BlackBerry Enterprise Server (BES)  that process images and so only affects MDaemon installations that have the optional BES server installed. If you're an MDaemon customer running the BES component we recommend you follow the instructions in this knowledge base guide to be on the safe side.

Back up your data off-site with RsyncIn this new stand-alone BackupAssist "how-to" video released by developer Cortex, we see how you can check if the Image backup you have taken has everything needed to perform a full Bare Metal recovery.
As with all backups it is imperative that you verify the backups to be sure they contain what you expect so we'd highly recommend you take a look at this video when you get a moment...

We're aware that many of you are patiently awaiting the release of BackupAssist v7.0, so you'll be pleased to know we have a date! Yes, we expect the latest iteration...

With the release of BlackBerry v10.0 last week, the method for synchronising the new set of BlackBerry 10 devices with MDaemon has changed. A BlackBerry Enterprise Server (BES) is no longer required for synchronisation, and handsets now use the ActiveSync standard for personal data synchronisation. The process of setting up an ActiveSync account on a BlackBerry 10 device is actually quite similar to the Android and iOS devices, requiring just the server details, email address and password in order to connect.

If you've used Achab's Archive Server (ASM) software in the past and upgraded to MailStore, it's highly likely you'll be wanting to bring across that historic archived data to the new platform. There are two ways you can go about importing an external ASM archive to MailStore - either directly as files, or, via your MDaemon email server. One of the limitations of importing directly into MailStore is that mail can't be sorted on a per-user basis and instead the archive will have to reside under a single MailStore user account which you delegate access to via MailStore's permissions system. It's for this reason that we tend to recommend the second option and utilise the MDaemon server as an intermediary for MailStore to collect the old archive data from.