Last week we let you know about the release of MailStore v10.1, the centrepiece of which was a simple but useful feature we’ve been asked for quite a bit – scheduled email reporting.
You may be thinking, MailStore is German so there won’t be any issues to report on!? Well, not everything about your email is under MailStore’s control, so as an administrator, it’s still nice to see confirmation that your ‘Enten in einer Reihe’ occasionally.
In this blog post, I’ll show you how to enable the delightful HTML report email, and let you know how to get the most from it.
These days we all expect our email to work flawlessly when we’re outside of the office, regardless of how we’re connected. Occasionally though, a change of connection is all it takes to cause issues.
In this post I take a quick look at why, if you connect to your own mail server using an SMTP connection (not applicable to ActiveSync users) from your mobile device, laptop or even desktop machine, you might experience problems with sending email. Oh, and what you can do about it of course!
Today’s nugget of MDaemon wisdom comes from conversations I’ve had with a small number of customers reporting they’re unable to send outbound email to specific recipients.
Upon closer inspection of the error in the SMTP (OUT) log, there’s a message reading “SSL negotiation failed“.
Out of the box MDaemon has some very detailed logging and real-time statistics built into the application.
In this post I’ll show you how to learn more about what a server’s doing using the free Performance Monitor feature in Windows.
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’.
Those of you already familiar with MDaemon and Texas-based developer Alt-N Technologies, will know that feedback from customers has always played a pivotal role in the way their products evolve.
The MDaemon beta community has been fundamental to this process but as we look towards the future and the imminent release of version 13, they’re opening this up and making it simple for anyone to contribute ideas and suggestions via their Idea Engine.
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.
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.