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.

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.