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.

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.

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.