Blog

In this latest case study, Phil Antill, IT & Facilities Manager at Winbro, kindly took the time to talk to us about his archiving requirements and succesful implementation of MailStore. The Leicestershire-based engineering company initially installed MailStore to aid with a mail server migration, however it's now being used to automatically manage their greatly-reduced mailbox sizes.

It's likely that if you've been using Outlook to archive your emails, by the time you get to the point where you're ready to  use a dedicated email archiving product such as MailStore, you'll have a number of PST archive files knocking about, and quite possibly in a variety of locations. There are a long list of reasons why we recommend against archiving to PST (which you can read all about in another post), but in this article I'm going to focus on what to do if you have gone down that route, and show you how to upload and centralise multiple PST archives in one go rather than one at a time.

How should you archive with MailStore?       If you've just downloaded MailStore, you're no doubt primed and ready to start hitting "next, next, next" to get up and running as soon as possible. Before you do however, it is worth just taking a moment to think about your requirements in a little more detail. We see all sorts of weird and wonderful variations to cater for different customer scenarios, but in most cases you'll need to consider which combination of "journalling", and direct connection to individual mailboxes you're going to use to archive your email.

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.