It's generally accepted that a message size of around 20MB is too large to send via email, and you'll find in lots of cases that mail servers will actually refuse to accept files that are this big. There are, however, many servers that don't limit the message size, which means if you try and share that high-quality 150MB video of your cat performing Dancing Queen, both your network and the recipient's will work overtime trying to deal with it.

The newest version of MDaemon will be available for download on Wednesday, September 5th. The new release sees a number of new features to help IT administrators and end users alike, such as:
  • Message ticketing support
  • Consolidated Mobile Device Management (MDM) interface and ActiveSync policies
  • Hijacked account detection
  • Document sharing, drag & drop attachments and custom logos in WorldClient
  • Traffic compression to improve Outlook Connector performance
View the PDF briefing document here for more information. As soon as it's available you'll be able to download the latest version of the installer from our web site here.

Another week, another set of new features to look at in the beta version of MDaemon version 13. Let's look at one of the more useful business features of MDaemon, the ability to capture email arriving on group email address such as sales@ and support@, and storing them directly into public folders. This feature allows a group of sales or support staff to monitor the public folders and take ownership of the emails, sharing the workload.

One of the more common customers support calls i get relates to MDaemon suddenly sending vast amounts of spam email. This floods the outbound Internet connection and everything crawls to a halt. Secondary to this the server's public IP address can get listed on various external SMTP blacklists which the customer then has to request removal from.

So on to part 2 of my look at the new MDaemon 13 beta... I mentioned ActiveSync policies in my last post, well version 13 also sees the addition of one extra small, but very nice feature, in the ability to simplify the self sign-up process for mobile devices using the Autodiscover process. By removing the necessity to know the public DNS name or IP address of your MDaemon server, all a user now needs to connect their mobile device is their email address and password.

Over the last few weeks I've been experimenting with the latest Beta editions of MDaemon version 13 and thought it'd be beneficial to share some of the great new up and coming features you can expect to see in the release. Just before I wet your appetite with the first of them - don't forget, if you're interested in getting involved in the MDaemon beta test process you can apply to join the community by registering here. 

MDaemon, Exchange or Office365?Towards the end of my last post I touched on the fact that Microsoft's recent announcement to drop Small Business Server next year has given particularly its partner community, reasons to look around at potential alternative solutions to Exchange. In this post I take a moment to highlight some of the reasons MDaemon Messaging Server should be on that list of alternatives you might be considering, including how the costs look alongside the equivalent Microsoft products.

I often speak to users of Exchange alternative MDaemon who are wondering why they've suddenly started receiving a larger volume of spam than usual. When I take a look at their installations it's not uncommon to find a secondary mail server in place with its own MX record. It's this second delivery path that can be the root cause of the problem and it's not unusual for the customer to be blissfully unaware either, as quite often they're configured by the DNS provider or their ISP automatically.

Some of our most common MDaemon support enquiries we get relate to users receiving spam. Typically the amount of spam has either suddenly increased and there is a flood of junk messages or its just a specific message that looks to be obviously spam but has somehow made its way through. Before picking up the phone to support you might find it useful to follow this simple guide to find out why MDaemon has not treated this message quite as expected.