Our standard recommendation for anyone who wants a true email archiving solution is MailStore Server, however, MDaemon does have some basic archiving capabilities worth being aware of too.
Version 16 of MDaemon introduces changes to the way these native capabilities work, so in this post, I’m going to take a moment to explain the changes and the options now available to you.
When vendors announce plans for all singing, all dancing, shiny new reseller incentives, there’s a good chance you’ll be thinking one or both of these things…
- Why bother – one of the big companies will win
- I bet this will be a headache to understand
You’d be right. They are common issues. However, we can assure you that neither apply to this one!
In a recent blog post I talked about how MailStore can help manage and speed up the unenviable task of migrating all of your historic Exchange 2003 email to MDaemon Messaging Server.
The point at which you’re moving email platform is ideal to be introducing an archiving solution like MailStore. Primarily because it will aid with the migration process itself, but also because it will manage your mailbox sizes on an ongoing basis too.
With this in mind, we’re offering a very healthy 50% off new MailStore licences to Exchange 2003 owners who are purchasing a new MDaemon licence of any size.
One the biggest challenges you’re likely to come across if you’re considering upgrading from Exchange 2003 to an alternative email platform, is how to move the colossal volumes of email you’re likely to have amassed over the years.
It can be a daunting prospect, but if you’re moving to MDaemon Messaging Server, the process is made considerably more simple than it might otherwise be, thanks to a free ‘MDMigrator’ utility that’s bundled in the installation folder.
Will MailStore alert me when a job fails?
Of the many queries I see as a member of the MailStore support team here at Zen Software, this is one of the more common ones.
Unfortunately, for the time being at least, this isn’t something you can do from within the software but fear not – the reason for my post is that there is a workaround.
EDIT: Email reporting was introduced in v10.1 – more information here.
Today sees the latest point release in the roadmap of German developer MailStore, and in addition to a long list of fixes there are a couple of interesting new developments which have caught our collective Zen Software eye.
Version 9.2’s ‘juicy bits’ that I’ll talk a little more about in this post include:
- Independence from the Windows scheduler
- A great new synchronisation feature for users of Office 365
- Better handling of large search results in the MailStore clients
- Support for the new 64-bit version of MDaemon
In order for any users to log in to email archiving software MailStore Server, a local ‘MailStore’ user account needs to exist.
You could simply just manually create users, entering usernames and passwords individually. However for any installation with more than a handful of users, as you can probably imagine, that can soon end up becoming a pain.
For this reason, MailStore includes the directory services feature to synchronise local accounts with an external user list which is what I’m going to cover in this post.
If you’re already backing up your email as part of a standard routine, you could be forgiven for thinking that adding archiving to the mix would needlessly be doubling up.
I should mention at this point, if you’re not doing anything at all, then you really need to be rectifying that situation rather than reading our blog (as nice as it is to have you).
We’ve just made the latest version of MailStore live on our site and if you, or perhaps your customers, are users of Google Apps, it’s one I highly recommend you download.
The ability to archive Google mail isn’t completely new to MailStore, however in previous versions, each mailbox would need to be archived individually, requiring a separate archiving ‘job’ and manual entry (and ongoing maintenance) of username and password credentials.
In version 9.1, the German developer have now made the whole process a breeze.
We recently needed to migrate our own internal MDaemon and SecurityGateway server to a new location. Luckily we often do this for customers and we have guides specifically written to help with this process.
However one of the areas which we felt we haven’t documented before is how to also migrate an existing SSL certificate that was being used by multiple services in these products.