In the last few weeks we have started seeing an increase in support requests relating to email delivery problems that are outside of the control of the MDaemon server. Specifically this happens when companies are relying on an ISP mail platform to provide POP3 mailboxes and SMTP services to deliver their mail to and from MDaemon. In this article I want to point out why the method you choose to get email in and out of MDaemon is so important and how you can redesign and often simplify your mail platform to minimise the effects of changes that are 'outside of your control'.

One of the particularly nice features in MDaemon is the ability to customise the flow of email through the use of its built in content filters. In the past we've mainly focused on using the content filter in different ways to automate tasks, change message content and redirect mail to other locations. In this article I'll give you an overview of how you can make use of the content filter and MDaemon's custom queues to intercept some or all outbound email, have a user check and authorise it manually, and then let it continue along its intended delivery path.

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...

Over the last few months we have had an increasing number of support calls that relate to failing SMTP connections over Internet connections. This can happen on a range of network connections, whether it's mobile devices on 3G or home users trying to access their MDaemon mail server. Even businesses can find that they can no longer create outbound SMTP sessions on port 25 on their office broadband connections.

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.